>I would hope we'd remove it. It's a toy implementation, unmaintained, >probably doesn't support a lot of newer protocol features, and is probably >full of bugs. Hopefully nobody uses it!
I use it and it works well for my specific use case - a Postfix spam filter. During incoming SMTP transactions, I have Postfix configured to pass the received message to my daemon via SMTP (smtpd_proxy_filter). My daemon pronounces judgement, allowing Postfix to potentially reject the message while the sender is still connected (so no bounce backscatter). My daemon only receives one connection at a time, and only well formed SMTP from postfix, so the smtpd module works well - no need for a 3rd party module or the hassle of async. -- Andrew McNamara, Senior Developer, Object Craft http://www.object-craft.com.au/ _______________________________________________ python-committers mailing list -- python-committers@python.org To unsubscribe send an email to python-committers-le...@python.org https://mail.python.org/mailman3/lists/python-committers.python.org/ Message archived at https://mail.python.org/archives/list/python-committers@python.org/message/QA2OVVFX564H5EBARUKODUPMYHTJAMCO/ Code of Conduct: https://www.python.org/psf/codeofconduct/
