I have been running mailinabox with a hetzner server for 2-3 years now.
- Setup was largely painless. Main problem was making sure dns settings at my domain registrar were correct.
- Almost zero problems with mail delivery on the big providers [1]. Last time my email was dropped was by amd.com.
- Last year had to do a major version upgrade to mailinabox and it was a huge hassle. I think they need to improve on this. Rolling updates are painless.
Here is my advice to people who are on the threshold of wanting to host their own email, but are unsure because of mail delivery issues. Well, there are zero problems with incoming mail. So setup mailinabox and use that email to register for websites [2]. Use it for all your mailing lists etc.
Do it for a few years and see how it feels. Occasionally send out email. If enough people do it, then over time it will become easier for more people to host their own email.
[1] I have a theory that I deployed. I asked a whole bunch of people with gmail/hotmail email addresses to send me emails first on my new email. I then replied to them. I think this ensured that from that start I was put on the good lists.
It was flat out impossible for me to get Outlook to accept my mail server. They'd only give me some vague response with no actionable steps to resolve it. I gave up and used a gmail account to route everything outgoing. That way mail still shows up as from:[email protected] but rides on Google's reputation. Defeats the purpose a little but there's nothing more I can do (apparently unless I buy my own non residential ISP line, host the server in my house, and build reputatiom forever, but that's an absurd length to have to go through. ideally we'd have antitrust legislation forcing MS et al to be fair towards smaller email and save the open internet overall, but I'm not holding my breath.).
They have something weird going on. I had to make an account with them to redeem a game key, and they wouldn't deliver the account verification email to my custom domain hosted by Fastmail. I used a gmail address and the email came instantly. Then out of the blue 24h later the emails to my custom domain were delivered (by which time the verification codes had all expired, of course).
I've done MiaB from 2015-2017, and I've always had deliverability issues from Digital Ocean. Microsoft is particularly nasty, and Gmail kept marking me as spam silently instead of rejecting mail.
I've decided to just move on and pay Fastmail. Email isn't private anyway.
A thousand times this! Everyone even remotely technical or interested in tech should run their own mail server.
For anyone too young to have known, this is how it used to be. Email was desktop (workstation) to desktop. Even when working at large corporations in the 90s, email arrived and was sent to the world directly from my personal workstation.
For anyone worried about deliverability, keep in mind you can outsource the delivery part while still running your own email server for incoming email.
I have experimented with using mailjet as an outgoing relay, for low volumes it was (maybe still?) free. I don't use a relay though, I deliver everything directly. But you don't have to if you worry about delivery.
Why would you do this? For one thing, as parent post says, it gets you used to running the server.
But much more importantly, it gives you complete control of incoming email. Never again is there any chance of google/yahoo/microsoft locking you out of receiving important emails (account resets, bank statements, etc) when you own the receiving server.
Over time you can start relaxing the relaying and deliver directly to most places, only keep the relay to those who give you trouble coughmicrosoftcough.
Or keep the outgoing relay forever if you prefer, but still reap all the benefits of owning the receiving side which is arguably more important.
My experience has been that MAIB version updates are usually very smooth. Regular OS update (apt update/apt install) are smooth. The big problem is that the recommended path is to install on a fresh system when moving between OS versions. In the most recent release that required that, I actually did an in-place upgrade of the OS by running do-release-upgrade twice and leaving the config files as-is. I followed some steps that were posted on the forum. I ran into one or two minor issues but they were the sorts of things I'd expect to see running an "unsupported" upgrade. Other than the OS updates which just take time to download and install, the total work doing it this unofficial way was maybe a couple of hours. That's necessary every 2-3 years, I think?
I do have a few things that I've customized. Updates to MIAB will overwrite them if they're involved in the services it provides. Recently NextCloud updates have been better about removing all of your plugins. The only problem I ever had with it during an update was when the SQLite DB got corrupt. That basically made it so you had to reset NextCloud.
> - Last year had to do a major version upgrade to mailinabox and it was a huge hassle. I think they need to improve on this. Rolling updates are painless.
Ran into this too, multiple times. Just not worth it if it breaks the underlying OS.
Your [2] note about using website names in emails is an awesome but underrated benefit. I’ve been doing that with hey.com email at the moment. (Using a custom domain, any address that doesn’t have an inbox goes into the “catch all” box. I can upgrade an address to a real one by setting up a free alias address which is pretty simple in their UI.)
I’ve only caught one sold email being used for spam so far (sketchy wristwatch store that wanted an email to unlock some discount I never used) but really happy I’ll know about the next one.
Used MIAB for years -- one install, about 20 domains, most low volume but 1-2 sending tens of thousands of emails a month. Some notes:
* Every thread that mentions hosting your own email brings out the it's-pointless-do-do-your-own-mail zealots; ignore them. If you're interested in trying it, try it.
* The only deliverability issues I ever had were with ATT networks because they don't use modern TLS; that was fixable. Mail to Google? Goes through, doesn't go into spam. Mail to Microsoft? Ditto. And this is on a Digital Ocean VM, which isn't the most reputable IP pool in the world.
* MIAB will happily be your full-fledged authoritative DNS server. Although I've since migrated to separating DNS from mail hosting, it was very convenient for a long time.
* Setup is dirt simple. And you get MTA-STS as well as DANE/DNSSEC right out of the box.
* The backup function worked without issue the one time I needed it. I'm sufficiently paranoid that I also do regular snapshots of the whole VM.
* There's a fork, Power Mail In A Box, that updates the UI, adds the ability to plug in relayhost settings, and does a few other nice things. It hasn't been updated in about a year, but was similarly solid.
My only quibble with MIAB, and the reason I migrated to Mailcow recently, is that I wanted to easily set up per-domain relay settings from the UI.
I'm on the fence. I wanted to do a super simple app hosting service on the Odroid SBC. I have few services running, but two of them: Authelia and Gitea need smtp for some actually valid reason.
This isn't the kind of thing I'd run - I'm still running old school Sendmail, IMAP-UW and Cyrus SASL - but it's good to see resources that make hosting email more accessible to everyone.
There are altogether too many people who think it's their place to tell others they *shouldn't* self host email, and I think that's a horrible take. It's not too different from saying, "I couldn't learn Finnish, so you shouldn't even try".
Actual, technical objections are fine, but most of the time objections brought up by gatekeepery people just show a lack of understanding and experience. For instance, the most common is "you'll never be able to deliver to...", which is ridiculous. Even if you're on a network that has a bad reputation, you can always smarthost through other providers, and you'll still have all the advantages of having logs and your own filters for incoming email, plus the security of possessing your own data.
The Internet is a better place when less centralized, so it's nice to know that we still have people who haven't thrown their hands in the air and given up to Google / Microsoft / Amazon :)
ISPmail/workaround.org is how I got serious with self hosting my emails 10/15? years ago. Really good starting ressource if you want to know how all the internals of a mailserver work
I've been using maddy.email running quietly on my RPi for a couple of years now. I think it's 'simpler' than mail-in-a-box because it implements IMAP, SMTP, all in one server which can be backed by a database, instead of managing installation and updates of many different programs. It also does DKIM automatically and uses ACME/LetsEncrypt to automate certificate management.
It doesn't have as many features as mail-in-a-box though for a example no webmail or Cal/CardDAV, so I have to run those separately. It would be great to extend the project
Another similar project is stalw.art mail server. I haven't used that yet but it looks promising, and it supports JMAP (a possible IMAP successor)
I am also using Maddy so my programs can email me with notifications (I'm not using it to email anyone else) and it has been great.
One thing about Mail-in-a-Box is you have to dedicate your entire machine to being MAIB, whereas Maddy is just a regular program you can run along with everything else.
At this point Stalwart and rspamd two combined will most likely offer a better experience. In terms of supporting modern standards, security and offering enough configurability without requiring arcane knowledge. You can get a good setup with way less effort and fragile components.
The hodgepodge of software used by MIB is just not good any more.
Also Stalwart Mail supports JMAP which is a nice protocol. Not sure how many email clients support it yet though. If I were to host my own mail I'd probably go with Stalwart as it provides a single binary/service for running imap, jmap, smtp, etc. No need to fiddle around with Postfix, Dovecot, etc.
This is awesome! Have really been thinking about this a lot lately, and my SES->Google Workspace solution works, but isn't viable if we ever left Google Workspace. I might set one up because abdullahkahlids' statement is compelling and correct: "If enough people do it, then over time it will become easier for more people to host their own email." (Plenty folks did this in the heady 90s...)
A few questions:
- I see that it seems to require Ubuntu, assuming this would work on Debian as well without too many needed tweaks? And are there plans to support CentOS? Ubuntu is my daily driver as a desktop OS, but I rarely use it for server apps due to all the "extra stuff" installed and the network stack is slower out-of-the-box than CentOS and I am usually too lazy to do anything about that other than put my server stuff on CentOS.
- Is more documentation available (especially a hardening guide)? For example, I see that Munin's installed (huge fan of Munin, but I'd want to firewall it off for sure), Roundcube used as the front-end management, there are variables you'd want to configure (like support email), I'd probably want to not have sieve open to the world, etc. Basically, I'd love to see a concise list of services and open ports at minimum, so I could figure out what to omit from installation and what to firewall off.
I JUST finished my server migration 2 days ago. Because the configuration was such a hassle I just duplicated my setup. Why wasn't this posted like 2 months ago when I started?
I could have tried this so easily on the new server before moving from the old one.
I am using a traditional provider as "frontend SMTP". Decided against doing my own because I need to send and receive emails for job hunting atm.
I operated an email forwarding services[1] and have research this area extensively because eventually customer will keep asking for IMAP.
When hosting email, receiving is easy part. But storing and fetching it is hard.
Sending out, on other side, is hard to configure but easy to store(there is not much to store except DKIM config).
But the hardest part is actually getting providrs to accept your email. I always had issue with ProofPoint and Outlook(Microsoft 365).
I also have issue with 800 emails per hours on fastmail.
Lot of thing like that come up when hosting your own emails.
However, it's worthed it, it open a lot of amazing thing once you own your own email.
With that being said, I recomend Maddy https://maddy.email/ it's a very simple deployment that handle pretty much everything. No need to glue multiple system together.
Does anyone have a recommendation about where to host an internet-facing mail server? I've been running my own mail server on various VSPs (digital ocean and linode), but sending email is not quite as reliable as I'd like it to be.
Are there different hosts I could try? Or am I better off paying for something like fastmail and using them as a smarthost?
N.B. this may only work with hosts that don't use UCEProtect and, honestly, if they're legit, they won't use UCEProtect
I have two email servers running on Digital Ocean just fine - one set up in 2016 and one set up in 2021. It's a matter of doing the initial work to deal with the rejections - following the process the various hosts have set up. There will be a few block lists that you need to submit tickets to to have your IP unblocked. You'll want to create bulk sender accounts (even if you're not) with Yahoo, Microsoft, and Google. It's mostly superstition - "may this web form bring blessings upon my IP". Don't bother actually trying to check any of the reports in the UIs - only Yahoo sends emails to abuse@ for spam reports for small senders.
You'll want to join the Mailop list [0]. I'd say it takes about a month or two, mostly spent waiting, before you are in the clear and have perfect deliverability. Yes, it's annoying. Yes, it can feel hopeless. But it clears up pretty quickly. I've only since had problems with smaller providers and it usually gets resolved by contacting them.
[0]: https://www.mailop.org/ - I think people who work at Yahoo, Google, and Microsoft all monitor this list
If you've got a sensible ISP, you can host from home just fine.
You'll need an ISP who can permit traffic on port 25 (usually blocked for domestic connections); a "static" IP address really is necessary (a fixed address, not behind a NAT); and your ISP must be able to handle your reverse DNS entries (IPv4 and IPv6). Any ISP who can handle commercial customers will be able to do all that. And a UPS power source is highly recommended.
In some ways, email is a good place to start self hosting. It's based on store-and-forward, so you can be down for a while ... and when you come back up, any stored email will be delivered :)
But be aware of security, and don't let your server become a spam relay!
Smarthosting is the best solution since it prevents the necessity of being at the whim of rather shitty companies that only take action when things get really bad, like Digital Ocean.
I host my own mail server on Vultr. One thing to note if you want to use them is that, by default, they block outgoing SMTP ports by default. You have to file a support ticket to unlock that port for your account, and you need to have a server running under your account on their infrastructure for at least a month before they'll unblock the port.
It's a bit annoying, but they do it to prevent people from using their infrastructure to send spam. And you only ever have to do it once.
I'd say Mail-in-a-Box, along with Modoboa and iRedMail, are perhaps the only serious open source email server setups right now, that are not based on Docker. Commercial ones do exist in the form of cPanel and Plesk (if you need some sort of support), although the underlying software is pretty much the same.
The only downside with MiaB is it is unnecessary complicated to update (both the software AND the server OS). This shouldn't be too hard to address in the future...
Jumping into the Mail-in-a-Box discussion: setting it up is pretty smooth, but watch out for those tricky DNS settings. If you're battling with Outlook acceptance, you're not alone - seems like a common headache. Some folks just route through Gmail to dodge the hassle. And hey, if you're looking for a cheap alternative, AWS SES might just be your ticket. So, whether you're DIY-ing your email server or seeking easier routes, the email server world's got a bit of everything. Stay nimble!
I ran a miab for about 5 years, maybe around 2018, I also actively tried to do extra things that would improve delivery, including registering postmaster accounts on the various postmaster whitelist tools etc in order to increase the chances my mail would be delivered.
Unfortunately if you host your mail on linode/digital ocean, you will eventually be blocked, and mst of your email will end up in spam folders.
This year after 13 years of running my own mail services, I finally gave up, I was sending emails and then sending followup “did you get my email” messages from gmail
I've since moved from SOGo to grommunio[0]. It's Activesync support is great, far better than SOGo, and supports MAPI for Outlook and they'ved just released EWS support for Apple Mail / Outlook for Mac. Couldn't be happier. The other parts are fairly standard, rspamd, postfix etc.
On a somewhat different note, I have been using iCloud custom domain hosting feature. The spam filtering is horrendous. Anyone else has this problem? I am tired of checking the spam folder everyday and I find legitimate emails almost 2-3 days a week. Of course, I click on not-spam but I think Apple's servers just don't learn very well (maybe due to focus on privacy?)
I’ve definitely seen an increase in Spam filtering issues on iCloud.
I recently emailed a new contact for the first time and their reply to my email went into the Junk folder. How does that happen?
This last week I’ve had two other emails from people that I’ve corresponded with for years go into Junk.
Given how poor iCloud Webmail is - to the degree that it looks like Apple simply doesn’t care about it as a product… at all… I’m not surprised if the internals are being neglected too.
I've been using mail in a box since 2016 for a handful of personal domains.
It's easy to setup and very low maintenance. Backups are solid too.
Just make sure your hosting package/provider allows and supports self-hosted mail. PTR dns records specifically as without your mail might work but much ends up in spam boxes.
The mail in a box setup guide covers this too.
[+] [-] abdullahkhalids|2 years ago|reply
- Setup was largely painless. Main problem was making sure dns settings at my domain registrar were correct.
- Almost zero problems with mail delivery on the big providers [1]. Last time my email was dropped was by amd.com.
- Last year had to do a major version upgrade to mailinabox and it was a huge hassle. I think they need to improve on this. Rolling updates are painless.
Here is my advice to people who are on the threshold of wanting to host their own email, but are unsure because of mail delivery issues. Well, there are zero problems with incoming mail. So setup mailinabox and use that email to register for websites [2]. Use it for all your mailing lists etc.
Do it for a few years and see how it feels. Occasionally send out email. If enough people do it, then over time it will become easier for more people to host their own email.
[1] I have a theory that I deployed. I asked a whole bunch of people with gmail/hotmail email addresses to send me emails first on my new email. I then replied to them. I think this ensured that from that start I was put on the good lists.
[2] Use [email protected] to register. Easy to block spam this way.
[+] [-] jimmaswell|2 years ago|reply
https://news.ycombinator.com/item?id=35691618
[+] [-] Arnavion|2 years ago|reply
They have something weird going on. I had to make an account with them to redeem a game key, and they wouldn't deliver the account verification email to my custom domain hosted by Fastmail. I used a gmail address and the email came instantly. Then out of the blue 24h later the emails to my custom domain were delivered (by which time the verification codes had all expired, of course).
I saw a bunch of discussion where other people reported the same thing like https://old.reddit.com/r/AMDHelp/comments/yr9tqq/amd_rewards... - they got emails instantly when they switched to gmail but other domains didn't work.
[+] [-] asmor|2 years ago|reply
I've decided to just move on and pay Fastmail. Email isn't private anyway.
[+] [-] jjav|2 years ago|reply
A thousand times this! Everyone even remotely technical or interested in tech should run their own mail server.
For anyone too young to have known, this is how it used to be. Email was desktop (workstation) to desktop. Even when working at large corporations in the 90s, email arrived and was sent to the world directly from my personal workstation.
For anyone worried about deliverability, keep in mind you can outsource the delivery part while still running your own email server for incoming email.
I have experimented with using mailjet as an outgoing relay, for low volumes it was (maybe still?) free. I don't use a relay though, I deliver everything directly. But you don't have to if you worry about delivery.
Why would you do this? For one thing, as parent post says, it gets you used to running the server.
But much more importantly, it gives you complete control of incoming email. Never again is there any chance of google/yahoo/microsoft locking you out of receiving important emails (account resets, bank statements, etc) when you own the receiving server.
Over time you can start relaxing the relaying and deliver directly to most places, only keep the relay to those who give you trouble coughmicrosoftcough.
Or keep the outgoing relay forever if you prefer, but still reap all the benefits of owning the receiving side which is arguably more important.
[+] [-] ajosh|2 years ago|reply
I do have a few things that I've customized. Updates to MIAB will overwrite them if they're involved in the services it provides. Recently NextCloud updates have been better about removing all of your plugins. The only problem I ever had with it during an update was when the SQLite DB got corrupt. That basically made it so you had to reset NextCloud.
[+] [-] gunapologist99|2 years ago|reply
Ran into this too, multiple times. Just not worth it if it breaks the underlying OS.
[+] [-] graypegg|2 years ago|reply
I’ve only caught one sold email being used for spam so far (sketchy wristwatch store that wanted an email to unlock some discount I never used) but really happy I’ll know about the next one.
[+] [-] gwbrooks|2 years ago|reply
* Every thread that mentions hosting your own email brings out the it's-pointless-do-do-your-own-mail zealots; ignore them. If you're interested in trying it, try it.
* The only deliverability issues I ever had were with ATT networks because they don't use modern TLS; that was fixable. Mail to Google? Goes through, doesn't go into spam. Mail to Microsoft? Ditto. And this is on a Digital Ocean VM, which isn't the most reputable IP pool in the world.
* MIAB will happily be your full-fledged authoritative DNS server. Although I've since migrated to separating DNS from mail hosting, it was very convenient for a long time.
* Setup is dirt simple. And you get MTA-STS as well as DANE/DNSSEC right out of the box.
* The backup function worked without issue the one time I needed it. I'm sufficiently paranoid that I also do regular snapshots of the whole VM.
* There's a fork, Power Mail In A Box, that updates the UI, adds the ability to plug in relayhost settings, and does a few other nice things. It hasn't been updated in about a year, but was similarly solid.
My only quibble with MIAB, and the reason I migrated to Mailcow recently, is that I wanted to easily set up per-domain relay settings from the UI.
[+] [-] brightball|2 years ago|reply
[+] [-] eurekin|2 years ago|reply
Would you recommend hosting for that use case?
[+] [-] johnklos|2 years ago|reply
There are altogether too many people who think it's their place to tell others they *shouldn't* self host email, and I think that's a horrible take. It's not too different from saying, "I couldn't learn Finnish, so you shouldn't even try".
Actual, technical objections are fine, but most of the time objections brought up by gatekeepery people just show a lack of understanding and experience. For instance, the most common is "you'll never be able to deliver to...", which is ridiculous. Even if you're on a network that has a bad reputation, you can always smarthost through other providers, and you'll still have all the advantages of having logs and your own filters for incoming email, plus the security of possessing your own data.
The Internet is a better place when less centralized, so it's nice to know that we still have people who haven't thrown their hands in the air and given up to Google / Microsoft / Amazon :)
[+] [-] throw0101b|2 years ago|reply
* https://workaround.org
* https://workaround.org/ispmail-bookworm/
Ansible playbook(s) available:
* https://github.com/Signum/ispmail-bookworm-ansible
[+] [-] Kirce|2 years ago|reply
[+] [-] mfashby|2 years ago|reply
It doesn't have as many features as mail-in-a-box though for a example no webmail or Cal/CardDAV, so I have to run those separately. It would be great to extend the project
Another similar project is stalw.art mail server. I haven't used that yet but it looks promising, and it supports JMAP (a possible IMAP successor)
[+] [-] voussoir|2 years ago|reply
One thing about Mail-in-a-Box is you have to dedicate your entire machine to being MAIB, whereas Maddy is just a regular program you can run along with everything else.
[+] [-] robwwilliams|2 years ago|reply
https://poolp.org/posts/2019-08-30/you-should-not-run-your-m...
[+] [-] type_Ben_struct|2 years ago|reply
[+] [-] Avamander|2 years ago|reply
The hodgepodge of software used by MIB is just not good any more.
[+] [-] snorremd|2 years ago|reply
[+] [-] jen_h|2 years ago|reply
A few questions:
- I see that it seems to require Ubuntu, assuming this would work on Debian as well without too many needed tweaks? And are there plans to support CentOS? Ubuntu is my daily driver as a desktop OS, but I rarely use it for server apps due to all the "extra stuff" installed and the network stack is slower out-of-the-box than CentOS and I am usually too lazy to do anything about that other than put my server stuff on CentOS.
- Is more documentation available (especially a hardening guide)? For example, I see that Munin's installed (huge fan of Munin, but I'd want to firewall it off for sure), Roundcube used as the front-end management, there are variables you'd want to configure (like support email), I'd probably want to not have sieve open to the world, etc. Basically, I'd love to see a concise list of services and open ports at minimum, so I could figure out what to omit from installation and what to firewall off.
[+] [-] pdntspa|2 years ago|reply
[+] [-] blkhawk|2 years ago|reply
I could have tried this so easily on the new server before moving from the old one.
I am using a traditional provider as "frontend SMTP". Decided against doing my own because I need to send and receive emails for job hunting atm.
[+] [-] kureikain|2 years ago|reply
When hosting email, receiving is easy part. But storing and fetching it is hard. Sending out, on other side, is hard to configure but easy to store(there is not much to store except DKIM config).
But the hardest part is actually getting providrs to accept your email. I always had issue with ProofPoint and Outlook(Microsoft 365).
I also have issue with 800 emails per hours on fastmail.
Lot of thing like that come up when hosting your own emails.
However, it's worthed it, it open a lot of amazing thing once you own your own email.
With that being said, I recomend Maddy https://maddy.email/ it's a very simple deployment that handle pretty much everything. No need to glue multiple system together.
For spam filering, just use RSPAMD.
---
https://mailwip.com
[+] [-] eminence32|2 years ago|reply
Are there different hosts I could try? Or am I better off paying for something like fastmail and using them as a smarthost?
[+] [-] dqv|2 years ago|reply
I have two email servers running on Digital Ocean just fine - one set up in 2016 and one set up in 2021. It's a matter of doing the initial work to deal with the rejections - following the process the various hosts have set up. There will be a few block lists that you need to submit tickets to to have your IP unblocked. You'll want to create bulk sender accounts (even if you're not) with Yahoo, Microsoft, and Google. It's mostly superstition - "may this web form bring blessings upon my IP". Don't bother actually trying to check any of the reports in the UIs - only Yahoo sends emails to abuse@ for spam reports for small senders.
You'll want to join the Mailop list [0]. I'd say it takes about a month or two, mostly spent waiting, before you are in the clear and have perfect deliverability. Yes, it's annoying. Yes, it can feel hopeless. But it clears up pretty quickly. I've only since had problems with smaller providers and it usually gets resolved by contacting them.
[0]: https://www.mailop.org/ - I think people who work at Yahoo, Google, and Microsoft all monitor this list
[+] [-] drpixie|2 years ago|reply
You'll need an ISP who can permit traffic on port 25 (usually blocked for domestic connections); a "static" IP address really is necessary (a fixed address, not behind a NAT); and your ISP must be able to handle your reverse DNS entries (IPv4 and IPv6). Any ISP who can handle commercial customers will be able to do all that. And a UPS power source is highly recommended.
In some ways, email is a good place to start self hosting. It's based on store-and-forward, so you can be down for a while ... and when you come back up, any stored email will be delivered :)
But be aware of security, and don't let your server become a spam relay!
[+] [-] johnklos|2 years ago|reply
[+] [-] zcdziura|2 years ago|reply
It's a bit annoying, but they do it to prevent people from using their infrastructure to send spam. And you only ever have to do it once.
[+] [-] oynqr|2 years ago|reply
[+] [-] fevangelou|2 years ago|reply
The only downside with MiaB is it is unnecessary complicated to update (both the software AND the server OS). This shouldn't be too hard to address in the future...
References:
https://modoboa.org/en/
https://www.iredmail.org/
[+] [-] jboynyc|2 years ago|reply
[+] [-] oriettaxx|2 years ago|reply
I use Ispconfig
they are both ordinary stuff, very very old style
(these all should be in docker swarm nowadays)
Ah, a great modern tool in front of ispconfig is proxmox mail gateway
[+] [-] JhonesTariH|2 years ago|reply
[+] [-] sammyjoe72|2 years ago|reply
Unfortunately if you host your mail on linode/digital ocean, you will eventually be blocked, and mst of your email will end up in spam folders.
This year after 13 years of running my own mail services, I finally gave up, I was sending emails and then sending followup “did you get my email” messages from gmail
[+] [-] johnklos|2 years ago|reply
So you know your own problem. Just find anyone else, or smarthost through a good provider.
[+] [-] amaccuish|2 years ago|reply
[0] https://grommunio.com/
[+] [-] gauravphoenix|2 years ago|reply
[+] [-] tailspin2019|2 years ago|reply
I recently emailed a new contact for the first time and their reply to my email went into the Junk folder. How does that happen?
This last week I’ve had two other emails from people that I’ve corresponded with for years go into Junk.
Given how poor iCloud Webmail is - to the degree that it looks like Apple simply doesn’t care about it as a product… at all… I’m not surprised if the internals are being neglected too.
I’ll be moving everything off iCloud very soon.
[+] [-] rtuin|2 years ago|reply
Just make sure your hosting package/provider allows and supports self-hosted mail. PTR dns records specifically as without your mail might work but much ends up in spam boxes. The mail in a box setup guide covers this too.
[+] [-] layer8|2 years ago|reply