Hi there,
what SMTP relay’s / services do you use or can recommend for sending monitoring alerts.
I’m running a few services, but mostly all my custom scripts, and tasks are configured to sent an e-mail if something goes “off-script”. Before I used my gmail account - but I’m in the middle of migrating away, and my requirements have evolved.
I’ve searched but I haven’t found anything good. Services like Mailgun, Mailtrap etc. are nice - but their bundle’s are a bit much for my taste.
The service/ relay should meet the following requirements.
- bring your own domain (use your own domain/ or sub-domains as sender address)
- must have DKIM (anything else is not a serious service!)
- support SMTP via TLS
- support multiple SMTP clients, with each different credentials/ secrets
- Allow custom header/ envelope changes
At the moment I’m looking at Amazon SES, because I don’t expect a lot of messages (I had 3 alerts in the last 1,5 yrs).
I’ve been using SMTP2Go at work for our low volume of notifications and it works fantastic
I know this doesn’t fit your criterea OP, but if anyone else is looking for some kind of notification service, I use: SMTP to Telegram
I get instantly notified on my phone for healthchecks.io failures, cronjob reports for different scripts like borg backups or ddns update failures, certain Home Assistant scripts, and Sonarr completions so I know when a new TV episode is done downloading, and a bunch of other things set to notify on failure like SMART failures or snapraid-runner failures or distro updates… so many things. It’s nice having peace of mind that if I haven’t been notified that something is wrong, then I know everything is working, and I do not need to check on it. So it’s one of my favorite services that I’m running.
I don’t think I need to say it, but this is obviously not something you would put facing WAN as there is no TLS nor authentication.
Even if it’s a bit different. It’s always nice to see what’s out there. I will definitively look into it.
For everything else you have SMTP to Apprise
That looks very nice, gives a lot more options which I love so I will have to look into it.
I use Purelymail for mine. I have Uptime Kuma integrated with it using the SMTP server and also have different things like my password vault connected through it. It’s generally lightning fast and budget friendly too.
It sounds very promising.
Thanks. I really appreciate all those “niche” products. With just web research I wouldn’t have found it.
I use mailrise which is apprise under the hood for anything that doesn’t have Pushover support built into it. Mailrise converts any email it receives to a push message. It supports a ton of different services like Pushover.
Have you thought of self-hosting mailcow? https://github.com/mailcow/mailcow-dockerized
It’s very easy to set up and fairly straightforward to maintain, if you have a static IP and it’s not impossible to get a PTR record then I highly recommend it. Yes you’re self hosting your own mail server but mailcow vastly simplifies this.
Alternatively plonking it on the right VPS can also work.
I thought about self-hosting, but first of all I got a dynamic IP. Further I want a solution which has roughly 98% availability and 99,99% reliability, because this service tells me if everything burns/ goes awry. That’s not the service I’d like to “toy” with. And hosting any kind of mail service with 98% availability and 99,99% reliability, automatic DKIM roll-over etc. is a tough nut. Even VPS cost’s seem higher than just Amazon SES.
For alerts I just have the server directly send email over SMTP to my address, no service needed. You could implement DKIM with such a setup if you wanted to.
Sure - but that would be another thing to self-host - because I have at least 5 machines which need to send, and I have a dynamic IP address - so it would involve updating the MX records via DNS API for at least 5 sub domains.
To be honest, I’m a KISS kind of guy - not everything technical possible or imaginable is worthwhile. Especially if it’s such a crucial part like alert monitoring. I want it done simple, secure, without caveats and keeping the complexity on the lowest level possible.
Most distro provide either EXIM or Postfix installed by default, and configured to send outbound emails from localhost. All you need to do is start the service, change
/etc/aliases
to addroot:
and runnewaliases
.You don’t need MX records for that. MX is only needed to receive emails on a domain. Worst case is your monitoring emails will end up in spam (because there’s no SPF configured for your machine), but your spam filter will eventually accept them as you move them from the spam folder to inbox.
Pretty KISS in my opinion. More than changing all your apps to use an external relay, setup accounts, yada yada…
My bad, I meant SPF record.
I have some issue with just that, all emails will end up in a spam filter (if your mail provider is thorough). Also your IP might end up on a public spam/ block list. To much to go wrong, in case some alerts need to reach me.
Plus I use a strict DMARC, so at least a correct SPF is needed.
I’m using postfix on my machines, all services send to it and it just to relays via a SMTP service. So only one point to configure.
I was specifically looking for the last part, a SMTP relay service.
As you please ;)
Be aware that I’ve been doing that for all my servers for the past 5 years and it works like a charm. I run OpenBSD, and only need to
rcctl start smtpd
to start sending outbound emails.They’re all sent from “root@host.domain.tld”, which have neither SPF nor DMARK records, and end up in my inbox no problem (I use spamassassin as my spam filter). They won’t end up on Blocklist as the volume is just waaayyyyyyy too low anyway.