I wouldnt say that. however setting uo your own mail server is a lot of work, as you have to abide a lot of "security" rules (SPF, DKIM, DMARC, rDNS). Additionally some hosters reuire you to apply for port 25 to be unblocked (e.g. hetzner)
Selfhosted
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:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
The set up isn't actually hard at all, if you understand the concepts. Keeping off blacklists is the hard part, as big providers often block entire IP ranges due to one bad actor.
Edit: I meant sometimes your server gets blacklisted for something some neighboring server did
Well I did set one up today and the mails land in the spam folder for GMX, GMail and Microsoft (@live.de), although I set up SPF, rDNS, and DKIM. I have to take a look at how to setup DMARC, beacause my domain hoster doesn't allow free configuration of the TXT entries, you have to use templates and there isn't one for DMARC
Couple things that I've found out,
- Gmail seems to need your server to have IPv6 with PTR, even if the mail is sent over IPv4
- Even a DMARC record with no ruf or rua helps lower the spam score
- For Outlook you need to send some mail to yourself or someone else and mark the messages as not spam manually for a while
- MS365 will even put mails from Gmail to spam initially
- Some TLDs like .xyz will go to spam even if everything is set up perfectly
- Outlook also seems to cache DNS quite long, you may need to wait a day for changes to propagate
- A recently registered domain will land in spam more easily, if it has been registered for a while it also seems to help
If you're not already familiar with these, https://mxtoolbox.com/SuperTool.aspx (write smtp:your.mx.record
is a good tool, and I've also used https://www.mail-tester.com/. Mxtoolbox blacklist check is also good.
I hate it that spammers have made hosting email such a hassle. Hope you get stuff running!
Not sure if you’re hosting on AWS (if yes, free for the first 62k/month), else the $0.10/1k/month shouldn’t be too bad - https://aws.amazon.com/ses/pricing/
From my past experience with Sendgrid, it is trash, most of their shared IPs have poor reputation anyways, had lots of issues with them.
Running your own email server might be a good learning experience, a quick search brought up this all-in-one container solution - https://mailu.io/2.0/
Messing about with Postfix directly could be a painful experience, but yet another possibility.
Either way, new IPs will probably take some time to warm up, so don’t expect full deliverability for the first few days/weeks.
You should check that your cloud provider doesn’t block outgoing smtp traffic - iirc digital ocean and GCP do block.
I’m piggybacking off of a mail server for a domain I run. My instance is small though so I’m not worried about a flood of emails.
If you are hosting public instances where you're sending emails out, you'll probably want to pay for transactional email providers like sendgrid as you've flagged. Sending large amount of email out yourself while ensuring high deliverability rating is doable, but will often result in more headache than cost savings.