Re: [Nmh-workers] When send does not recognize a mime type

[Ken Hornstein]

>Could send have an option that makes an unrecognized mime type an error?

I assume you mean an unrecognized file extension, because the MIME types
are kinda arbitrary and new ones are being added all of the time.

Do you really want that?  If a file is "unknown", the RFCs say that
the MIME type should fall back to application/octet-stream, and we do that.
I'm on the fence about the behavior where it attempts to auto-detect text,
but I see the utility there.  I'm just trying to understand why this would
be a good thing; I think send should generally try really hard to work
unless there are errors in the transport system.

--Ken