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'
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?
Is there any way I can turn the shunted message into something that
can be passed to bin/inject?
There have been a couple posts of this same error, but I haven't seen
any resolution (or, in fact, reply..)
--
- Patrick Bogen
------------------------------------------------------
Mailman-Users mailing list
[email protected]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
