Geert Uytterhoeven dixit:
I used "git format-patch" to create a patch, which contains a.o. the following headers: | Content-Type: text/plain; charset=UTF-8 | Content-Transfer-Encoding: 8bit
Yes, but that will not pass through all SMTP servers, since 8bit is an optional extension which, for example, exim4 does not support¹ by default, and other servers² can be configured to be strict, too (or simply not show³ 8BITMIME support). […]
No Base64 or QP involved.
Yes, but you cannot _depend_ on that. ① exim4 can be configured to either display 8BITMIME in the EHLO response or not, but that doesn’t change its handling – it’s simply oblivios of whether the message contains 8bit or not, just passes them on in either case (violating the SMTP RFC) ② for curiosity reasons, I run such servers ③ e.g. those that don’t do EHLO at all; I *bet* there are still commercial SMTP implementations like that around bye, //mirabilos -- “It is inappropriate to require that a time represented as seconds since the Epoch precisely represent the number of seconds between the referenced time and the Epoch.” -- IEEE Std 1003.1b-1993 (POSIX) Section B.2.2.2 -- To unsubscribe from this list: send the line "unsubscribe linux-m68k" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
