My FreeBSD machines are all set up to not store mail, nor allow reading mail locally. But because you need the ability to deliver mail (for example so status reports from cron jobs show up), I have ssmtp installed and configured. This works great: Programs such as mail(1) can send mail; they do that by executing sendmail in a pipe and feeding the message into it, and sendmail itself internally runs ssmtp. Great.
Except, there is a new requirement I didn't know about. It turns out there are some programs that like to send mail by opening a socket to port 25 on localhost, and using SMTP protocol to send messages. I think Python programs in particular like to do that, because the default Python mail support library smtplib works this way. And one has to admit, it even makes sense to assume that the local host has a functioning MTA that can accept messages locally. But ssmtp doesn't work that way, so on my machines those sockets get timeouts.
And to be completely clear: I want a (very simple) SMTP server on localhost on port 25, but no open port 25 (or 465 or 587 or ...) to the outside world. This is only for local mail submission, for programs that prefer this technique over the submission technique of executing sendmail.
How to improve this most easily? Super heavyweight solution: Go back to using sendmail, and configure it to have port 25 open on localhost, no other incoming ports, all mail goes out via a smarthost, no mail storage. I am certain that this is possible (since anything is possible with sendmail), but sendmail configuration is also heavy-weight and requires lots of practice. I neither want that much work, nor taking the risk of administering a complex thing I don't really need 99% of. A similar (and even worse) option might be to install another full-featured MTA like Postfix or Exim: Same amount of complexity, and even less familiar.
I looked at dma, and like ssmtp, it can not accept port 25, even locally.
Anyone got a good idea? Something as simple as ssmtp, but that can also accept local mail (with no interesting features required)? Or a little daemon that runs on port 25, and simply takes complete messages and ships them out via sendmail?
Except, there is a new requirement I didn't know about. It turns out there are some programs that like to send mail by opening a socket to port 25 on localhost, and using SMTP protocol to send messages. I think Python programs in particular like to do that, because the default Python mail support library smtplib works this way. And one has to admit, it even makes sense to assume that the local host has a functioning MTA that can accept messages locally. But ssmtp doesn't work that way, so on my machines those sockets get timeouts.
And to be completely clear: I want a (very simple) SMTP server on localhost on port 25, but no open port 25 (or 465 or 587 or ...) to the outside world. This is only for local mail submission, for programs that prefer this technique over the submission technique of executing sendmail.
How to improve this most easily? Super heavyweight solution: Go back to using sendmail, and configure it to have port 25 open on localhost, no other incoming ports, all mail goes out via a smarthost, no mail storage. I am certain that this is possible (since anything is possible with sendmail), but sendmail configuration is also heavy-weight and requires lots of practice. I neither want that much work, nor taking the risk of administering a complex thing I don't really need 99% of. A similar (and even worse) option might be to install another full-featured MTA like Postfix or Exim: Same amount of complexity, and even less familiar.
I looked at dma, and like ssmtp, it can not accept port 25, even locally.
Anyone got a good idea? Something as simple as ssmtp, but that can also accept local mail (with no interesting features required)? Or a little daemon that runs on port 25, and simply takes complete messages and ships them out via sendmail?
