Traceback in error file

Bug #265758 reported by Acarpenter
2
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/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)

[http://sourceforge.net/tracker/index.php?func=detail&aid=630497&group_id=103&atid=100103]

Revision history for this message
Barry Warsaw (barry) wrote :

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.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.