Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

When opening attachments within VUwebmail, the filenames get lost and only the extension remains. If I open the attachment with Mulberry, the filenames are there. What gives?

0
Posted

When opening attachments within VUwebmail, the filenames get lost and only the extension remains. If I open the attachment with Mulberry, the filenames are there. What gives?

0

The difference is the client-side handling of the MIME type. MIME (Multipurpose Internet Mail Extensions) extends the format of Internet mail to allow non-US-ASCII textual messages, non-textual messages, multipart message bodies, and non-US-ASCII information in message headers. Your browser preserved the extension because that’s probably how it determined MIME type (some browsers do it differently, not all alike). The funky file name is the local temp swap/space file name created on the fly to store the file once the browser downloaded locally to pass off to your local app for the determined MIME type. Mulberry (or any other Fat client) is going to handle passing a file (piece of attached content) to a local app differently, relying usually on the OS to determine mime type. Also, depending on how your mailboxes are established in Mulberry, the attached files (your entire message) may have already been downloaded locally, hence no need to temp swap/space file naming.

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.