MH seems to detect MIME messages based on the existence of the
Content-Type field. I sometimes get mail that uses some odd, old
encoding that is not MIME, but that *does* have a Content-Type field.
MHN barfs on the mail because it attempts to parse the Content-Type
field based on rules that (I presume) are defined in the MIME RFC.
Here's my question: if MHN is only going to support MIME (which makes
sense), shouldn't it check for the existence of a MIME-Version header
instead of a Content-Type header?
What would be "really nice" is the ability to use MHN for MIME messages and
to specify an alternate "viewer" for messages with a Content-Type,
but no MIME-Version.
p.s. -- here's my current MH setup in case I'm just behind the times:
version: MH 6.8 #16[UCI] (daedalus.dcrt.nih.gov) of Mon Sep 13 13:41:45 EDT 1993
options: [ATHENA] [ATTVIBUG] [BIND] [BPOP] [BSD42] [BSD43] [FCNTL]
[FOLDPROT='"0711"'] [MHE] [MHRC] [MIME] [MSGPROT='"0600"']
[NNTP] [NTOHLSWAP] [OVERHEAD] [POP] [RENAME] [RPATHS] [SENDMTS]
[SUN40] [SUN41] [TYPESIG=int] [UNISTD] [VSPRINTF] [ZONEINFO]
Nat'l Insts. of Health, 12A/2033 UUCP: ...!uunet!nih-csl!weisen
Bethesda, MD 20892 Voice: 301/402-4030