… keyword and value. 11. The UTF8SMTP extension is valid on the submission port [RFC4409]. 3.2. The UTF8SMTP Extension An SMTP server that announces this extension MUST be prepared to accept a UTF-8 string [RFC3629] in any position in which RFC 2821 specifies that a mailbox can ap…

…message store user agents (MUAs) to manipulate email messages after delivery. [ RFC4409 ] defines a "profile" of the SMTP service that is specifically used for message submission. MUAs are expected to submit messages to mail submission agents (MSAs) using this approach. RFC2782 ]…

…S keyword and value. 11. The UTF8SMTP extension is valid on the submission port RFC4409 ]. 3.2 . The UTF8SMTP Extension An SMTP server that announces this extension MUST be prepared to accept a UTF-8 string [ RFC3629 ] in any position in which RFC 2821 specifies that a mailbox ca…

…ings have used SMTP RFC5321 ]. The standard currently preferred is SUBMISSION [ RFC4409 ]. Although SUBMISSION derives from SMTP, it uses a separate TCP port and imposes distinct requirements, such as access authorization. Crocker Informational [Page 31] RFC 5598 Email Architectu…

…n easily imagine modifications to message submission servers (as described in [ RFC4409 ]) so that they would perform downgrading, or perhaps even upgrading, operations, receiving messages with one or more of the internationalization extensions discussed here and adapting the out…

…empts by intermediaries to correct or interpret such content. See Section 8 of [RFC4409] for examples of changes that are commonly made. Such "corrections" may invalidate DKIM signatures or have other undesirable effects, including some that involve changes to the way a message i…

…n easily imagine modifications to message submission servers (as described in [ RFC4409 ]) so that they would perform downgrading, or perhaps even upgrading, operations, receiving messages with one or more of the internationalization extensions discussed here and adapting the out…