lotus

previous page: 14 Java (LAN Mail Protocols)
  
page up: LAN Mail Protocols FAQ
  
next page: 16 Other Sources of Information (LAN Mail Protocols)

15 List of Protocols and RFCs (LAN Mail)




Description

This article is from the LAN Mail Protocols FAQ, by John Wobus jmwobus@syr.edu with numerous contributions by others.

15 List of Protocols and RFCs (LAN Mail)

Note: for up-to-date information on the RFCs, get an index from an RFC
repository. For up-to-date information on the state of each RFC as to
the Internet Standards, see the most recent RFC called "Internet
Official Protocol Standards".

Name: Simple Mail Transfer Protocol
Nickname: SMTP
Document: RFC 821 (Postel, August 1982)
TCP-port: 25
Status: According to RFC 2000 (2/97), Standard/Recommended (STD 10);
Virtually universal for IP-based e-mail systems.

Name: Post Office Protocol, Version 2
Nickname: POP2
Document: RFC 937 (Butler et al, February 1985)
TCP-port: 109
Status: According to RFC 2000 (2/97), Historic/Not Recommended;
Functionally replaced by incompatible POP3 but likely to be
used at a few sites.

Name: Post Office Protocol, Version 3
Nickname: POP3
Document: RFC 1939 (Myers & Rose, May 1996)
TCP-port: 110 (109 also often used)
Status: According to RFC 2000 (2/97), Standard/Elective (STD 53);
In common use.
Sites: UC Irvine, MIT
Old Docs: RFC 1725.

Name Post Office Protocol, Version 3 Authentication command
Nickname: POP3 AUTH
Document: RFC1734 (Myers, December 1994)
Status: According to RFC 2000 (2/97), Proposed/Elective.

Name: Post Office Protocol, Version 3 Extended Service Offerings
Nickname: POP3 XTND
Document: RFC 1082 (Rose, November 1988)

Name: Distributed Mail Service Protocol
Nickname: DMSP, Pcmail
Document: RFC 1056 (Lambert, June 1988)
TCP-port: 158
Status: According to RFC 2000 (2/97), Informational;
Used very little
Sites: MIT

Name: Interactive Mail Access Protocol, Version 2
Nickname: IMAP2
Document: RFC 1176 (Crispin, August 1990)
TCP-port: 143
Status: According to RFC 2000 (2/97), Experimental/Limited Use;
In use, being replaced by upward-compatible IMAP4(rev1).
Sites: Stanford, U Washington

Name: Interactive Mail Access Protocol, Version 2bis
Nickname: IMAP2bis
TCP-port: 143
Status: Experimental, but in use, being replaced by upward-compatible
IMAP4(Rev1); No RFC.

Name: Interactive Mail Access Protocol, Version 3
Nickname: IMAP3
Document: RFC 1203 (Rice, February 1991)
TCP-port: 220
Status: According to RFC 2000 (2/97) "Historic(Not Recommended)";
No one uses it.
Sites: Stanford

Name: Internet Message Access Protocol, Version 4
Nickname: IMAP4
Document: RFC 1730 (Crispin, December 1994)
TCP-port: 143
Status: According to RFC 2000 (2/97) "Obselete Proposed/Elective
Protocol" obseleted by IMAP4rev1"; Implementations exist,
being replaced by revised version IMAP4rev1.
Sites: U Washington
Related: RFC 1731 (Myers, December 1994),
RFC 1732 (Crispin, December 1994),
RFC 1733 (Crispin, December 1994)

Name: Internet Message Access Protocol, Version 4rev1
Nickname: IMAP4rev1
Document: RFC 2060 (Crispin, December 1996)
TCP-port: 143
Status: According to RFC 2000 (2/97) "Proposed/Elective Protocol";
Implementations exist and more are in progress.
Sites: U Washington
Related: RFC 2061 (Crispin, December 1996),
RFC 2062 (Crispin, December 1996)

Name: Interactive Mail Support Protocol
Nickname: IMSP
Document: Draft RFC: ? (Myers, June 1995)
TCP Port: 406
Status: Experimental, renamed ACAP
Sites: Carnegie Mellon

Name: Application Configuration Access Protocol
Nickname: ACAP
Document: Draft RFC: ? (Myers, June 1996)
Status: ?
Sites: Carnegie Mellon

Note: The "I" in IMAP used to stand for "Interactive". Now it stands
for "Internet" and the "M" stands for "Message" rather than "Mail".
Also, Internet drafts are available at ds.internic.net, munnari.oz.au,
and nic.nordu.net in directory internet-drafts. IMAP2bis is
essentially an early version of IMAP4.

 

Continue to:













TOP
previous page: 14 Java (LAN Mail Protocols)
  
page up: LAN Mail Protocols FAQ
  
next page: 16 Other Sources of Information (LAN Mail Protocols)