Home > smtp envelope > rfc smtp error codes

Rfc Smtp Error Codes

Simple Mail Transfer Protocol Status of This Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization email address rfc state and status of this protocol. Distribution of this memo is unlimited. Abstract This document smtp rfc 5321 is a specification of the basic protocol for Internet electronic mail transport. It consolidates, updates, and clarifies several previous documents, making all email rfc 822 or parts of most of them obsolete. It covers the SMTP extension mechanisms and best practices for the contemporary Internet, but does not provide details about particular extensions. Although SMTP was designed as a mail transport and

Smtp Envelope Vs Header

delivery protocol, this specification also contains information that is important to its use as a "mail submission" protocol for "split-UA" (User Agent) mail reading systems and mobile environments. Klensin Standards Track [Page 1] RFC 5321 SMTP October 2008 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5 1.1. Transport of Electronic Mail smtp data command . . . . . . . . . . . . . . . 5 1.2. History and Context for This Document . . . . . . . . . . 5 1.3. Document Conventions . . . . . . . . . . . . . . . . . . . 6 2. The SMTP Model . . . . . . . . . . . . . . . . . . . . . . . . 7 2.1. Basic Structure . . . . . . . . . . . . . . . . . . . . . 7 2.2. The Extension Model . . . . . . . . . . . . . . . . . . . 9 2.2.1. Background . . . . . . . . . . . . . . . . . . . . . . 9 2.2.2. Definition and Registration of Extensions . . . . . . 10 2.2.3. Special Issues with Extensions . . . . . . . . . . . . 11 2.3. SMTP Terminology . . . . . . . . . . . . . . . . . . . . . 11 2.3.1. Mail Objects . .

(213) 822-1511 RFC 821

Smtp Rcpt To Multiple Recipients

August 1982 Simple Mail Transfer Protocol TABLE OF CONTENTS 1.

Smtp Envelope Structure

INTRODUCTION .................................................. 1 2. THE SMTP MODEL ................................................ 2 3. THE SMTP PROCEDURE ............................................ 4 https://tools.ietf.org/html/rfc5321 3.1. Mail ..................................................... 4 3.2. Forwarding ............................................... 7 3.3. Verifying and Expanding .................................. 8 3.4. Sending and Mailing ..................................... 11 3.5. Opening and Closing ..................................... 13 3.6. Relaying ................................................ 14 https://tools.ietf.org/html/rfc821 3.7. Domains ................................................. 17 3.8. Changing Roles .......................................... 18 4. THE SMTP SPECIFICATIONS ...................................... 19 4.1. SMTP Commands ........................................... 19 4.1.1. Command Semantics ..................................... 19 4.1.2. Command Syntax ........................................ 27 4.2. SMTP Replies ............................................ 34 4.2.1. Reply Codes by Function Group ......................... 35 4.2.2. Reply Codes in Numeric Order .......................... 36 4.3. Sequencing of Commands and Replies ...................... 37 4.4. State Diagrams .......................................... 39 4.5. Details ................................................. 41 4.5.1. Minimum Implementation ................................ 41 4.5.2. Transparency .......................................... 41 4.5.3. Sizes ................................................. 42 APPENDIX A: TCP ................................................. 44 APPENDIX B: NCP .....................................

Sub-Codes Registration Procedure(s) Specification Required Expert(s) Chris Newman Reference [RFC5248] Available Formats CSV Code Summary Description Reference Submitter Change Controller 2.XXX.YYY Success Success specifies that the DSN is reporting a positive delivery action. Detail sub-codes http://www.iana.org/assignments/smtp-enhanced-status-codes/smtp-enhanced-status-codes.xhtml may provide notification of transformations required for delivery. [RFC3463] (Standards track) G. Vaudreuil IESG 4.XXX.YYY Persistent Transient Failure A persistent transient failure is one in which the message as sent is valid, but persistence of some temporary condition has caused abandonment or delay of attempts to send the message. If this code accompanies a delivery failure report, sending in the future may be successful. smtp envelope [RFC3463] (Standards track) G. Vaudreuil IESG 5.XXX.YYY Permanent Failure A permanent failure is one which is not likely to be resolved by resending the message in the current form. Some change to the message or the destination must be made for successful delivery. [RFC3463] (Standards track) G. Vaudreuil IESG Subject Sub-Codes Registration Procedure(s) Specification Required Expert(s) Chris Newman Reference [RFC5248] Available Formats CSV Code Summary rfc smtp error Description Reference Submitter Change Controller X.0.YYY Other or Undefined Status There is no additional subject information available. [RFC3463] (Standards track) G. Vaudreuil IESG X.1.YYY Addressing Status The address status reports on the originator or destination address. It may include address syntax or validity. These errors can generally be corrected by the sender and retried. [RFC3463] (Standards track) G. Vaudreuil IESG X.2.YYY Mailbox Status Mailbox status indicates that something having to do with the mailbox has caused this DSN. Mailbox issues are assumed to be under the general control of the recipient. [RFC3463] (Standards track) G. Vaudreuil IESG X.3.YYY Mail System Status Mail system status indicates that something having to do with the destination system has caused this DSN. System issues are assumed to be under the general control of the destination system administrator. [RFC3463] (Standards track) G. Vaudreuil IESG X.4.YYY Network and Routing Status The networking or routing codes report status about the delivery system itself. These system components include any necessary infrastructure such as directory and routing services. Network issues are assumed to be under the control of the destination or intermediate system administrator. [RFC3463] (Standards track) G. Vaudreuil IESG X.5.YYY M

Related content

rfc smtp error messages
Rfc Smtp Error Messages p Simple Mail Transfer Protocol Status of This Memo This document specifies an Internet standards track protocol for the Internet community and requests discussion and suggestions for improvements Please refer to the current edition of the Internet Official Protocol Standards STD for the standardization state and status of this protocol Distribution of this memo is unlimited Abstract This document is a specification of the basic protocol for email address rfc Internet electronic mail transport It consolidates updates and clarifies several previous documents making all or parts of most of p Email Rfc p them obsolete It