I’ve been using SMTP2Go at work for our low volume of notifications and it works fantastic
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.
I am in the exact same boat. I just switched to Proton as it looked like they had these features right away. But it turns out you have to explain what you want to use smtp for before they allow you to generate tokens. Which is probably due to them attracting a high amount of scammers due to their really good privacy. So I can understand but it is a tad annoying. If you are willing to wait I'd give them a try. Their business plan is cheaper than googles and gives you a lot and they are open source.
Good to know, thank you. I looked into proton for my primary mail account, but I didn't think of it for that purpose.
Nevermind. After days of back and forth with them they said that they only have that feature available to big companies that have an account with them for a year or more, which is definitely annoying. I'm going to give Brevo a shot next, I heard someone mention them in a thread before about this. It looks like their free tier allows for 300 emails a day. I'll let you know how that goes if you are still looking.
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.
SES is pretty solid and easy to work with. Free for small email volumes like your use case.
You need to verify your domain and request production access explaining your use-case. If you're only sending to known recipients, you can just verify them and not worry about the "production access".
A little note on that: Amazon SES free tier is going to change starting tomorrow though. It changed from free to free for 12 months (with adjusted limits), see https://devclass.com/2023/06/23/aws-to-remove-62000-message-simple-email-service-always-free-tier-from-august-2023/
After the pricing change, I believe it's still free (or negligible) for low email traffic.
5,000 emails per month are still free, at $0.07 per 1,000 after that.
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 add root: and run newaliases.
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.
I use mailgun at the moment. Still free for me and I send 2-3 mails per day. I had problems once with some mails not arriving or landing in spam, but that was fixed after a day or so.
Edit: Just checked the dashboard and I'm getting 1000 mails per month for free. Can't find exactly where they offer this plan anymore though, so they might have removed that.
Was signed up there as well, when they started like years ago. But I couldn’t get back into their free tier.
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!