I am not tacking a new problem onto an old thread!
I am adding info I noticed when this problem just popped up again:
The culprit is Outlook, but knowing outlooks gig, Zimbra may make allowances, until microsoft stops shipping the product. (I HATE outllook, I hate using it, I hate supporting it. I need either Migrane medicine to deal with outlook, or better yet, Uninstall!)
Anyhow OTHERS use Outlook and forward emails to our users.
The attachement comes as an Envelope Icon with a name, but no extension.
This leads to the pop up issue I was discussing above.
You can see contents of the attachment by right clicking on the Fragment of the message and clicking show original.
The attachment, is simply the stripped text of the previous message (and forwards if it has been forwardedforwardedforwarded) but it is encapsulated with:
Rather than just adding the content to the body of the forwarded message as zimbra does, it takes the content, and turns it into attachments... which with no extension, zimbra doesnt know how to handle.
Content-Type: text/plain; charset=utf-8
<body content here>
<additional content here>
My workaround for now was to tell all staff via emal that if they get an email forwarded to them from outside, and it has an attachement that has no extension, to right click on the fragment and choose show original.
What I wanted to say was "friends dont let friends use Outlook" but that is another story...