[Mailman-Users] Shunted messages on mailman 2.1.8

[Mark Sapiro]

Jannis Leidel wrote:
>
>I recently upgaded on a debian server to mailman 2.1.8 and came
>across some problems.
>Emails sent to any of the running lists are shunted and therefore not  
>delivered..
>
>The log states:
>
>May 04 17:29:48 2006 (16886) Uncaught runner exception: 'ascii' codec  
>can't decode byte 0xfc in position 62: ordinal not in range(128)
>May 04 17:29:48 2006 (16886) 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 167, in
>_onefile
>     keepqueued = self._dispose(mlist, msg, msgdata)
>   File "/usr/lib/mailman/Mailman/Queue/OutgoingRunner.py", line 73,
>in _dispose
>     self._func(mlist, msg, msgdata)
>   File "/usr/lib/mailman/Mailman/Handlers/SMTPDirect.py", line 132,
>in process
>     Decorate.process(mlist, msg, msgdata)
>   File "/var/lib/mailman/Mailman/Handlers/Decorate.py", line 99, in
>process
>     ufooter = unicode(footer, lcset)
>UnicodeDecodeError: 'ascii' codec can't decode byte 0xfc in position
>62: ordinal not in range(128)
>
>May 04 17:29:48 2006 (16886) SHUNTING: 1146751225.21892
>+6230ec621e1d4a40688513317ea394ddb0d8e5e8
>
>It worked on 2.1.7  so do you have any idea how to fix this?


It looks like we may have a bug in this area, but in the mean time, I
think you can avoid the problem by removing any non-ascii characters
from the list's msg_footer.

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