Serious bug shunting messages
Sorry, didn't have the time to look if there already was a bug report on SF for this one...
I'm getting this traceback and a lot of files in qfiles/shunt/, seems to be something with digests and i18n? List language is Norwegian.
Mar 12 22:47:24 2003 (10688) Traceback (most recent call last):
File "/home/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop
self._onefile(msg, msgdata)
File "/home/mailman/Mailman/Queue/Runner.py", line 155, in _onefile
keepqueued = self._dispose(mlist, msg, msgdata)
File "/home/mailman/Mailman/Queue/IncomingRunner.py", line 130, in
_dispose
more = self._dopipeline(mlist, msg, msgdata, pipeline)
File "/home/mailman/Mailman/Queue/IncomingRunner.py", line 153, in
_dopipeline sys.modules[modname].process(mlist, msg, msgdata)
File "/home/mailman/Mailman/Handlers/ToDigest.py", line 82, in process
send_digests(mlist, mboxfp)
File "/home/mailman/Mailman/Handlers/ToDigest.py", line 123, in
send_digests
send_i18n_digests(mlist, mboxfp)
File "/home/mailman/Mailman/Handlers/ToDigest.py", line 295, in
send_i18n_digests
msg = scrubber(mlist, msg)
File "/home/mailman/Mailman/Handlers/Scrubber.py", line 264, in
process
part.set_payload(_("""
File "/home/mailman/Mailman/i18n.py", line 78, in _
return _translation.gettext(s) % dict
UnicodeError: ASCII decoding error: ordinal not in range(128)
This is giving me a major headache... I'm having 60+ messages stuck in the shunt queue, and people complaining about lists not working, messages not getting through, etc... anyone else seen this?
I'm using latest Release_2_1-maint CVS branch...
"DB" == Daniel Buchmann <Daniel.Buchmann@bibsys.no> writes:
DB> This is giving me a major headache... I'm having 60+ messages
DB> stuck in the shunt queue, and people complaining about lists
DB> not working, messages not getting through, etc... anyone else
DB> seen this?Ha! I'll bet you have messages with rfc2231 encoded non-ascii filename or description parameters. But that's just a wild guess. :)
Peer's been haranguing me <wink> about similar problems for weeks. I /think/ I might have a solution but I want to test it a little bit more before I commit it to the head. I need to backport a bunch of head changes to the maint branch. We'll see if I have time for all that tonight.
synchronicit-ly y'rs, -Barry
On Wed, 2003-03-12 at 23:03, Barry A. Warsaw wrote:
Peer's been haranguing me <wink> about similar problems for weeks. I /think/ I might have a solution but I want to test it a little bit more before I commit it to the head. I need to backport a bunch of head changes to the maint branch. We'll see if I have time for all that tonight.
Thanks a lot Barry! The recently committed change to i18n.py solved the problem! :D My qfiles/shunt/ dir is now empty. I also had a problem with the daily cron/senddigests, but it went away after patching i18n.py. ;)
Btw: where is the message pipeline in Mailman? What I want to do is change the order of the tests that cause messages to be held etc. (See my post http://mail.python.org/pipermail/mailman-developers/2003-February/014847.htm...)
Thanks, hope to see you around on #mailman again sometime soon. ;)
.dan
Hi Barry,
just a note to mention that last night's corrections have solved the "daily reminder unicode traceback" that I had been getting for a week. Thanks.
BTW, does anyone have a current pointer how how to integrate spamassassin into the Mailman pipe? (A Google search brings a lot of old stuff.)
-- Fil
just a note to mention that last night's corrections have solved the "daily reminder unicode traceback" that I had been getting for a week. Thanks.
Oops! bin/list_members doesn't work anymore
Traceback (most recent call last): File "/home/mailman/bin/list_members", line 240, in ? main() File "/home/mailman/bin/list_members", line 218, in main print >> fp, formataddr((safe(name), addr)) File "/home/mailman/bin/list_members", line 103, in safe return unicode(addr, ENC, 'replace').encode(ENC, 'replace') TypeError: coercing to Unicode: need string or buffer, int found
-- Fil
"DB" == Daniel Buchmann <Daniel.Buchmann@bibsys.no> writes:
DB> Thanks a lot Barry! The recently committed change to i18n.py
DB> solved the problem! :D My qfiles/shunt/ dir is now empty. I
DB> also had a problem with the daily cron/senddigests, but it
DB> went away after patching i18n.py. ;)Excellent!
DB> Btw: where is the message pipeline in Mailman? What I want to
DB> do is change the order of the tests that cause messages to be
DB> held etc. (See my post
DB> http://mail.python.org/pipermail/mailman-developers/2003-February/014847.html)This part's definitely kludgy, and I have ideas for how to fix it. But for now, there are two places to look. First is GLOBAL_PIPELINE in Defaults.py.in. There you'll see that it calls out to the Moderate module and then to the Hold module. There's been a bit of thrash on the order of these. ;)
Then, inside Hold.py, you'll see that process() hard codes the order in which conditions are tried. Changing this requires hacking the code.
My idea (for 2.2 or 3.0 -- I'm still conflicted) is that /all/ the hold tests would be applied to a message and there'd be some way <wink> for admins to either see all the conditions that apply or select the priority in which they cause a message to be held or rejected. Not much more detail than that, but it's definitely something on my radar. Suggestions are welcome!
DB> Thanks, hope to see you around on #mailman again sometime
DB> soon. ;)I'm trying to hang out there occasionally these days! -Barry
participants (4)
-
barry＠python.org -
Dan Mick -
Daniel Buchmann -
Fil