On Sat, Jan 12, 2002 at 05:58:56PM +0100, Roman Neuhauser wrote: > Hi there, > > some time ago I reported problems with mailcap handlers for tar.(gz|bz2) > files. I didn't investigate it further until yesterday when I tried (and > failed) to get mutt recognize a file by its extension no matter where I > put the ext -> MIME type mapping (i. e. /usr/local/etc/mime.types or > ~/.mime.types). > > I got really bothered by this, and run mutt in strace. While I could see > mutt opening ~/.mailcap, there was no mention of mime.types. So I got > mutt log debug info, but this didn't show mutt using mime.types either. > Might be the right piece of code doesn't call the dprint() macro; the > only place where the code mentions mime.types is check_mime_type() in > sendlib.c, however. Plus, it looks like this function is only called > when you *compose* a message (because then I get the right content > type). > > So... could someone point me to the function which mutt uses to > determine the MIME type of the attachments when you view a message?
I've always believed that the mime type of an attachment was actually stored in the mime headers and so was independant of the file name. Of course when composing a message, mutt needs a method of mapping extensions to mime types and so uses mime.types, but when viewing a message this is unnecessary. -- Benjamin Smith <[EMAIL PROTECTED], [EMAIL PROTECTED]>
msg23013/pgp00000.pgp
Description: PGP signature
