[Mailman-Developers] digest problems (anyone seen this?)

[Barry Warsaw]

On Wed, 2003-08-06 at 18:48, Chuq Von Rospach wrote:

> So it seems to be Mailman making an unsafe assumption about how the 
> MIME is constructed, not a problem with an incoming message.
> 
> Barry? What's your thought here?

If it's really the digest.mbox file that's busted here (and you can
check by looking at lists/<yourlist>/digest.mbox before the next digest
is sent out), then it's likely something in the scrubber.  Try to find
the matching offending message in your archive's .mbox file and send me
a copy of that.  I'll run it through my own scrubber and see what
happens.

If the scrubbing leaves the text/plain payload without a trailing
newline then indeed it will get into the digest.mbox file that way, and
that will screw up the digest parsing later.  In that case, then the
following (untested) patch might do the trick.

If this patch works, then I'll probably apply it as a fallback, but I'll
want to make sure the scrubber is fixed too, otherwise it's possible
that your mbox archive is also broken (though you wouldn't notice it
until you regenerated your pipermail archives).

-Barry

-------------- next part --------------
A non-text attachment was scrubbed...
Name: ToDigest.py-patch.txt
Type: text/x-patch
Size: 967 bytes
Desc: not available
Url : http://mail.python.org/pipermail/mailman-developers/attachments/20030806/be3adca6/ToDigest.py-patch.bin