Hi, * Kyle Wheeler [07-09-18 09:27:06 -0500] wrote:
On Tuesday, September 18 at 09:03 AM, quoth Mutt:
On the other hand, the question is what to do when all charsets in $send_charset fail and $charset does not match an officially assigned charset name, like in your case.
The options are 1) go ahead with a charset possibly not supported on the receiving side or 2) go ahead with a possible broken encoding in a valid charset.
There's also option 3) refuse to send the mail, and display an error message. I prefer this option. I don't like the idea of mutt being a potential source of bad email.
With messages created from scratch locally that could be an option (or at least issue a warning). But given you received a mail with a broken encoding already, 3) would mean you couldn't reply to it unless you manually fix the encoding.
I didn't look at the source yet to see if a prompt would be possible to choose between 2) and 3) though (for mailx mode, you wouldn't want to interrupt with a prompt).
bye, Rocco -- :wq!