|
From: Tom H. <to...@co...> - 2009-01-15 14:44:56
|
Rich Coe wrote: > aha. > It has an invalid mime-encoded header. > > Here are the relevant parts: > In the header: > # Content-Type: multipart/mixed; > # boundary="----=_NextPart_000_1230E45_01C975FB.0A21E221" > > In the body: > # This is a multi-part message in MIME format. > # > # ------=_NextPart_000_1230E50_01C975FB.13F78D21 > [...] > # ------=_NextPart_000_1230E50_01C975FB.13F78D21-- > # ------=_NextPart_000_1230E45_01C975FB.0A21E221-- When it got to you maybe, it was fine when it left here, and when my copy came back from the list... When today's one for mg left here it looked like this: Content-Type: multipart/mixed; boundary="----------=_1231990307-24921-0" Content-Transfer-Encoding: binary MIME-Version: 1.0 ... ------------=_1231990307-24921-0 Content-Type: text/plain; name="final" Content-Disposition: inline; filename="final" Content-Transfer-Encoding: 7bit ... ------------=_1231990307-24921-0 Content-Type: text/plain; name="diffs" Content-Disposition: inline; filename="diffs" Content-Transfer-Encoding: 7bit ... ------------=_1231990307-24921-0-- What came back from the list was the same, with the same delimiter string, except for the addition of two sections to hold the SF advert and the mailing list signature. My guess would be that the list mail, on it's way to you, passed through a broken gateway that pulled the mail apart and put it back together with different (and broken) delimiters. I've seen numerous commerical mail gateway/firewall things do such things (and far, far worse) in the past. Tom -- Tom Hughes (to...@co...) http://www.compton.nu/ |