Shunt clogged up - RFC2231 unicode problem?
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GNU Mailman |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Dozens of messages are backed up in my shunt directory
with the message "TypeError: unicode() argument 2 must
be string, not None" (full traceback example below).
This seems very similar to a problem fixed by ber with 2.0.x
earlier this year but I'm running 2.1.2 (on FreeBSD). I tried
my best to apply a similar solution to Message.py but
apparently I don't know enough about python to make it
work.
Here's a typical Traceback --
Aug 16 16:08:25 2003 (46338) Uncaught runner
exception: unicode() argument 2 must be string, not None
Aug 16 16:08:25 2003 (46338) Traceback (most recent
call last):
File "/usr/local/
105, in _oneloop
self.
File "/usr/local/
155, in _onefile
keepqueued = self._dispose(
File "/usr/local/
IncomingRunner.py", line 130, in _dispose
more = self._dopipelin
File "/usr/local/
IncomingRunner.py", line 153, in _dopipeline
sys.
File "/usr/local/
line 89, in process
send_
File "/usr/local/
line 130, in send_digests
send_
File "/usr/local/
line 303, in send_i18n_digests
msg = scrubber(mlist, msg)
File "/usr/local/
line 257, in process
url = save_attachment
File "/usr/local/
line 348, in save_attachment
fnext = os.path.
File "/usr/local/
707, in get_filename
return unicode(
TypeError: unicode() argument 2 must be string, not None
[http://
ps - moving the various digest.mboxes freed up the blocked lists -
too many messages with attachments in the digests for me to
figure out exactly which one was causing the problem, but I'll be
happy to forward copy of offending mbox to anyone interested.