Steffen Nurpmeso wrote in <20230920214009.w5mrf%stef...@sdaoden.eu>: |Ingo Schwarze wrote in | <zqrdqncxfvpfh...@asta-kit.de>: | ... ||I just checked - even though i'm using the higer-level mutt(1) MUA ||most of the time and even though the shell i'm starting mutt(1) from ||has LC_CTYPE=C.UTF-8 set on that particular machine, the last sixteen ||mails i sent all contained the explicit header || || Content-Type: text/plain; charset=us-ascii || ||and intentionally so. Yes, i do occasionally send UTF-8 mail on | |To be a hundred percent correct: MIME is not needed at all in that
That is to say, to be correct myself: like RFC 2045 says, "MIME defines a number of new RFC 822 header fields that are used to describe the content of a MIME entity". Yet if there is no MIME entity but only a plain RFC 822/2822/5322 internet message format, there is nothing to describe. [.]there are still circumstances in which it might be desirable for a mail-processing agent to know whether a message was composed with the new standard in mind. Therefore, this document defines a new header field, "MIME-Version", which is to be used to declare the version of the Internet message body format standard in use. Messages composed in accordance with this document MUST include such a header field, with the following verbatim text: But normally OpenBSD Mail does not, so no "MIME-Version: 1.0", because no The presence of this header field is an assertion that the message has been composed in compliance with this document. |case, unless a transfer-encoding had to be used (you do not show |that header), maybe because of overlong lines to-be-folded, or for |whatever reason. (But it is swallowed by consumers of course.) That would at least be my point of view. --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt)
