On Sat, Nov 03, 2001 at 13:13:46 -0500, David T-G wrote:
> Bruno --
> 
> ...and then Bruno Postle said...
> % 
> % Am I the only person who got a huge windows virus tagged onto the end of
> % that email?
> 
> No; I got it, too (a 3060 line message is hard to miss).  Interestingly
> enough, though, I had to pump the message through less to find it, and
> then there were some other headers at the top.  To wit:
 
> I wonder why it didn't show up in the attachments list even though it
> looked like a valid MIME separator between the sig and this stuff...

Mutt doesn't show it because Mutt is MIME-compliant. The message just
had a huge (over 3000 lines!) epilogue, which it ignored as it should.

RFC 2046 says:

   There appears to be room for additional information prior to the
   first boundary delimiter line and following the final boundary
   delimiter line.  These areas should generally be left blank, and
   implementations must ignore anything that appears before the first
   boundary delimiter line or after the last one.

   NOTE:  These "preamble" and "epilogue" areas are generally not used
   because of the lack of proper typing of these parts and the lack of
   clear semantics for handling these areas at gateways, particularly
   X.400 gateways.  However, rather than leaving the preamble area
   blank, many MIME implementations have found this to be a convenient
   place to insert an explanatory note for recipients who read the
   message with pre-MIME software, since such notes will be ignored by
   MIME-compliant software.

Reply via email to