[Mailman-Users] Error during mailman runs
msapiro at value.net
Thu Sep 1 06:54:32 CEST 2005
Sean Roe wrote:
>Mark Sapiro wrote:
>>Sean Roe wrote:
>>>I am getting the following errors durring mailman runs:
>>>mailman01:/var/lib/mailman/qfiles/out# Traceback (most recent call last):
>>> File "/var/lib/mailman/bin/qrunner", line 270, in ?
>>> File "/var/lib/mailman/bin/qrunner", line 230, in main
>>> File "/var/lib/mailman/Mailman/Queue/Runner.py", line 87, in run
>>> File "/var/lib/mailman/Mailman/Queue/BounceRunner.py", line 220, in
>>> File "/var/lib/mailman/Mailman/Queue/BounceRunner.py", line 132, in
>>> File "/var/lib/mailman/Mailman/Queue/BounceRunner.py", line 120, in
>>> mlist.registerBounce(addr, msg, day=day)
>>> File "/var/lib/mailman/Mailman/Bouncer.py", line 108, in registerBounce
>>> info = self.getBounceInfo(member)
>>> File "/var/lib/mailman/Mailman/MysqlMemberships.py", line 530, in
>>> row, row)
>>>TypeError: __init__() takes exactly 5 arguments (6 given)
>>>What does this mean?
>>It appears to be saying that the MysqlMemberships.py member adaptor
>>that you have installed is not compatible with your version of Mailman.
>>What Mailman version do you have?
>>What version of MysqlMemberships.py do you have (latest is 1.61,
>>Mark Sapiro <msapiro at value.net> The highway is for gamblers,
>>San Francisco Bay Area, California better use your sense - B. Dylan
>I am using 1.61 per the revision number on the file:
>Kev Green, oRe Net (http://www.orenet.co.uk/), 2003/11/04
>$Revision: 1.61 $
>and the mailman version is via version in bin:
>Using Mailman version: 2.1.6
>Is there some sort of issue with spammers? It doesn't happen all the
>time. There appears to be no rhyme or reason for it.
The number of arguments to __init__ in the _BounceInfo class changed
from 6 to 5 in Mailman 2.1.4. It looks like the MysqlMemberships.py
member adaptor getBounceInfo() method is not compatible with Mailman
versions newer than 2.1.3.
This error doesn't occur all the time because getBounceInfo() only
instantiates a _BounceInfo object when it is asked to return existing
bounce info which is only when a bounce is being processed for a
member with prior bounces.
I suggest you take this up with the author/provider of the
MysqlMemberships.py member adaptor.
Mark Sapiro <msapiro at value.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
More information about the Mailman-Users