[Mailman-Users] character encoding error

[Dan Phillips]

When I updated to 2.1.3 I immediately had problems with Japanese 
language password reminders causing errors, but I applied the patch 
provided by Tokio Kikuchi and those went away. Since then, however, 
every time I receive a post that includes an unusual (for English) 
character -- ç, 1/2 (as one character), anything with an umlaut, etc -- 
the following error message is generated:

> Oct 09 08:04:51 2003 (449) Uncaught runner exception: 'NoneType' 
> object has no attribute 'lower'
> Oct 09 08:04:51 2003 (449) Traceback (most recent call last):
>   File "/users/mailman/Mailman/Queue/Runner.py", line 110, in _oneloop
>     self._onefile(msg, msgdata)
>   File "/users/mailman/Mailman/Queue/Runner.py", line 160, in _onefile
>     keepqueued = self._dispose(mlist, msg, msgdata)
>   File "/users/mailman/Mailman/Queue/IncomingRunner.py", line 130, in 
> _dispose
>     more = self._dopipeline(mlist, msg, msgdata, pipeline)
>   File "/users/mailman/Mailman/Queue/IncomingRunner.py", line 153, in 
> _dopipeline
>     sys.modules[modname].process(mlist, msg, msgdata)
>   File "/users/mailman/Mailman/Handlers/ToDigest.py", line 90, in 
> process
>     send_digests(mlist, mboxfp)
>   File "/users/mailman/Mailman/Handlers/ToDigest.py", line 131, in 
> send_digests
>     send_i18n_digests(mlist, mboxfp)
>   File "/users/mailman/Mailman/Handlers/ToDigest.py", line 373, in 
> send_i18n_digests
>     rfc1153msg.set_payload(plainmsg.getvalue(), lcset)
>   File "/users/mailman/pythonlib/email/Message.py", line 224, in 
> set_payload
>     self.set_charset(charset)
>   File "/users/mailman/pythonlib/email/Message.py", line 262, in 
> set_charset
>     cte(self)
>   File "/users/mailman/pythonlib/email/Encoders.py", line 88, in 
> encode_7or8bit
>     charset = msg.get_charset().output_charset.lower()
> AttributeError: 'NoneType' object has no attribute 'lower'
>
> Oct 09 08:04:51 2003 (449) SHUNTING: 
> 1065704690.3426059+c2b29a13c674529127a4c79472d3c58829f5937c

Unfortunately, every message received after the offending one is also 
shunted, and cron/senddigests also produces the same error message. A 
quick look at the digest.mbox shows one character that appears in pico 
as a black diamond with a question mark in it. If I replace that with 
an approximation without a diacritical and save the mbox, then I can 
run /cron/senddigests and unshunt successfully.

Any ideas?

DP