Gordon Messmer writes:

It does here. You sent the message last time. From your original message, the headers are:

# ... # From: teleh0r <tele...@DOGLOVER.COM> # Subject: Remote buffer overflow in CrazyWWWBoard. # To: BUGT...@SECURITYFOCUS.COM # # --------------Boundary-00=_A2I2DLCMTNFX032YRX2X # Content-Type: text/plain; # charset="iso-8859-1" # Content-Transfer-Encoding: 8bit # # Dear, Bugtraq # # "Just little bits of history repeating" # # I have discovered a buffer overflow in CrazyWWWBoard Full Edition && # CrazyWWWBoard Limited Edition. # ...

After feeding it through reformime -r, this gets rewritten as:

# ... # # From: teleh0r <tele...@DOGLOVER.COM> # Subject: Remote buffer overflow in CrazyWWWBoard. # To: BUGT...@SECURITYFOCUS.COM # # This is a MIME-formatted message. If you see this text it means that your # E-mail software does not support MIME-formatted messages. # # --=_ny.email-scan.com-22688-986424098-0001-2 # Content-Type: text/plain; charset=iso-8859-1 # Content-Transfer-Encoding: 8bit # # ...

I should have mentioned that the MIME headers in the original ARE broken, but reformime coped with it. RFC 2045 is very clear that the newline immediately preceding a multipart boundary delimiter is a part of the boundary delimiter itself. In the original message there was a single blank line between the header, and the mime boundary delimiter. There must be two blank lines: one blank line to terminate headers from the body, and a second newline that precedes the multipart boundary delimiter that appears on the next line.