plain text digest bug in appending messages

Bug #265893 reported by Rixhq
2
Affects Status Importance Assigned to Milestone
GNU Mailman
Fix Released
Medium
Unassigned

Bug Description

Sometimes, messages are incorrectly appended in the plain digests, which
cause 2 or more messages to be attached to 1. For example, I got a digest
which mentions one message in the Topic list, but at the end of this
message, the next message is "glued" to the bottom of it:

(...top of first message...)
---------------------------------
Do you Yahoo!?
Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!From
<email address hidden> Fri Mar 28 14:04:32 2003
Return-Path: <email address hidden>
Delivered-To: <email address hidden>
(...second message continues with all it's headers and content)

As you can see, the "From..." of the second message starts
directly after the last character of the first message.

Here's a second example:
(... top of first message...)
peace out:
-oscarFrom <email address hidden> Tue Apr 1 15:04:42 2003
Return-Path: <email address hidden>
Delivered-To: <email address hidden>
(..second message continues...)

Again, the "From..." from the next message is glued to the
previous message.

Is this a simple missing end of line issue or is it more complicated?
I can't seem to see a good pattern in it...

Ricardo.

[http://sourceforge.net/tracker/index.php?func=detail&aid=715581&group_id=103&atid=100103]

Revision history for this message
Fjpb (fjpb) wrote :

Is the first message originally in quoted-printable, with no
concluding blank line?

I have seen quite a lot of concatenated messages lately, and
in every instance that I've checked the first message is QP, is
multipart/alternative with the other part in html (stripped for
digest), and has the boundary immediately after the last line of
the QP part.

The problem affects MIME-digests as well as plaintext ones.

I have no clue how it might be fixed, or even where things are
going wrong, but maybe someone else can get a handle on it
from this info.

Revision history for this message
Ashawley (ashawley) wrote :

why was this bug closed, is it fixed in CVS?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.