Tokio Kikuchi wrote: > >I'm curious what kind of message caused this error. >I think that the exact message causing this error contains a header like: > >Content-Type: text/plain; charset=base64 > >It would be nice if you can check the moved digest.mbox and answer if my >hyposis is right or not.
Also Jared, what Mailman version is this? see below. >Mark, I've checked in a patch for this error. Will you please review it >and back out if it is not appropriate because I have not much time to >spend now. I'm kind of swamped myself, but I will look further at the patch. On first inspection, it seems it won't cause any harm and may in this case produce a good digest, but I think the answer depends on exactly what the bad message is. Also, the Mailman 2.1.7 patch to ToDigest.py to catch all send_digests exceptions should prevent the shunting in this case, although digests are still stopped, so the current patch or another patch is required to get the digest out. -- Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ 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
