Ralph wrote:
Hi David,
If the server doesn't support 8BITMIME, fail with a message to user
that they need to encode the message for 7-bit transport. That
would be a change from current nmh behavior.
Current behaviour being it spots top-bit-set bytes and QPs or base64s?
As someone that pays for bandwidth by the byte, I'm all in favour of
more fully using all their bits. :-)
Actually, unencoded 8bit is used (by mhbuild) for non-ASCII text.
(It's used by send attach, and can be specified with mhbuild
directives.) That's no change from 1.6.
The issue is that post doesn't check if the SMTP server can handle
the 8-bit data. The change mentioned above is to fail if it can't.
David
_______________________________________________
Nmh-workers mailing list
Nmh-workers(_at_)nongnu(_dot_)org
https://lists.nongnu.org/mailman/listinfo/nmh-workers