Hi,
I'm a long-time Mutt user, and have been very happy with it.
I recently encountered an issue with an attachment failing to properly decode
when saving it from Mutt.
To save the attachment from Mutt, I navigated to the e-mail message, typed 'v'
to view the different parts of that particular e-mail message, then used arrow
keys to nagivate to the appropriate section, and finally typed 's' to save it.
I think I've identified the issue, but my question is: is this a bug or
expected behavior?
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
If I change the type to anything other than text/plain (I've only tried a
couple of other types), then Mutt properly decodes/saves the attachment.
If I save it when the type is text/plain, then \r\n sequences end up getting
shortened to just \n (which is obiously bad when the data is a zip file).
The original e-mail appears to have been generated via an automated process,
and not through a common e-mail client.
I've replicated this issue in the Mutt client that comes with Ubuntu 22.04
(version 2.1.4) as well as Ubuntu 24.04 (version 2.2.12)
If this is considered a bug, I can provide a sanitized MBOX-format version of
an e-mail that triggers this issue. Gzipped and base64-encoded, it's less than
900 bytes.
Thanks,
- Daniel
