PROBLEM: Cron <mailman@king> /usr/bin/python -S /var/mailman/cron/senddigests
Hello! I've just subscribed to see if anyone here is familiar with the error report I am now getting repeatedly from mailman (see below).
Also, I'm not certain yet, but it appears my archiving may have stopped working. When I go to check archives, there are no listings for the current week.
If there is a specific set of info I can post (config, etc) let me know. I've made no changes to list settings in the past few days, and my postfix logs seem to show individual e-mails going out from the lists.
Incidentally, I'm sorry, but generic fixes like "upgrade mailman" won't help me, because I'm stuck with the Red Hat 9 rpm. (sigh) But if someone can tell me how to 'unstick' the following error, I would appreciate it.
---------- Forwarded message ---------- Date: Sun, 29 Oct 2006 12:00:02 -0500 (EST) From: Cron Daemon <root@hwcn.org> To: mailman@hwcn.org Subject: [WL] Cron <mailman@king> /usr/bin/python -S /var/mailman/cron/senddigests
Traceback (most recent call last): File "/var/mailman/cron/senddigests", line 94, in ? main() File "/var/mailman/cron/senddigests", line 86, in main mlist.send_digest_now() File "/var/mailman/Mailman/Digester.py", line 60, in send_digest_now ToDigest.send_digests(self, mboxfp) File "/var/mailman/Mailman/Handlers/ToDigest.py", line 123, in send_digests send_i18n_digests(mlist, mboxfp) File "/var/mailman/Mailman/Handlers/ToDigest.py", line 295, in send_i18n_digests msg = scrubber(mlist, msg) File "/var/mailman/Mailman/Handlers/Scrubber.py", line 252, in process payload = part.get_payload(decode=1) File "/var/tmp/mailman-root/var/mailman/pythonlib/email/Message.py", line 189, in get_payload File "/var/tmp/mailman-root/var/mailman/pythonlib/email/Utils.py", line 75, in _bdecode File "/usr/lib/python2.2/base64.py", line 44, in decodestring return binascii.a2b_base64(s) binascii.Error: Incorrect padding
Thanks,
- Charles
Additional note: I'm now digging through the archives (and having better luck finding 'incorrect padding' as a search term).
It looks like it is caused by an attachment coding prob? Makes me wonder why I am running into it now after years of successful posts?
Is it possible I could just tell list members to NOT USE some particular 'function' or 'attachment'? The list is configured to only pass/permit attachments of :
multipart/mixed multipart/alternative text/plain text/html
- Charles
On Mon, 30 Oct 2006, Charles Gregory wrote:
Traceback (most recent call last): File "/var/mailman/cron/senddigests", line 94, in ? main() File "/var/mailman/cron/senddigests", line 86, in main mlist.send_digest_now() File "/var/mailman/Mailman/Digester.py", line 60, in send_digest_now ToDigest.send_digests(self, mboxfp) File "/var/mailman/Mailman/Handlers/ToDigest.py", line 123, in send_digests send_i18n_digests(mlist, mboxfp) File "/var/mailman/Mailman/Handlers/ToDigest.py", line 295, in send_i18n_digests msg = scrubber(mlist, msg) File "/var/mailman/Mailman/Handlers/Scrubber.py", line 252, in process payload = part.get_payload(decode=1) File "/var/tmp/mailman-root/var/mailman/pythonlib/email/Message.py", line 189, in get_payload File "/var/tmp/mailman-root/var/mailman/pythonlib/email/Utils.py", line 75, in _bdecode File "/usr/lib/python2.2/base64.py", line 44, in decodestring return binascii.a2b_base64(s) binascii.Error: Incorrect padding
Thanks,
- Charles
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/cgregory%40hwcn.org
Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
Charles Gregory wrote:
Additional note: I'm now digging through the archives (and having better luck finding 'incorrect padding' as a search term).
It looks like it is caused by an attachment coding prob? Makes me wonder why I am running into it now after years of successful posts?
IIRC, this is fixed in recent versions, but since you asked us not to suggest upgrading, I won't bother to look up the detail.
I think the error comes from a messahe part that has Content-Transfer-Encoding: base64 and has incorrect padding at the end. You haven't seen it before, because it is the result of an encoding error by one person's broken MUA or possibly a message garbled in transit.
You have to find the problem message which will be in some list's lists/listname/digest.mbox file and edit the file to either fix or remove the problem message. The list will be the first one in alphabetical order that isn't getting it's periodic digests.
Is it possible I could just tell list members to NOT USE some particular 'function' or 'attachment'? The list is configured to only pass/permit attachments of :
multipart/mixed multipart/alternative text/plain text/html
I don't think you need to do that. You'll know more when you find the bad message.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
My list is administrator-controlled, rather than recipient controlled, to add members to a list.
I have not found any way to enter both an email address and a "plain-language name" in the space provided, in a single transaction. Any ideas?
Thanks.
Larry Israel
Larry Israel wrote:
I have not found any way to enter both an email address and a "plain-language name" in the space provided, in a single transaction. Any ideas?
See <http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq03.044.htp>.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mark Sapiro writes:
You have to find the problem message which will be in some list's lists/listname/digest.mbox file and edit the file to either fix or remove the problem message.
Note that fixing the message is a matter of adding or removing a few "=" at the end of a BASE64-encoded text.
Since it's in a body part, look for a header that says
Content-Transfer-Encoding: base64
Following that header section there will be a body part of long lines of random-looking characters with no spaces in them and very few punctuation characters. Most mailers produce lines of 64 characters (IIRC), so to check the length-multiple-of-4 constraint, just look at the last line. It should end with 0, 1, or 2 "=" signs as padding to make it a multiple of 4 (there's a technical reason why 3 is impossible).
As long as you don't do *anything else* to the file, adding or subtracting "=" as described here cannot make the situation worse. :-)
[[ For completeness, if had been in a header, you'd be looking for a "MIME encoded word" which looks like
=?ENCODING?B?BASE64-characters-length-multiple-of-4?=
The "=?" prefix, "?" separators, and "?=" are literal. The "ENCODING" depends on character set used, the "B" means "BASE64", and the rest is encoded content. If the "BASE64-characters-length-multiple-of-4" part is not a multiple of 4, then it should end with "=" pad characters, either 1 or 2. ]]
HTH
Steve
Hi and thanks!
On Mon, 30 Oct 2006, Mark Sapiro wrote:
I think the error comes from a messahe part that has Content-Transfer-Encoding: base64 and has incorrect padding at the end. You haven't seen it before, because it is the result of an encoding error by one person's broken MUA or possibly a message garbled in transit.
(nod) That is what I gathered from the web. But it keeps happening every day. And thanks to your next comment I figured it out.....
You have to find the problem message which will be in some list's lists/listname/digest.mbox file and edit the file to either fix or remove the problem message. The list will be the first one in alphabetical order that isn't getting it's periodic digests.
THANKS! I keep forgetting that apart from our main list we have a couple of other small 'unused' ones. Unused, except that they attract the occasional piece of spam! While the digest.mbox for the main list was cycling properly, the digest.mbox for one of the smaller ones was 'stuck' starting with the date the error appeared!
Fortunately no one gets the digest on that list, so I just trashed it. And I am also happy because this means there is no 'regular poster' on the main list using a broken MUA. (wipe brow with relief)
Excellent! So the cause was what I thought. I just had to look in the right list for the 'bad' message. Thanks again!
- Charles
participants (4)
-
Charles Gregory -
Larry Israel -
Mark Sapiro -
stephen＠xemacs.org