Email processes and protocols/Related Articles: Difference between revisions
Jump to navigation
Jump to search
imported>David MacQuigg m (correct capitalization) |
imported>David MacQuigg m (→Subtopics) |
||
| Line 17: | Line 17: | ||
{{r|Post Office Protocol|Post Office Protocol (POP)}} (RFC-1939) | {{r|Post Office Protocol|Post Office Protocol (POP)}} (RFC-1939) | ||
{{r|Messaging application protocols|Internet Message Access Protocol (IMAP)}} (RFC-3501) | {{r|Messaging application protocols|Internet Message Access Protocol (IMAP)}} (RFC-3501) | ||
{{r|SMTP | {{r|SMTP example sessions}} | ||
==Other related topics== | ==Other related topics== | ||
Revision as of 14:15, 26 September 2009
- See also changes related to Email processes and protocols, or pages that link to Email processes and protocols or to this page or whose text contains "Email processes and protocols".
Parent topics
- Email system [r]: General overview of how the Internet electronic mail system works. [e]
Subtopics
- Simple Mail Transfer Protocol (SMTP) [r]: In the Internet Protocol Suite, SMTP is the basic method for transferring the "envelopes" of electronic mail among servers performing the electronic "post office" function, not the user mailbox function. [e] (RFC-5321)
- Post Office Protocol (POP) [r]: A client-server messaging protocol for email which requires messages to be downloaded to a client's computer, phone or tablet for reading. [e] (RFC-1939)
- Internet Message Access Protocol (IMAP) [r]: Add brief definition or description (RFC-3501)
- SMTP example sessions [r]: Typical email sessions using the SMTP protocol. [e]
- Email message formats [r]: The formats and encodings used for text, pictures, and various other objects in an email. [e] (RFC-5322)
- Email message headers [r]: The header lines in every email message, defined in RFC 5322 [e]
- Email authentication [r]: Brief overview of methods used to authenticate the sender of an email. [e]
- Multipurpose Internet Mail Extensions (MIME) [r]: MIME extends the format of Internet mail to allow non-US-ASCII textual messages, non-textual messages, multipart message bodies, and non-US-ASCII information in message headers. [e] (RFC-2045..2049)