Re: Attachment decode issue
Kurt Hackenberg <[email protected]> Fri, 28 Mar 2025 19:08:52 -0400
| Newsgroups | gmane.mail.mutt.user |
|---|---|
| Message-ID | <[email protected]> |
On Fri, Mar 28, 2025 at 05:49:24PM -0400, Kurt Hackenberg wrote: >>Background: I received an e-mail with an attached ZIP file >>(base64-encoded), where the attachment had the following mime headers: >> Content-Type: text/plain; name="name.zip" >> Content-Transfer-Encoding: base64 > >I think that's a bug in the software that generated the message, not a >bug in Mutt. That Content-Type: is wrong. It should be application/zip >if that exists, else application/octet-stream. Application/zip exists, and has since 1993. <https://www.iana.org/assignments/media-types/media-types.xhtml> This message has a small zip file attached, unless the mailing list software stripped it off. Anyway, Mutt automatically generated: Content-Type: application/zip Content-Disposition: attachment; filename="five.zip" Content-Transfer-Encoding: base64 You could do the same test -- attach a zip file to a message -- with Mutt or any mail reader.
five.zip
(application/zip, 374 B) - not displayed