Hi,
In the past couple of days I've been hit by this behaviour. I'm using
mutt 1.5.21 compiled from scratch. Suppose that I receive a mail with
several attachments:
I 1 <no description> [multipa/alternativ, 7bit, 7.2K]
I 2 ├─><no description> [text/plain, 7bit, iso-8859-1, 0.7K]
I 3 └─><no description> [text/html, 7bit, iso-8859-1, 6.3K]
A 4 file.txt [text/plain, 8bit, us-ascii, 2.3K]
A 5 file.xml [text/xml, 8bit, us-ascii, 0.1K]
A 6 file.pdf [text/x-unknown-, base64, us-ascii, 66K]
The message has 3 attachments, one text file, one xml document and one
pdf document. This is a real example, and the sender MUA is Thuderbird
3.1.18. It turns out that the sender MUA got it wrong, and the character
encoding is wrongly set (us-ascii), but:
- file.txt is utf-8 encoded
- file.xml is also utf-8 encoded. Besides, the xml declaration says
the document is indeed utf-8 encoded:
% head -n 1 file.xml
<?xml version="1.0" encoding="utf-8"?>
- file.pdf is a pdf document.
The problem is that there is no way to save these attachment
properly. For instance, when saving file.xml all the non ascii
characters are replaced with "?". So if file.xml originally was:
<?xml version="1.0" encoding="utf-8"?>
<a>©Áéñio</a>
After saving to disk it becomes:
<?xml version="1.0" encoding="utf-8"?>
<a>????????io</a>
The same happens with the text file. Even the pdf document is wrongly
saved. The only way to actually get the original content of the
attchments is to manually set the mime type (using ctrl-e) to
"application/octet-stream", and then saving them to disk.
So my question is: is any way to tell mutt "ok, the mime information may
be wrong. In any case, I want you to save the attachment as-is to the
disc, i.e. without any translation etc".
thanks,
aitor
