email:smtp_transaction
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
email:smtp_transaction [2016/11/04 15:24] – peter | email:smtp_transaction [2019/11/27 22:09] (current) – removed peter | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Email - SMTP Transaction ====== | ||
- | Simple SMTP dialogue | ||
- | |||
- | ^ Client | ||
- | | Initiates a TCP connection to server. | ||
- | | Introduces itself by way of an Hello command, either HELO (now obsolete) or EHLO, followed by its own Fully Qualified Domain Name:\\ <WRAP box cyan> | ||
- | | | <color / | ||
- | | | | | ||
- | | | | | ||
- | |||
- | |||
- | 220 your.f.q.d.n ESTMP... | ||
- | |||
- | Introduces itself by way of an Hello command, either HELO (now obsolete) or EHLO, followed by its own Fully Qualified Domain Name: | ||
- | EHLO peers.f.q.d.n|Accepts this greeting with a 250 response. If the client used the extended version of the Hello command (EHLO), your server knows that it is capable of handling multi-line responses, and so will normally send back several lines indicating the capabilities offered by your server: | ||
- | |||
- | 250-your.f.q.d.n Hello ... | ||
- | 250-SIZE 52428800 | ||
- | 250-8BITMIME | ||
- | 250-PIPELINING | ||
- | 250-STARTTLS | ||
- | 250-AUTH | ||
- | 250 HELP | ||
- | |||
- | If the PIPELINING capability is included in this response, the client can from this point forward issue several commands at once, without waiting for the response to each one.| | ||
- | |||
- | |||
- | Starts a new mail transaction by specifying the Envelope Sender: | ||
- | MAIL FROM:< | ||
- | |||
- | |||
- | Issues a 250 response to indicate that the sender is accepted. | ||
- | |||
- | |||
- | Lists the Envelope Recipients of the message, one at a time, using the command: | ||
- | RCPT TO:< | ||
- | |||
- | Issues a response to each command (2xx, 4xx, or 5xx, depending on whether delivery to this recipient was accepted, subject to a temporary failure, or rejected). | ||
- | |||
- | |||
- | Issues a DATA command to indicate that it is ready to send the message. | ||
- | |||
- | |||
- | Responds 354 to indicate that the command has been provisionally accepted. | ||
- | |||
- | |||
- | Transmits the message, starting with RFC 2822 compliant header lines (such as: From:, To:, Subject:, Date:, Message-ID: | ||
- | |||
- | |||
- | Replies 250 to indicate that the message has been accepted. | ||
- | |||
- | |||
- | If there are more messages to be delivered, issues the next MAIL FROM: command. Otherwise, it says QUIT, or in rare cases, simply disconnects. | ||
- | |||
- | |||
- | Disconnects. |
email/smtp_transaction.1478273048.txt.gz · Last modified: 2020/07/15 09:30 (external edit)