moggers87 / lmtpd

A LMTP counterpart to smtpd in the Python standard library

moggers87

Hey it's me.

I write code for living. Send me money or consider hiring me if you like my work.

Latest releases

• django-sendfile2 0.7.1 released on 2024-02-17
• django-two-factor-auth 1.16.0 released on 2024-02-03
• Inboxen deploy-2023.11.27.20.52.7 released on 2023-11-27
• Inboxen deploy-2023.9.12.15.59.8 released on 2023-09-12
• Inboxen deploy-2023.9.5.10.25.4 released on 2023-09-05

From moggers87.co.uk

• (art) Penguin posted on 2022-04-05
• (art) Ribbons posted on 2021-10-07
• (food) Harissa lentil pot posted on 2021-09-13
• (food) Chickpea burger posted on 2021-09-13
• (food) Sweet potato wedges posted on 2021-09-13

lmtpd's Issues

Multiple responses, how?

From reading the pydoc on lmtpd, I cannot work out how to return a single reply for every recipient. Moreover, it is strange that the last one should be explicitly returned, as None would also have a response that would apply to that last recipient.

It would make sense to me to return a list as long as the list of RCPT TO addresses; it would also make sense if a separate 250 Ok was sent for each of these when None was returned. But I cannot work this out from the documentation.

Furthermore, an empty list of RCPT TO addresses should return 503, which is a deviation from SMTP. Has this been taken care of, or is it the subclass's responsibility?

Finally, a remark might be useful that the module really completely locks out unless it is sent the CR-LF line endings. It is absolutely not forgiving (and nc -C is enough to resolve that, but it helps to know why it freezes).

Could you update the documentation please, and if needed, the code as well, to deviate from SMTP where LMTP needs it?

Drop Python 2 support

Python 2 goes EOL at the end of 2019.

Also remove code required for Python 2 support.

Missing files in PyPI package

test_lmtp file is not included in PyPI release tarball. Could it be added so one could use it as a source when packaging for distros? For now, I'll use the GitHub release tarball because that contains it.

Py3K support

Support Python 3, maybe even look into getting it included in Python 3's smtpd.py

Update supported Python versions

• Remove 2.6 and anything from 3.x that's reached EOL
• Add 3.7 and 3.8

IPv6 support

Currently only IPv4 and UNIX sockets are supported. We should use getaddrinfo to see what's available and maybe allow the user to override what we find there.

PIPELINING and ENHANCEDSTATUSCODES support

The RFC says:

A server implementation MUST implement the PIPELINING [PIPELINING]
and ENHANCEDSTATUSCODES [ENHANCEDSTATUSCODES] ESMTP extensions. A
server implementation SHOULD implement the 8BITMIME [8BITMIME]
extension.

This is totally something we should do.

Python 3 and non-ASCII/UTF-8 data

While implementing Python 3 support in Salmon (see moggers87/salmon#7 ), I stumbled upon this: https://bugs.python.org/issue19662

tl;dr: Python's SMTPd is absolutely useless in anything less than 3.5 (assuming the above patch made it into the 3.5 release)

We should start testing with non-ASCII/UTF-8 data and fix the library to work with Python 3.5 and then decide what do about 3.3 and 3.4.