On Wed, Dec 05, 2012 at 01:34:29PM +0000, ed wrote:
I have a weird setup where any UTF message causes me to create a Content-Type of text/plain; 8bit, unknown. Is it possible to make a hook which sets the Content-Type to text/plain; 8bit, us-ascii after editing? I figure this should be simpler than correcting the underlying problem in this particular environment.
If there are non-ascii characters in the message, then us-ascii would not be the appropriate charset. The default value of $send_charset is "us-ascii:iso-8859-1:utf-8", which causes Mutt to try and convert your message to the first charset in that list that is applicable.
To answer your question, there is no hook for changing the content type. You would have to manually edit it.
