[ mailman-Bugs-1536532 ] digest mails: RFC2046 non-compliance

Bugs item #1536532, was opened at 2006-08-08 11:40 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1536532&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Colin Leroy (colinleroy) Assigned to: Nobody/Anonymous (nobody) Summary: digest mails: RFC2046 non-compliance Initial Comment: Hi, Mailman 2.1.6 does not respect RFC2046 when sending out digests: the end boundary of the last inner digested mail is not separated from the separator boundary between the multipart/digest main part and footer part, as described on http://www.thewildbeast.co.uk/sylpheed-claws/bugzilla/show_bug.cgi?id=998 See the attachments (broken email, hand-fixed email and diff between the two). The relevant part of RFC2046 is: RFC 2046 - page 19: NOTE: The CRLF preceding the boundary delimiter line is conceptually attached to the boundary so that it is possible to have a part that does not end with a CRLF (line break). Body parts that must be considered to end with line breaks, therefore, must have two CRLFs preceding the boundary delimiter line, the first of which is part of the preceding body part, and the second of which is part of the encapsulation boundary. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1536532&group_id=103
participants (1)
-
SourceForge.net