Bitmessage echo server12/28/2022 This seems to be of little practical relevance given that most servers apparently accept 8-bit messages by default even if the argument is missing. Unless mail.strictly_mime is set, messages beyond the ASCII range are sent as 8-bit messages (at least in the text/plain part).įurthermore, the BODY=8BITMIME parameter isn't sent with the MAIL request, thus the server may not know that an 8-bit message is coming. The SMTP implementation in MailNews Core still ignores the 8BITMIME response to an EHLO greeting, thus won't care whether or not the server actually supports 8-bit body encoding. > parameter must appear after the address. > command is identical to the MAIL command in, except that a BODY > arbitrary lines of octet-aligned material. > to transmit a content body consisting of a MIME message containing > The extended MAIL command is issued by a client SMTP when it wishes > command and will accept MIME messages containing arbitrary octet. > then the server SMTP is indicating that it supports the extended MAIL > command, and the response includes the EHLO keyword value 8BITMIME, #Bitmessage echo server code#> the server SMTP responds with code 250 to the EHLO > for such capability with BODY=8BITMIME clause at the "MAIL FROM:" > Server puts capability flag 8BITMIME as I see in logs, but client should ask (Quoting Alexei from bug 800877 comment #4) +++ This bug was initially created as a clone of Bug #800877 +++
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |