Brian Craft <[EMAIL PROTECTED]> wrote:
>
> Is there any way to debug mutt's reading of mime types, or dump what
> mime types it knows?
I was under the impression that Mutt doesn't know about ANY mime types
other than text/{plain,enriched} internally. Everything else comes from
the mailcap files.
> I've been trying for an hour to get it to add one mime type, and the
> result is always the same: "MIME type not defined. Cannot view
> attachment." I've tried adding it to ~/.mime.types and
> /etc/mime.types. Both work for Netscape.
mime.types files tell Mutt (and Netscape!) that, if a file ends with a
particular extension, (such as ".doc"), that it can be considered to be
a particular MIME type (such as "application/msword"). They do not tell
Mutt (or Netscape) what to do with such a document. You see? They are
ways of finding out the MIME type when the type is not known. But when
you receive an E-mail attachment, the MIME type *is* known, so Mutt
doesn't look at the mime.types file at all. It looks at the mailcap
files instead; this is where you must put your type definitions (for
both Mutt and Netscape).
--
David DeSimone | "The doctrine of human equality reposes on this:
[EMAIL PROTECTED] | that there is no man really clever who has not
Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson
Convex Division | PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
