Uncaught runner exception

[Jd-waverly]

In 2.1.5 Apparently some email message characters can
crash the Runner.py. I have inserted $mailman in place
of my mailman path in the message below from
$mailman/logs/error

Jun 12 01:25:48 2004 (16604) Uncaught runner
exception: ASCII decoding error: ordinal not in range
(128)
Jun 12 01:25:48 2004 (16604) Traceback (most recent
call last):
  File "$mailman/Mailman/Queue/Runner.py", line 111, in
_oneloop
    self._onefile(msg, msgdata)
  File $mailman/Mailman/Queue/Runner.py", line 167, in
_onefile
    keepqueued = self._dispose(mlist, msg, msgdata)
  File "$mailman/Mailman/Queue/CommandRunner.py",
line 223, in _dispose
    res = Results(mlist, msg, msgdata)
  File "$mailman/Mailman/Queue/CommandRunner.py",
line 77, in __init__
    subj = make_header(decode_header
(subj)).__unicode__()
  File "$mailman/pythonlib/email/Header.py", line 144, in
make_header
    h.append(s, charset)
  File "$mailman/pythonlib/email/Header.py", line 272, in
append
    ustr = unicode(s, incodec, errors)
UnicodeError: ASCII decoding error: ordinal not in range
(128)

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

[Tomtervo (tomtervo)]

Do you need some additional information for debugging this
one, I've over 200 mails stuck on shunts. AFAIK this is
quite fatal bug, emails just disappear and nobody gets
notification.
UnicodeDecodeError: 'ascii' codec can't decode byte 0xf6 in
position 10: ordinal not in range(128)

Mailman 2.1.5 and python 2.3.4 on Solaris 8.

[Gray-john (gray-john)]

I'm seeing this in 2.1.6 as well. We are running Debian
Sarge. Any word on getting this resolved?

[Mark Sapiro (msapiro)]

gray-john wrote:
>
>I'm seeing this in 2.1.6 as well. We are running Debian
>Sarge. Any word on getting this resolved?

This error was fixed in source in 2.1.6 by catching and
passing the UnicodeError exception. See bug 909490 which is
the same problem.

If you are seeing this error in 2.1.6, it must be coming
from somewhere other than CommandRunner calling make_header.

I suggest you try to get a resolution by posting your
specific error trace to <email address hidden>.

I'm closing this report.

[Doctorchd (doctorchd)]

mailman 2.1.6 on FreeBSD (default installation from ports
collection)
python-2.4.2

A letter with charset=ISO-2022-JP stopped a maillist. New
letters are added to the digest but not get sent.

logs/error:
Dec 08 11:12:05 2005 (8832) Uncaught runner exception:
ISO-2022-JP decoding error: invalid designation
Dec 08 11:12:05 2005 (8832) Traceback (most recent call last):
  File "/usr/local/mailman/Mailman/Queue/Runner.py", line
111, in _oneloop
    self._onefile(msg, msgdata)
  File "/usr/local/mailman/Mailman/Queue/Runner.py", line
167, in _onefile
    keepqueued = self._dispose(mlist, msg, msgdata)
  File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py",
line 130, in _dispose
    more = self._dopipeline(mlist, msg, msgdata, pipeline)
  File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py",
line 153, in _dopipeline
    sys.modules[modname].process(mlist, msg, msgdata)
  File "/usr/local/mailman/Mailman/Handlers/ToDigest.py",
line 92, in process
    send_digests(mlist, mboxfp)
  File "/usr/local/mailman/Mailman/Handlers/ToDigest.py",
line 133, in send_digests
    send_i18n_digests(mlist, mboxfp)
  File "/usr/local/mailman/Mailman/Handlers/ToDigest.py",
line 331, in send_i18n_digests
    payload = unicode(payload, mcset, 'replace'
UnicodeError: ISO-2022-JP decoding error: invalid designation

Dec 08 11:12:05 2005 (8832) SHUNTING:
1134033124.1110449+22e27c8eb18c70264c17eb27d07146812a8c656c

I can present the letter that causes this error (I didn't
find how is it possible to attach a file here).

[Mark Sapiro (msapiro)]

A few remarks with regard to the 2005-12-08 comment from
doctorchd:

1) Posting new information to a Closed/Fixed Bug report is
not too useful. It would be better to generate a new report.

2) The Traceback and error reported by doctorchd is not at
all the same error as the one originnaly reported in this
report. The only thing they have in common is they both
generate uncaught UnicodeError exceptions.

3) The error reported by doctorchd is fixed by patch 1246003
which has been accepted and is in CVS.