[Mailman-Users] Error in pipermail
mark at msapiro.net
Mon Oct 29 23:47:20 EDT 2018
On 10/25/18 12:03 PM, David Gibbs wrote:
> I just upgraded from a pretty old version of MM to 2.1.29 and everything
> appears to be working OK.
> I noticed the following in my error log though.
> I only have a few lists that archive using the built in functionality.
> Oct 24 07:57:40 2018 (18940) Uncaught runner exception: 'ascii' codec
> can't decode byte 0xb5 in position 26: ordinal not in range(128)
> Oct 24 07:57:40 2018 (18940) Traceback (most recent call last):
> File "/usr/local/mailman/Mailman/Queue/Runner.py", line 119, in _oneloop
> self._onefile(msg, msgdata)
> File "/usr/local/mailman/Mailman/Queue/Runner.py", line 190, in _onefile
> keepqueued = self._dispose(mlist, msg, msgdata)
> File "/usr/local/mailman/Mailman/Queue/ArchRunner.py", line 77, in
> File "/usr/local/mailman/Mailman/Archiver/Archiver.py", line 216, in
> File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 596, in
> File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 640, in
> author = fixAuthor(article.decoded['author'])
> File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 63, in
> while i>0 and (L[i-1] in lowercase or
> UnicodeDecodeError: 'ascii' codec can't decode byte 0xb5 in position 26:
> ordinal not in range(128)
> Any suggestions on how to fix this?
There should be a 'SHUNTING: xxxx.pck' message immediately following the
above traceback. This points to an entry in Mailman' qfiles/shunt/
You can see the message by pointing Mailman's bin/show_qfiles at that
file. There is something bogus and/or non-ascii in that message's From:
header, possibly an RFC 2047 encoded word with the 'wrong' character set.
Please post the message or at least the headers of the message here, and
I will investigate further.
Mark Sapiro <mark at msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
More information about the Mailman-Users