Traceback in error file
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GNU Mailman |
Fix Released
|
High
|
Unassigned |
Bug Description
Since I upgraded to 2.1b4, I have started to get the
following tracebacks in the error log file. It is a
characteristics of our busiest mail list that many of the posts
come from the far east with unicode characters in their
subject line.
Oct 29 14:19:35 2002 (26533) Uncaught runner exception:
ASCII decoding error: or
dinal not in range(128)
Oct 29 14:19:35 2002 (26533) Traceback (most recent call
last):
File "/usr/local/
105, in _oneloop
self.
File "/usr/local/
154, in _onefile
keepqueued = self._dispose(
File "/usr/local/
, line 129, in _dispo
se
status = self._dopipelin
File "/usr/local/
, line 167, in _dopip
eline
mlist.
File "/usr/local/
BounceMessage
lang=
File "/usr/local/
__init__
self['Subject'] = Header(subject, charset,
header_
File "/usr/local/
164, in __init__
self.append(s, charset)
File "/usr/local/
230, in append
ustr = unicode(s, incodec)
UnicodeError: ASCII decoding error: ordinal not in range
(128)
[http://
There have been lots of related fixes in 2.1b6 (and in cvs),
so it would be good to know whether upgrading fixes the problem.
If not, please un-pend this bug report and attach (not
paste) one of the offending messages so I can try to
reproduce it.