Bugs item #630497, was opened at 2002-10-29 09:41 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=630497&group_id=103

Category: bounce detection Group: 2.1 beta

Status: Pending Resolution: None Priority: 7 Submitted By: Andy Carpenter (acarpenter) Assigned to: Nobody/Anonymous (nobody) Summary: Traceback in error file

Initial Comment: 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/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 154, in _onefile keepqueued = self._dispose(mlist, msg, msgdata)

File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py" , line 129, in _dispo se status = self._dopipeline(mlist, msg, msgdata, pipeline)

File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py" , line 167, in _dopip eline mlist.BounceMessage(msg, msgdata, e) File "/usr/local/mailman/Mailman/Bouncer.py", line 273, in BounceMessage lang=self.preferred_language) File "/usr/local/mailman/Mailman/Message.py", line 203, in __init__ self['Subject'] = Header(subject, charset, header_name='Subject') File "/usr/local/mailman/pythonlib/email/Header.py", line 164, in __init__ self.append(s, charset) File "/usr/local/mailman/pythonlib/email/Header.py", line 230, in append ustr = unicode(s, incodec) UnicodeError: ASCII decoding error: ordinal not in range (128)

Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-24 00:00

Message: Logged In: YES user_id=12800

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.

You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=630497&group_id=103