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