The biggest problem with setting up new web services is getting to be able to successfully send email... (I've got a half-dozen solutions I use, but it's my main source of annoying sysadmin)

@lightweight tell this to the people who think emailing patches is still a good way to write software

@be @lightweight Curious to know what you find wrong with email. I outlined my thoughts in the thead I imagine you’re alluding to.

@lightweight I've a lambda written that receives a POST request and just sends. Most likely not applicable to the situations you find yourself in, but it's removed nearly all that annoyance for me personally!

@futuresprog I use a lot of Docker and in cases where the app uses localhost by default, I use MSMTP (a non-daemon Sendmail alternative) to talk to one of my Mailcow installations. Or I go directly to the Mailcow via auth SMTP if the app in question supports it. But currently wrestling with Piwigo refusing to send mail from my personal instance... :)

@lightweight I keep a public-facing email server in the cloud that also has an interface to my private vpn. I configure the email server so that inbound email from the vpn interface is authorized for relay out, and add extra limitations at the firewalls. Then each local sendmail/postfix/exim4/whatever only needs to point to the email server as a "satellite." Since each service typically handles sendmail-style handling, it's fast & and uniform for me to get them working.
@lightweight Nice write-up! And then agreed ~ once you know what you're doing at the postfix config level and everything above it, it really is just a pain in the butt dealing with the different applications wanting to send. No one will let that problem get old :-p
Sign in to participate in the conversation
Mastodon - NZOSS

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!