[Mailman-Users] shunting messages

[Noah]

Mark Sapiro wrote:
> Noah wrote:
>
>   
>> Take a look at this.  I ran bin/unshunt
>>
>> now i have a ton of 'SHUNT' errors in the /usr/local/mailman/logs/error
>>
>>
>> so it looks like there are some python errors here.  please look below.  
>> I am not sure where to go from here.
>>
>> # pkg_info | grep python
>> python-2.3.5_1      An interpreted object-oriented programming language
>> python-2.4.3        An interpreted object-oriented programming language
>> # pkg_info | grep mailman
>> mailman-2.1.9       A mailing list manager (MLM) with a user-friendly 
>> web front
>> # python -V
>> Python 2.4.3
>>
>>
>> ---- snip ----
>>
>> Oct 07 18:26:43 2006 (65294) SHUNTING: 
>> 1160195626.2888789+de6ec73e1418406952d796443
>> 2212bd9d3bac7a5
>> Oct 07 18:26:44 2006 (65294) Uncaught runner exception: 'str' object has 
>> no attribu
>> te 'get_sender'
>> Oct 07 18:26:44 2006 (65294) Traceback (most recent call last):
>>  File "/usr/local/mailman/Mailman/Queue/Runner.py", line 112, in _oneloop
>>    self._onefile(msg, msgdata)
>>  File "/usr/local/mailman/Mailman/Queue/Runner.py", line 162, in _onefile
>>    sender = msg.get_sender()
>> AttributeError: 'str' object has no attribute 'get_sender'
>>     
>
> There seems to be an issue with the FreeBSD Mailman 2.1.9 package. See
> the whole thread beginning at
> <http://mail.python.org/pipermail/mailman-users/2006-September/053546.html>.
> The second and third posts in that thread give a suggested workaround
> (be sure to read the correction in the third post). I still have no
> idea what the cause is, especially since in your case, you say it only
> affects one list. It may not even be the whole source of your problem,
> and it appears the workaround may not have been effective for the OP.
>
> Perhaps there is some modification in the FreeBSD package that breaks
> the queueing mechanism. Can you download Switchboard.py, revision 8023
> from
> <http://svn.sourceforge.net/viewvc/mailman/tags/Release_2_1_9/Mailman/Queue/Switchboard.py?view=log>
> and compare it to the one in your installation - maybe post the result
> of 'diff -u' if they are different.
>
>   
thank you for the explanation after looking at the first message with 
bin/dumpdb

I am able to see parsemsg is set to:

--- snip ---

{   '_parsemsg': False,
    'received_time': 1160195626.2888789,
    'version': 3,
    'whichq': '/usr/local/mailman/qfiles/in'}
[----- end pickle file -----]


----s nip ---

so I am hoping your fix works

cheer,s

Noah