This looks like something worth combining with alps[0] for easy self-hosted email. I might give it a go and ditch gsuite!
[0] https://github.com/tomav/docker-mailserver [1] https://github.com/containrrr/watchtower
I used to be a Kolab [2] user and "promoter" for many years but the project seems stalled a bit recently and although it is still being worked on and developed, it is lacking documentation for the latest releases.
I have moved to mailcow recently and am amazed at how easy it is to setup and maintain as opposed to Kolab.
The thing I miss from Kolab in mailcow is the integrated LDAP storage and custom built UI (if anyone knows a good and reliable LDAP administration UI as a web app, please let me know!), which I got used to using for user authentication in other services. Luckily, there are some efforts in LDAP integration into mailcow [3], although, still not mature yet and not that tightly integrated.
[0] https://mailcow.email/ [1] https://sogo.nu/ [2] https://kolab.org/ [3] https://github.com/Programmierus/ldap-mailcow
Another good alternative is migadu (who sponsored the webmail you linked above, and IIRC are already using it). They do charge about $20/year for a micro plan that lets you have any number of addresses and domains , with some throughput limits, and $90/year for a full plan without those limits. Something similar to the micro plan was free until recently - personally, I'm on the $90 plan with a few domains and emails, which would have cost about 10 times on much on gsuite and fastmail.
It is not me. Just wanted to give a little tribute to the amazing person who put a lot of work into email libraries for Go: https://github.com/emersion/
I'm hoping to use a Golang-based application as a simple SMTP Relay, which also allows for ranges of IP addresses to be whitelisted to connect openly to it from within our campus network.
Basically, the scenario is as follows: a number of internal services are older and may not support the authenticated route so we can use Sendgrid directly and send emails securely, so instead we currently have them routed to an internal Windows server which is running an older piece of IIS functionality (it's an SMTP Server in Windows that can be turned on). That piece is configured to be open (so it can receive messages on Port 25) but is also limited to a set of IP address ranges that internal servers are using (so that it's not generally usable by just anyone inside our network) and is configured to send those received messages out using Sendgrid.
I found the following Goland project just a few months back that seemed promising: https://github.com/wiggin77/mailrelay
And I'll probably need to follow up with the developer again (or try and make the contribution back to the project on my own), but the main issue it had was that the IP range whitelisting wasn't available (and even whitelisting by specific IP addresses seemed problematic, so in my testing I had to keep it completely open for it to work as expected).
If Maddy can fulfill the need instead though I can give it a shot ;-).
That is rather than a timeout or connection refused, an smtp 550 or 530 error with exlenation (access/relay denied; client ip not in whitelist)?
Though I admit that for someone who did not tinker with UNIX for years, configuring this kind of setup might be daunting.
Personal mail could be solved by some kind of daemon which provides SMTP, IMAP, built-in spam detection, DNS checks, some simple administration web interface and works with 0 configuration for typical use-cases. Maddy could be this project, so I would be happy to replace all those daemons with a single binary. I hope that they'll implement spam detection, as rspamd is a separate daemon which requires redis, so in the end it's still a complex setup with lots of moving parts.
https://battlepenguin.com/tech/how-google-and-microsoft-made...
I still prefer to host my own though.
Great article btw!
P.S. As far as I am aware, redis is optional for rspamd. I certainly run it for @hexanet.dev email without having redis installed.
I recently switched to Fastmail, and one of the features I like about them is that they support wildcard sender aliases, so if I sign up for a service with someservice@mydomain.com, when I hit reply to any emails to that address, it automatically sends from someservice@mydomain.com even though I've never specifically registered that identity with Fastmail.
[0] https://thedigitalnonprofit.com/use-gmail-own-domain-free/
Also, while aliases in gmail work generally, I find they leak the main gmail account address, which makes them significantly less desirable.
You can just head over to the "External DNS" page where MIAB will tell you what DNS entries you need and what each entry does. Then you just copy the DNS entries you need.
Intellectually, I don't like domain DNS on the same box; practically speaking? It works and works well -- so well that it's often easier to disable per-domain DNS where my sites are hosted and just point A records over to the sites from MAIB.
Original reply:
Buying domain hosting gives you "unlimited" email addresses, so domain hosting is cheaper as soon as you need 3 or more addresses.
3 addresses x $2 = $6/mo for email vs $4.95/mo for any number of addresses. I have a friend who is married with 4 children. He pays $4.95/mo for 6 addresses. You don't have to actually host an http domain to get email hosting that comes with domain hosting.
"unlimited" in quotes because obviously there are some limits and service terms. You can't start a competitor to gmail with a $4.95/mo hosting account.
There are tons of other options. Mailbox.org, Migadu, Protonmail, Tutanota and Mailfence for example.
Great service, E2E for everything, including contacts and calendar, and it's quite cheap (I think I pay €12/year).
This seems good, however for 5+ it becomes expensive too.
Is this service related to what you linked?