
MAIL Parameters

(last updated 2007-11-14)

Registry Name: Mail Service Types
Note:
The set of services desired from a mail server are sometimes
characterized by the "hello" keyword used.  These are listed here.

Registry:
Keywords  Description                       Reference
--------  --------------------------------  ---------
HELO      Simple Mail                       [RFC821]
EHLO      Mail Service Extensions           [RFC1869]
LHLO      Local Mail                        [RFC2033]


Registry Name: Mail Encryption Types
Note:
[RFC822] specifies that Encryption Types for mail may be assigned.
There are currently no RFC 822 encryption types assigned.  Please use
instead the Mail Privacy procedures defined in [RFC1421], [RFC1422],
[RFC1423].


Registry Name: SMTP Service Extensions
Reference: [RFC1425]
Registration Procedures: Standards Track RFC

Note:
The Simple Mail Transfer Protocol [RFC2821] specifies a set of commands
or services and a general procedure for extending that set. The table below 
lists SMTP service extensions. Both message submission [RFC2476] and mail 
transfer [RFC2821] may use these extensions unless otherwise specified.

The server response to a client EHLO command includes a keyword for each 
service extension the server implements.

Registry:
Keywords             Description                         Reference
-------------------  ----------------------------------  ---------
SEND                 Send as mail                        [RFC821]
SOML                 Send as mail or terminal            [RFC821]
SAML                 Send as mail and terminal           [RFC821]
EXPN                 Expand the mailing list             [RFC821]
HELP                 Supply helpful information          [RFC821]
TURN                 Turn the operation around           [RFC821]
8BITMIME             Use 8-bit data                      [RFC1652]
SIZE                 Message size declaration            [RFC1870]
VERB                 Verbose                             [Eric Allman]
ONEX                 One message transaction only        [Eric Allman]
CHUNKING             Chunking                            [RFC3030]
BINARYMIME           Binary MIME                         [RFC3030]
CHECKPOINT           Checkpoint/Restart                  [RFC1845]
DELIVERBY            Delivery within prescribed period   [RFC2852]
PIPELINING           Command Pipelining                  [RFC2920]
DSN                  Delivery Status Notification        [RFC3461]
ETRN                 Extended Turn                       [RFC1985] +
ENHANCEDSTATUSCODES  Enhanced Status Codes               [RFC2034]
STARTTLS             Start TLS                           [RFC3207]
NO-SOLICITING        Notification of no soliciting       [RFC3865]
MTRK                 Message Tracking                    [RFC3885]     
SUBMITTER            SMTP Responsible Submitter          [RFC4405]
ATRN                 Authenticated TURN                  [RFC2645] +
AUTH                 Authentication                      [RFC4954]
BURL                 Remote Content                      [RFC4468] *
FUTURERELEASE        Future Message Release              [RFC4865]

+ SMTP [RFC2821] only. Not for use on Submit port 587.
* Submit [RFC2476] only. Not for use with SMTP on port 25. 

Some of these keywords have parameters.  These are listed here (those
keywords not listed here have no parameters).

Service Ext      EHLO Keyword   Parameters               Reference
---------------  -------------  -----------------------  ---------
Size             SIZE           number                   [RFC1870]
No Soliciting    NO-SOLICITING  Soliciting-keywords      [RFC3865]
Authentication   AUTH           SASL mechanism names     [RFC4954]
Remote Content   BURL           Permitted URL prefixes   [RFC4468]


MAIL SYSTEM NAMES and ADDRESS TYPES

In some places, an identification of other mail systems is used.

One of these is in "The COSINE and Internet X.500 Schema" (section
9.3.18) [RFC1274].  The mail system names listed here are used as the
legal values in that schema under the "otherMailbox" attribute
"mailboxType" type (which must be a PrintableString).

Another place is in "Mapping between X.400(1988) / ISO 10021 and RFC
822" (section 4.2.2) [RFC1327] (obsoleted by [RFC2156]).  The names 
listed here are used as the legal values in that schema under the 
"std-or-address" attribute "registered-dd-type" type (which must be 
a "key-string").

Note that key-string = <a-z, A-Z, 0-9, and "-" >.

Mail System Name  Description               Reference
----------------  ------------------------  ---------
mcimail           MCI Mail


Registry Name: Address Types
Reference: [RFC3461][RFC3464]
Note: 
Please see the following:
http://www.iana.org/assignments/dsn-types


Registry Name: Diagnostic Types
Reference: [RFC3461][RFC3464]
Note: 
Please see the following:
http://www.iana.org/assignments/dsn-types


Registry Name: MTA Name Types
Reference: [RFC3461][RFC3464]
Note: 
Please see the following:
http://www.iana.org/assignments/dsn-types


Registry Name: Mail Transmission Types
Reference: [RFC821][RFC822][RFC2821]
Note: 
The Simple Mail Transfer Protocol [RFC821][RFC2821] and the Standard 
for the Format of ARPA Internet Text Messages [RFC822] specify that a 
set of "Received" lines will be prepended to the headers of electronic 
mail messages as they are transported through the Internet. These 
received line may optionally include either or both a "via" phrase 
and/or a "with" phrase.  The legal values for the phrases are listed here. 
The via phrase is intended to indicate the link or physical medium over
which the message was transferred.  The with phrase is intended to
indicate the protocol or logical process that was used to transfer the
message.

Sub-registry: VIA link types
Registry:
VIA link types  Description                   Reference
--------------  ----------------------------  ---------
UUCP            Unix-to-Unix Copy Program     [???]
TCP             TCP                           [RFC2821]

Sub-registry: WITH protocol types
Registry:
WITH protocol types  Description                        Reference
-------------------  ---------------------------------  ---------
SMTP                 Simple Mail Transfer Protocol      [RFC2821]
ESMTP                SMTP with Service Extensions       [RFC2821]
ESMTPA               ESMTP with SMTP AUTH               [RFC3848]
ESMTPS               ESMTP with STARTTLS                [RFC3848]
ESMTPSA              ESMTP with both STARTTLS and       [RFC3848]
                     SMTP AUTH
LMTP                 Local Mail Transfer Protocol       [RFC3848]
LMTPA                LMTP with SMTP AUTH                [RFC3848]
LMTPS                LMTP with STARTTLS                 [RFC3848]
LMTPSA               LMTP with both STARTTLS and        [RFC3848]
                     SMTP AUTH
ESMTP                ESMTP with NO-SOLICITING           [RFC3865]
MMS                  Multimedia Messaging Service       [RFC4356]


Registry Name: Address Literal Tags
Reference: [RFC2821]
Note: 
Please see the following:
http://www.iana.org/assignments/dsn-types


References
----------
[ANSI-X12]

[IS-10646]

[POSTSCRIPT] 
           Adobe Systems Inc., "PostScript Language Reference
           Manual", 2nd Edition, 2nd Printing, January 1991.

[RFC821]   Postel, J., "Simple Mail Transfer Protocol", STD 10, RFC 821,
           USC/Information Sciences Institute, August 1982.

[RFC822]   Crocker, D., "Standard for the Format of ARPA-Internet Text
           Messages", STD 11, RFC 822, UDEL, August 1982.

[RFC1274]  Barker, P., and S. Kille, "The COSINE and Internet X.500
           Schema", RFC 1274, University College London, November 1991. 

[RFC1327]  Hardcastle-Kille, S., "Mapping between X.400(1988) / ISO
           10021 and RFC 822", RFC 1327, University College London,
           May 1992.

[RFC1421]  Linn, J., "Privacy Enhancement for Internet Electronic
           Mail: Part I: Message Encipherment and Authentication
           Procedures", RFC 1421, IAB IRTF PSRG, IETF PEM WG,
           February 1993.

[RFC1422]  Kent, S., "Privacy Enhancement for Internet
           Electronic Mail: Part II -- Certificate-Based Key
           Management", BBN, IAB IRTF PSRG, IETF PEM, February 1993.

[RFC1423]  Balenson, D., "Privacy Enhancement for Internet Electronic
           Mail: Part III -- Algorithms, Modes, and Identifiers",
           RFC 1423, TIS, IAB IRTF PSRG, IETF PEM WG, February 1993.

[RFC1505]  Costanzo, A., Robinson, D., and R. Ullmann, "Encoding Header
           Field for Internet Messages", RFC 1505, AKC Consulting,
           Computervision Corporation, August 1993.

[RFC1652]  Klensin, J., Freed, N., Rose, M., Stefferud, E., and D.
           Crocker, "SMTP Service Extension for 8bit-MIMEtransport", 
           RFC 1652, MCI, Innosoft, Dover Beach Consulting, Inc.,
           Network Management Associates, Inc., Silicon Graphics, Inc.,
           July 1994.

[RFC1830]  Vaudreuil, G., "SMTP Service Extensions for Transmission of
           Large and Binary MIME Messages", RFC 1830, Octel Network
           Services, August 1995.

[RFC1845]  Crocker, D., N. Freed, and A. Cargille, "SMTP Service
           Extension for Checkpoint/Restart", RFC 1845, Brandenburg
           Consulting, Innosoft International, September 1995.

[RFC1869]  Klensin, J., Freed, N., Rose, M., Stefferud, E., and D.
           Crocker, "SMTP Service Extensions", RFC 1869, MCI, Innosoft,
           Dover Beach Consulting, Inc., Network Management Associates,
           Inc., Brandenberg Consulting., November 1995.

[RFC1870]  Klensin, J., Freed, N., and K. Moore, "SMTP Service
           Extension for Message Size Declaration", RFC 1870,
           MCI, Innosoft, University of Tennessee, November 1995.

[RFC1985]  DeWinter, J., "SMTP Service Extension for Remote Message
           Queue Starting", RFC1985, Wildbear Consulting, August 1996.

[RFC2033]  Myers, J., "Local Mail Transfer Protocol", RFC 2033,
           Carnegie Mellon, October 1996.

[RFC2034]  Freed, N., "SMTP Service Extension for Returning Enhanced
           Status Codes", RFC Innosoft International, October 1996.

[RFC2156]  S. Kille, "MIXER (Mime Internet X.400 Enhanced Relay):
           Mapping between X.400 and RFC 822/MIME", RFC 2156, January 1998.
 
[RFC2183]  Troost, R., S. Dorner, and K. Moore, "Communicating
           Presentation Information in Internet Messages: The
           Content-Disposition Header Field", RFC 2183, New Century
           Systems, QUALCOMM Incorporated, University of Tennessee,
           August 1997.

[RFC2197]  Freed, N., "SMTP Service Extension for Command Pipelining",
           RFC 2197, Innosoft, September 1997.

[RFC2487]  Hoffman, P., "SMTP Service Extension for Secure SMTP over
           TLS", RFC 2487, Internet Mail Consortium, January 1999.

[RFC2645]  R. Gellens, "ON-DEMAND MAIL RELAY (ODMR) SMTP with Dynamic 
           IP Addresses", RFC 2645, August 1999.

[RFC2821]  J. Klensin, Editor, "Simple Mail Transfer Protocol", 
           RFC 2821, April 2001.

[RFC2852]  D. Newman, "Deliver By SMTP Service Extension", RFC 2852,
           June 2000.

[RFC2920]  N. Freed, "SMTP Service Extension for Command Pipelining",
           RFC 2920, September 2000.

[RFC3030]  G. Vaudreuil, "SMTP Service Extensions for Transmission of Large
           and Binary MIME Messages", RFC 3030, December 2000.

[RFC3207]  P. Hoffman, "SMTP Service Extension for Secure SMTP over 
           Transport Layer Security", RFC 3207, February 2002.

[RFC3461]  K. Moore, "Simple Mail Transfer Protocol (SMTP) Service 
           Extension for Delivery Status Notifications (DSNs)", RFC 3461, 
           January 2003.

[RFC3848]  C. Newman, "ESMTP and LMTP Transmission Types Registration",
           RFC 3848, July 2004.  

[RFC3865]  C. Malamud, "A No Soliciting SMTP Service Extension", RFC 3865,
           September 2004.

[RFC3885]  E. Allman and T. Hansen, "SMTP Service Extension for Message 
           Tracking", RFC 3885, September 2004.

[RFC4405]  E. Allman and H. Katz, "SMTP Service Extension for Indicating
           the Responsible Submitter of an E-mail Message", RFC 4405, April 2006.

[RFC4356]  R. Gellens, "Mapping Between the Multimedia Messaging Service (MMS) 
           and Internet Mail", RFC 4356, January 2006.

[RFC4468]  C. Newman, "Message Submission BURL Extension", RFC 4468, May 2006.

[RFC4865]  G. White, G. Vaudreuil, "SMTP Submission Service Extension for 
           Future Message Release", RFC 4865, May 2007.

[RFC4954]  Robert Siemborski and Alexey Melnikov, "SMTP Service Extension 
           for Authentication", RFC 4954, July 2007.

[]





