About Opentopia
Opentopia Directory Encyclopedia Tools

Simple Mail Transfer Protocol

Encyclopedia : S : SI : SIM : Simple Mail Transfer Protocol

 Internet protocol suite
Layer Protocols
Application DNS, TLS/SSL, TFTP, FTP, HTTP, IMAP, IRC, NNTP, POP3, SIP, SMTP, SNMP, SSH, TELNET, BitTorrent, RTP, rlogin, …
Transport TCP, UDP, DCCP, SCTP, IL, RUDP,
Network IP (IPv4, IPv6), ICMP, IGMP, ARP, RARP, …
Link Ethernet, Wi-Fi, Token ring, Point-to-Point Protocol>PPP, SLIP, FDDI, ATM, DTM, Frame Relay, SMDS, …

Simple Mail Transfer Protocol (SMTP) is the de facto standard for e-mail and internet fax transmissions across the Internet. Formally SMTP is defined in RFC 821 (STD 10) as amended by RFC 1123 (STD 3) chapter 5. The protocol used today is also known as ESMTP and defined in RFC 2821.

Contents

History

SMTP is a relatively simple, text-based protocol, where one or more recipients of a message are specified (and in most cases verified to exist) and then the message text is transferred. It is quite easy to test an SMTP server using the telnet program (see below). 

SMTP uses TCP port 25. To determine the SMTP server for a given domain name, the MX (Mail eXchange) DNS record is used, falling back to a simple A record in the case of no MX.


SMTP started becoming widely used in the early 1980s.  At the time, it was a complement to UUCP (Unix to Unix CoPy) which was better suited to handle e-mail transfers between machines that were intermittently connected.  SMTP, on the other hand, works best when both the sending and receiving machines are connected to the network all the time. 


The article about sender rewriting contains technical background info about the early SMTP history and source routing before RFC 1123 (1989, obsoleted by RFC 2821).


Sendmail was one of the first (if not the first) mail transfer agents to implement SMTP.  As of 2001 there are at least 50 programs that implement SMTP as a client (sender of messages) or a server (receiver of messages).  Some other popular SMTP server programs include exim, Postfix, qmail, and Microsoft Exchange Server.


Since this protocol started out as purely ASCII text-based, it did not deal well with binary files.  Standards such as MIME were developed to encode binary files for transfer through SMTP.  MTAs developed after sendmail also tended to be implemented 8-bit-clean, so that the alternate "just send eight" strategy could be used to transmit arbitrary data via SMTP.  Non-8-bit-clean MTAS today tend to  support the 8BITMIME extension, permitting binary files to be transmitted almost as easily as plain text.


SMTP is a "push" protocol that does not allow one to "pull" messages from a remote server on demand. To do this a mail client must use POP3 or IMAP. Another SMTP server can trigger a delivery in SMTP using ETRN.



Developers




Many persons edited or contributed to the core SMTP specifications, among them Jon Postel, Eric Allman, Dave Crocker, Ned Freed, Randall Gellens, John Klensin, and Keith Moore.



Sample SMTP communications

After establishing a connection between the sender (the client) and the receiver (the server), the following is a legal SMTP session.  In the following conversation, everything sent by the client is prefaced with C: and everything sent by the server is prefaced with S:.  On most computer systems, a connection can be established using the telnet command on the client machine, for example.



telnet www.example.com 25



which opens an SMTP connection from the sending machine to the host www.example.com.



S: 220 www.example.com ESMTP Postfix
C: HELO mydomain.com
S: 250 Hello mydomain.com
C: MAIL FROM:
S: 250 Ok
C: RCPT TO:
S: 250 Ok
C: DATA
S: 354 End data with .
C: Subject: test message
C: From: sender@mydomain.com
C: To: friend@example.com
C:
C: Hello,
C: This is a test.
C: Goodbye.
C: .
S: 250 Ok: queued as 12345
C: QUIT
S: 221 Bye


Although optional and not shown above, nearly all clients ask the server which SMTP extensions the server supports, by using the EHLO greeting to invoke Extended SMTP (ESMTP). These clients use HELO only if the server does not respond to EHLO.


Contemporary clients will use the ESMTP extension keyword SIZE to inquire of the server the maximum message size that will be accepted. Older clients and servers will try to transfer huge messages that will be rejected after wasting the network resources, including a lot of connect time to dialup ISPs that are paid by the minute. 


For the edit planning of giant files or sending with older clients, users can manually determine in advance the maximum size accepted by ESMTP servers. The user telnets as above, but substitutes "EHLO mydomain.com" for the HELO command line. 



S: 220-serverdomain.com ESMTP 
S: 220 NO UCE. 
C: EHLO mydomain.com
S: 250-serverdomain.com Hello mydomain.com [127.0.0.1]
S: 250-SIZE 14680064
S: 250-PIPELINING
S: 250 HELP


This serverdomain.com declares that it will accept a fixed maximum message size no larger than 14,680,064 octets (8-bit bytes). Depending on the server's actual resource usage, it may be currently unable to accept a message this large. 


In the simplest case, an ESMTP server will declare a maximum SIZE with only the EHLO user interaction. If no number appears after the SIZE keyword, or if the current message limit must exactly determined, the user can further interact by simulating the ESMTP header of a message with an estimated size. See External Link RFC 1870 below.



SMTP Security and Spamming


One of the limitations of the original SMTP is that it has no facility for authentication of senders.  Therefore the SMTP-AUTH extension was defined. 


In spite of this, E-mail spamming is still a major problem. Modifying SMTP extensively, or replacing it completely, is not believed to be practical, due to the network effects of the huge installed base of SMTP. Internet Mail 2000 is one such proposal for replacement.


For this reason, there are a number of proposals for sideband protocols that will assist SMTP operation. The Anti-Spam Research Group of the IRTF is working on a number of E-mail authentication and other proposals for providing simple source authentication that is flexible, lightweight, and scalable. Recent IETF activities include MARID (2004) leading to two approved IETF experiments in 2005, and DKIM in 2006.



Related RFCs



See also





External links



cr.yp.to links





Other links







.




















































 





From Wikipedia, the Free Encyclopedia. Original article here. Support Wikipedia by contributing or donating.
All text is available under the terms of the GNU Free Documentation License See Wikipedia Copyrights for details.













Search Titles









0123456789
ABCDEFGHIJ
KLMNOPQRST
UVWXYZ?










E-mail this article to:



Personal Message: