[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Nmh-workers] whatnow: can't attach because no header field name was

From: Ken Hornstein
Subject: Re: [Nmh-workers] whatnow: can't attach because no header field name was given.
Date: Thu, 15 Mar 2012 09:23:45 -0400

>Is the attach command of whatnow making no attempt whatsoever to try
>to determine the correct MIME content type specification?  Is every
>attachment just going to be sent as "application/octet-stream"?

Dude, you make it seem like using application/octet-stream is an
injustice on par with the imprisonment of Alfred Dreyfus or an
Acadmey Award being given to Marisa Tomei.  I don't think it's
unreasonable to use if nmh doesn't know how to handle a content

The send(1) man page explains how nmh can be configured to map
particular suffixes to MIME content types when using atttach (although
it's brief and probably should contain a reference to the mhshow(1)
man page for the exact syntax).

Should nmh have some better defaults?  Probably.  In fact ... I forget
we have mhn.defaults.  I could populate that with a few more things
(in fact, our defaults are kinda cruddy, now that I look at them).
But you can fix this yourself in your .mh_profile for at least some
common types.  Something else for the 1.5 list :-/


reply via email to

[Prev in Thread] Current Thread [Next in Thread]