[Mailman-Users] Assertion error in senddigests

Mark Sapiro msapiro at value.net
Sat Jun 16 00:29:49 CEST 2007

Dan Lowe wrote:

>I know a bit of Python, but this traceback is way over my head. I'm  
>getting this every day when the senddigests cron job runs:
>Traceback (most recent call last):
>   File "/usr/local/pkg/mailman/cron/senddigests", line 94, in <module>
>     main()
>   File "/usr/local/pkg/mailman/cron/senddigests", line 86, in main
>     mlist.send_digest_now()
>   File "/usr/local/pkg/mailman/Mailman/Digester.py", line 60, in  
>     ToDigest.send_digests(self, mboxfp)
>   File "/usr/local/pkg/mailman/Mailman/Handlers/ToDigest.py", line  
>142, in send_digests
>     send_i18n_digests(mlist, mboxfp)
>   File "/usr/local/pkg/mailman/Mailman/Handlers/ToDigest.py", line  
>324, in send_i18n_digests
>     msg = scrubber(mlist, msg)
>   File "/usr/local/pkg/mailman/Mailman/Handlers/Scrubber.py", line  
>373, in process
>     t = t.encode(charset, 'replace')
>   File "/usr/local/pkg/python/lib/python2.5/encodings/ 
>quopri_codec.py", line 20, in quopri_encode
>     assert errors == 'strict'
>Searching list archives and Google haven't turned up anything that  
>looks useful. The traceback doesn't even point to which list was  
>being operated on at the time of the error. The only thing I've found  
>in the Mailman logs is this sort of message, in logs/error:
>Jun 12 16:08:44 2007 (504) send_digests() failed:
>Jun 12 16:11:40 2007 (504) send_digests() failed:
>Jun 12 16:18:20 2007 (504) send_digests() failed:
>Jun 12 16:21:30 2007 (504) send_digests() failed:
>Jun 12 16:21:40 2007 (504) send_digests() failed:
>Jun 12 16:23:06 2007 (504) send_digests() failed:
>Jun 12 16:47:21 2007 (504) send_digests() failed:
>Jun 12 16:49:58 2007 (504) send_digests() failed:
>Jun 12 16:58:42 2007 (504) send_digests() failed:
>Jun 12 17:20:15 2007 (504) send_digests() failed:
>Also, though most of my lists are set as digestable (but not  
>digesting by default), none of my lists have any digest-enabled  

Every post to the list triggers a digest on size and produces the above
error log message. You may be able to deduce the list from the timing
of the messages. Even if there are no digest members, if the list is
digestable, a digest.mbox is maintained and processed.

At least one of your lists has a lists/<listname>/digest.mbox file with
a bad message in it. The bad message (I think) has a Content-Type:
header with a charset="quoted-printable" parameter.

The attached senddigests.patch.txt patch to cron.senddigests will
produce stderr output pointing to the offending list and digest.mbox.
If you run it from the command line, you will see the output. If cron
runs it, you should get the output in email rather than the above

You can catch the AssertionError in scrubber. There is a fixed version
of Scrubber.py in SVN at
(rev. 8237) which has this and a few other post 2.1.9 fixes.

Mark Sapiro <msapiro at value.net>       The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: senddigests.patch.txt
Url: http://mail.python.org/pipermail/mailman-users/attachments/20070615/8cfff515/attachment.txt 

More information about the Mailman-Users mailing list