I got a message with no text in the message body and a ZIP file attached. The list showed "yes" for attachments, so that was alright. But when I clicked on the message to see it in the preview window, MWP showed the contents of the ZIP file (which was unreadable of course, but still).

I guess that if there would have been a single space in the message body, this would not have happened. Haven't tested that, though...

Jerry

And your point is ... what? What I'm "hearing" is that you recevied an improperly formatted message (might even be the same one I got yesterday.) How does that constitute a "bug" in MW?

I could have and should have a little bit more clear here. I meant that the bug - admittedly a little one, so the term 'buglet' is more appropriate - is that MW doesn't recognize the divider between the message and the attachment when the message is empty.

<blush>Ahem, I now see I even typed the word 'BUG' in capitals... Sorry!</blush>

Jerry

Jerry,
   No offense taken. I'm still confused though, as to whether there was a divider between the message and the attachment or not. Which is to say, there's supposed to be a blank line between the header and the body, then with an attachment there should have also been a multipart-header which would specify the delimiter for the attachment.
   It is known that MWP will behave as you say if the blank line between header and body is missing, and there's really not much that could be done about that. But if there was a multipart header, then I would agure that MWP could see that and assume a null body, which would be better than trying to display a .zip or any other attachment.
   And while that still may not be a bug per se, it might be nice to handle it anyway.

I'll run some tests and see if there is any difference with attachment types or things like an empty body and a body consisting of a single space. The message was sent from Outlook by the way, using plain text format.