[Mailman-Users] Shunted Messages: Uncaught runner exception: 'str'object has no attribute 'get_sender'

[Mark Sapiro]

Patrick Bogen wrote:

>Traceback is as follows:
>
>Apr 17 11:37:11 2006 (11200) SHUNTING:
>1143744566.924134+af04699cdb8ee11fa521f987815fb056a487203c
>Apr 17 11:37:11 2006 (11200) Uncaught runner exception: 'str' object
>has no attribute 'get_sender'
>Apr 17 11:37:11 2006 (11200) Traceback (most recent call last):
>  File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop
>    self._onefile(msg, msgdata)
>  File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 159, in _onefile
>    sender = msg.get_sender()
>AttributeError: 'str' object has no attribute 'get_sender'


The real question here is why is switchboard returning an unparsed
message instead of a message object.


>Using Mailman 2.1.7-1 from Debian Testing. I can't upgrade to the
>2.1.7-2 from Testing until I get these unshunted.
>
>If I move them aside, and upgrade, and then attempt to unshunt, will
>it cause problems?


Probably, because the queue entries may be defective. I.e. it appears
that the message object in the .pck file is an unparsed string but
'_parsemsg' is False in the message metadata.


>Is there any way I can turn the shunted message into something that
>can be passed to bin/inject?


bin/show_qfiles should be the way, but it was broken until 2.1.8 and
may not work anyway because of the apparent problem.

bin/dumpdb should both produce a text message and show the metadata so
you can see if my theory is correct.


>There have been a couple posts of this same error, but I haven't seen
>any resolution (or, in fact, reply..)


Maybe you can gather enough information to find the cause.

-- 
Mark Sapiro <msapiro at value.net>       The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan