The existing code takes a non-ASCII message body and sends it as an attachment
of type application/octet-stream.
Your patch changes this behavior so that it is sent as type text/plain with the
appropriately chosen character set.
You know .... I'm all for backwards compatibility and everything, but
I'm wondering ... did the previous behavior actually make sense? Can
people argue that it was desirable or correct? Or was the previous
behavior actually wrong, and this is really fixing a long-standing
bug? Because if we decide that the previous behavior is a bug, then
I don't think an explicit enable option for this chance makes sense; I'd
prefer that the new behavior be the default.
(I am personally on the fence regarding whether or not the previous
behavior is a bug).
--Ken
_______________________________________________
Nmh-workers mailing list
Nmh-workers(_at_)nongnu(_dot_)org
http://lists.nongnu.org/mailman/listinfo/nmh-workers