[Mailman-Users] bouce processing problem
Mark Sapiro
mark at msapiro.net
Sat Sep 26 17:05:51 CEST 2009
Dimitrios Karapiperis wrote:
>
>Is there anything I can do for the floating point issue?
It probably isn't an issue. I'm just guessing with incomplete
information.
>here is a chink form error file
>
>admin(28713): Traceback (most recent call last):
>173 admin(28713): File "/usr/lib/mailman/scripts/driver", line 101, in
>run_main
>174 admin(28713): main()
>175 admin(28713): File "/usr/lib/mailman/Mailman/Cgi/options.py", line
>178, in main
>176 admin(28713): mlist.ConfirmUnsubscription(user, userlang)
>177 admin(28713): File "/usr/lib/mailman/Mailman/MailList.py", line
>1286, in ConfirmUnsubscription
>178 admin(28713): cookie = self.pend_new(Pending.UNSUBSCRIPTION, addr)
>179 admin(28713): File "/usr/lib/mailman/Mailman/Pending.py", line 65,
>in pend_new
>180 admin(28713): db = self.__load()
>181 admin(28713): File "/usr/lib/mailman/Mailman/Pending.py", line 95,
>in __load
>182 admin(28713): return cPickle.load(fp)
>183 admin(28713): AttributeError: 'module' object has no attribute
>'UserDesc'
>184 admin(28713): [----- Python Information -----]
>185 admin(28713): sys.version = 2.4.3 (#1, Sep 17 2008, 16:07:08)
>186 [GCC 4.1.2 20071124 (Red Hat 4.1.2-41)]
>187 admin(28713): sys.executable = /usr/bin/python
>188 admin(28713): sys.prefix = /usr
>189 admin(28713): sys.exec_prefix = /usr
>190 admin(28713): sys.path = /usr
>191 admin(28713): sys.platform = linux2
This specific error has nothing to do with bounce processing. It would
have resulted in a "we hit a bug" message when someone tried to
unsubscribe from the options login page for some list. It indicates
that that list's lists/LISTNAME/pending.pck file is corrupt. This
could also cause errors in bounce processing for that list which
should also be logged.
Try the following for each list (assuming normal RedHat paths)
#! /bin/sh
for list in `/usr/lib/mailman/bin/list_lists --bare`; do
echo $list
/usr/lib/mailman/bin/dumpdb /var/lib/mailman/lists/$list/pending.pck
done
If the attempt to dump the pending.pck for a list throws an exception
with a traceback, rather than dumping the contents, that list's
pending.pck is corrupt. Remove it, and a new one will be created when
needed. This may fix bounce processing for any list with a corrupt
pending.pck.
Also note the following:
The bounce log messages like:
Sep 25 18:43:55 2009 (5775) test: city at domain.gr already scored a
bounce for date 25-Sep-2009
are normal. Once a bounce is recorded for a particular user on a
particular list, all subsequent bounces for that user/list on the same
calendar day are ignored. This also means that if the threshold is,
e.g., 5 and the user's score is 2 (from a bounce on this day),
lowering the threshold to 2 or less will; have no effect for that user
until a bounce is received on a subsequent day.
--
Mark Sapiro <mark at msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
More information about the Mailman-Users
mailing list