Source code: Lib/smtpd.py [https://hg.python.org/cpython/file/default/Lib/smtpd.py]
This module offers several classes to implement SMTP (email) servers.
Several server implementations are present; one is a generic do-nothing implementation, which can be overridden, while the other two offer specific mail-sending strategies.
Additionally the SMTPChannel may be extended to implement very specific interaction behaviour with SMTP clients.
The code supports RFC 5321 [http://tools.ietf.org/html/rfc5321.html], plus the RFC 1870 [http://tools.ietf.org/html/rfc1870.html] SIZE and RFC 6531 [http://tools.ietf.org/html/rfc6531.html] SMTPUTF8 extensions.
Create a new SMTPServer object, which binds to local address localaddr. It will treat remoteaddr as an upstream SMTP relayer. It inherits from asyncore.dispatcher, and so will insert itself into asyncore‘s event loop on instantiation.
data_size_limit specifies the maximum number of bytes that will be accepted in a DATA command. A value of None or 0 means no limit.
enable_SMTPUTF8 determins whether the SMTPUTF8 extension (as defined in RFC 6531 [http://tools.ietf.org/html/rfc6531.html]) should be enabled. The default is False. If enable_SMTPUTF is set to True, the process_smtputf8_message() method must be defined. A ValueError is raised if both enable_SMTPUTF8 and decode_data are set to True at the same time.
A dictionary can be specified in map to avoid using a global socket map.
decode_data specifies whether the data portion of the SMTP transaction should be decoded using UTF-8. The default is True for backward compatibility reasons, but will change to False in Python 3.6. Specify the keyword value explicitly to avoid the DeprecationWarning.
Raise a NotImplementedError exception. Override this in subclasses to do something useful with this message. Whatever was passed in the constructor as remoteaddr will be available as the _remoteaddr attribute. peer is the remote host’s address, mailfrom is the envelope originator, rcpttos are the envelope recipients and data is a string containing the contents of the e-mail (which should be in RFC 5321 [http://tools.ietf.org/html/rfc5321.html] format).
If the decode_data constructor keyword is set to True, the data argument will be a unicode string. If it is set to False, it will be a bytes object.
Return None to request a normal 250 Ok response; otherwise return the desired response string in RFC 5321 [http://tools.ietf.org/html/rfc5321.html] format.
Raise a NotImplementedError exception. Override this in subclasses to do something useful with messages when enable_SMTPUTF8 has been set to True and the SMTP client requested SMTPUTF8, since this method is called rather than process_message() when the client actively requests SMTPUTF8. The data argument will always be a bytes object, and any non-None return value should conform to RFC 6531 [http://tools.ietf.org/html/rfc6531.html]; otherwise, the API is the same as for process_message().
Override this in subclasses to use a custom SMTPChannel for managing SMTP clients.
Changed in version 3.4: The map argument was added.
Changed in version 3.5: localaddr and remoteaddr may now contain IPv6 addresses.
New in version 3.5: the decode_data and enable_SMTPUTF8 constructor arguments, and the process_smtputf8_message() method.
Create a new debugging server. Arguments are as per SMTPServer. Messages will be discarded, and printed on stdout.
Create a new pure proxy server. Arguments are as per SMTPServer. Everything will be relayed to remoteaddr. Note that running this has a good chance to make you into an open relay, so please be careful.
Create a new pure proxy server. Arguments are as per SMTPServer. Everything will be relayed to remoteaddr, unless local mailman configurations knows about an address, in which case it will be handled via mailman. Note that running this has a good chance to make you into an open relay, so please be careful.
Create a new SMTPChannel object which manages the communication between the server and a single SMTP client.
conn and addr are as per the instance variables described below.
data_size_limit specifies the maximum number of bytes that will be accepted in a DATA command. A value of None or 0 means no limit.
enable_SMTPUTF8 determins whether the SMTPUTF8 extension (as defined in RFC 6531 [http://tools.ietf.org/html/rfc6531.html]) should be enabled. The default is False. A ValueError is raised if both enable_SMTPUTF8 and decode_data are set to True at the same time.
A dictionary can be specified in map to avoid using a global socket map.
decode_data specifies whether the data portion of the SMTP transaction should be decoded using UTF-8. The default is True for backward compatibility reasons, but will change to False in Python 3.6. Specify the keyword value explicitly to avoid the DeprecationWarning.
To use a custom SMTPChannel implementation you need to override the SMTPServer.channel_class of your SMTPServer.
Changed in version 3.5: the decode_data and enable_SMTPUTF8 arguments were added.
The SMTPChannel has the following instance variables:
Holds the SMTPServer that spawned this channel.
Holds the socket object connecting to the client.
Holds the address of the client, the second value returned by socket.accept
Holds a list of the line strings (decoded using UTF-8) received from the client. The lines have their "\r\n" line ending translated to "\n".
Holds the current state of the channel. This will be either COMMAND initially and then DATA after the client sends a “DATA” line.
Holds a string containing the greeting sent by the client in its “HELO”.
Holds a string containing the address identified in the “MAIL FROM:” line from the client.
Holds a list of strings containing the addresses identified in the “RCPT TO:” lines from the client.
Holds a string containing all of the data sent by the client during the DATA state, up to but not including the terminating "\r\n.\r\n".
Holds the fully-qualified domain name of the server as returned by socket.getfqdn().
Holds the name of the client peer as returned by conn.getpeername() where conn is conn.
The SMTPChannel operates by invoking methods named smtp_<command> upon reception of a command line from the client. Built into the base SMTPChannel class are methods for handling the following commands (and responding to them appropriately):
| Command | Action taken |
|---|---|
| HELO | Accepts the greeting from the client and stores it in seen_greeting. Sets server to base command mode. |
| EHLO | Accepts the greeting from the client and stores it in seen_greeting. Sets server to extended command mode. |
| NOOP | Takes no action. |
| QUIT | Closes the connection cleanly. |
| Accepts the “MAIL FROM:” syntax and stores the supplied address as mailfrom. In extended command mode, accepts the RFC 1870 [http://tools.ietf.org/html/rfc1870.html] SIZE attribute and responds appropriately based on the value of data_size_limit. | |
| RCPT | Accepts the “RCPT TO:” syntax and stores the supplied addresses in the rcpttos list. |
| RSET | Resets the mailfrom, rcpttos, and received_data, but not the greeting. |
| DATA | Sets the internal state to DATA and stores remaining lines from the client in received_data until the terminator "\r\n.\r\n" is received. |
| HELP | Returns minimal information on command syntax |
| VRFY | Returns code 252 (the server doesn’t know if the address is valid) |
| EXPN | Reports that the command is not implemented. |
