…8 Address Type "An Extensible Message Format for Delivery Status Notifications" RFC3464 ] defines the concept of an address type. The address format introduced in "Internationalized Email Headers" [ RFC6532 ] is a new address type. The syntax for the new address type in the conte…
…8 Address Type "An Extensible Message Format for Delivery Status Notifications" RFC3464 ] defines the concept of an address type. The address format introduced in "Internationalized Email Headers" [ RFC6532 ] is a new address type. The syntax for the new address type in the conte…
… MAIL FROM to be null, which is typical of some Delivery Status Notifications [ RFC3464 ], commonly called email bounces. In this case, the only entity available for performing an SPF check is the "HELO" identity defined in Section 1.1.4 . SPF functionality is enhanced by adminis…
…(envelope identifier) can be used for message-tracking purposes ([ RFC3885 ], [ RFC3464 ]) concerning a single posting/delivery transfer. The ENVID labels a single transit of the MHS by a specific message. So, the ENVID is used for one message posting until that message is delive…
… delivery notifications [ RFC3461 ], and the format of delivery notifications [ RFC3464 ]. These issues are discussed in a forthcoming document that will update those RFCs as needed [ EAI-DSN ]. 6.3 . Use of Email Addresses as Identifiers There are a number of places in contempor…
… notification process MUST conform to the requirements of RFC 5321 , RFC 3464 [ RFC3464 ], and RFC 6533 [ RFC6533 ]. o As specified in Section 2.2.3 of RFC 5321 , an SMTP client with additional information and/or knowledge of special circumstances MAY choose to requeue the messag…
…he notification process MUST conform to the requirements of RFC 5321, RFC 3464 [RFC3464], and RFC 6533 [RFC6533]. o As specified in Section 2.2.3 of RFC 5321, an SMTP client with additional information and/or knowledge of special circumstances MAY choose to requeue the message an…
… the notification process MUST conform to the requirements of RFC 5321 RFC 3464 RFC3464 ], and RFC 6533 RFC6533 ]. o As specified in Section 2.2.3 of RFC 5321 , an SMTP client with additional information and/or knowledge of special circumstances MAY choose to requeue the message …
…upport for internationalization of delivery and service notifications [ RFC3461 RFC3464 ], and (finally) a requirement for support of the 8BITMIME SMTP extension [ RFC6152 ] so that all of these can be transported through the mail system without having to overcome the limitation …
…y. Such notification MUST be done as specified in RFC 2821 [RFC2821], RFC 3464 [RFC3464], and the EAI delivery status notification (DSN) specification [RFC5337]. 3. It may find an alternate route to the destination that permits UTF8SMTP. That route may be discovered by trying alt…
… delivery notifications [ RFC3461 ], and the format of delivery notifications [ RFC3464 ]. These issues are discussed in a forthcoming document that will update those RFCs as needed [ EAI-DSN ]. 6.3 . Use of Email Addresses as Identifiers There are a number of places in contempor…
…ty. Such notification MUST be done as specified in RFC 2821 RFC2821 ], RFC 3464 RFC3464 ], and the EAI delivery status notification (DSN) specification [ RFC5337 ]. 3. It may find an alternate route to the destination that permits UTF8SMTP. That route may be discovered by trying …