Re: Handling attached .eml files

[Kyle Wheeler <kyle-mutt@xxxxxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Saturday, March  8 at 02:42 AM, quoth Gary Johnson:
> But those steps tell mutt how to use an _external_ application, as 
> specified in the mailcap file, to view the message.  Mutt doesn't 
> look at the content type associated with the extension to see if it 
> knows how to handle that content type internally.  I think that's a 
> weakness of the mime_lookup feature.
>
> I already have step 1 in my muttrc and I added step 2 to my 
> mime.types file just to see what would happen.  The results were the 
> same as before.

Darn. Well then you could always edit the message with a text editor 
(press 'e') to manually change application/octet-stream to 
message/rfc822.

>   There is nothing wrong with forwarding.
>   Other option is use outlook.

Well... I suppose technically, they may be right. As far as I can 
tell, EML files are not *guaranteed* to be compliant with 
message/rfc822 mime-type requirements (e.g. line endings, that sort of 
thing). Given that, unless you've done more extensive checking of the 
file's innards to ensure compliance, the best way to send an EML file 
is as an application/octet-stream, which doesn't help anybody.

It may be worth filing an enhancement request at http://bugs.mutt.org, 
but given how rare, microsoft-centric, and nonstandard EML files 
are... it may not be worth the time and trouble to the developers. But 
it's worth a shot.

~Kyle
- -- 
Beauty is in the eye of the beholder and it may be necessary from time 
to time to give a stupid or misinformed beholder a black eye.
                                                          -- Miss Piggy
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!

iD8DBQFH0rFxBkIOoMqOI14RAiwTAKDeGwwyIIjbxXTuAm7TUMmSn/RxngCghmO3
TS9ONWcA/JUXXOqcoKeXGNs=
=Fyib
-----END PGP SIGNATURE-----