[Mailman-Users] cron/senddigests - error
mark at msapiro.net
Thu Feb 7 23:33:12 CET 2008
Stephen J. Turnbull wrote:
>Con Wieland writes:
> > version 2.1.4
> > The odd thing though is it has only been happening the last couple of
> > weeks
>Could be due to a new poster with a busted MTA, or an old poster with
>a busted MTA who recently started using non-ASCII in MIME headers.
>Maybe it's fixed in recent Mailman, Mark or Tokio will probably
>remember, or you could look through the changelogs (browsable with
>bzr, I should think) for "2231" which will probably pop it up.
Actually, it's fixed in the Python email library. The problem is
discussed in the thread starting at
is fixed in email 2.5.8 which shipped with Mailman 2.1.9.
In any case, Con's problem is almost certainly caused by a message in
the list's digest.mbox file that has an apostrophe (') in either a
long subject or a long attachment filename.
I can't tell from the error trace which list is involved, but you can
do something like
find ~mailman/lists/ -name digest.mbox -print
to find which lists have digests pending, and then run
~mailman/cron/senddigests -l listname
on each in turn until you find the offending list. From there, you have
to edit the digest.mbox to remove the extra apostrophe from the rfc
2231 encoded header.
Note that the apostrophe in the header is not wrong, but prior to email
2.5.8, it would confuse the email.Utils.decode_rfc2231 function
causing the error.
Mark Sapiro <mark at msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
More information about the Mailman-Users