I'm running 2.1.6rc2. For the first time yesterday, I started getting cron errors and messages getting shunted. The cron errors and the shunting errors appear to be the same. When I run bin/unshunt, the following shows up in my error log:
Apr 29 17:44:04 2005 (30197) SHUNTING: 1114627404.7106659+9a129579e22b7a7876567eea456d5c78552c286f
Apr 29 17:44:04 2005 (30197) Uncaught runner exception: unicode() argument 2 must be string, not None
Apr 29 17:44:04 2005 (30197) 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 315, in send_i18n_digests
msg = scrubber(mlist, msg)
File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 349, in process
partcharset = part.get_content_charset()
File "/usr/local/mailman/Mailman/Message.py", line 204, in get_content_charset
unicode('x', charset)
TypeError: unicode() argument 2 must be string, not None
Apr 29 17:44:04 2005 (30197) SHUNTING: 1114767622.905226+1a0d1f1ee1d75fba10ef000cfb04f6aba24ec9ae
I assume the bottom TypeError is the significant part.
I found about four similar reports when I searched the archives, but didn't find any solutions. Actually I did find a reply from Barry for one of them, but it was from 2003 and said to wait for version 2.1.3.
Is this likely a bug in 2.1.6rc2, or is there something I can fix on my end?
Apparently it was a bug in 2.1.6rc2. I'm not sure whether my report triggered a very fast fix, or if I should have waited another day before reporting. In any case 2.1.6rc3 seems to have resolved the problem. Thanks guys!
------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
