I came across MIAB as I was looking to replace our old Postfix server. It’s approximately 15 years old (could be even older), it’s been virtualised, moved onto numerous ESXI servers all around the country and has been pretty well bomb proof. It runs our family e-mail and has been hacked, updated, modified, changed and generally bears little resemblance to what it started life out as.
The problem is that its old, doh, the OS is years out of support, there are no patches any more and whilst it does still run on an ESXI 5.5 server, its probably time for us to move upwards and onwards.
We don’t want to try and migrate the server config as its so old (did I mention that), so we are looking around for a replacement and we’ll migrate the data and some of the ‘concepts’.
I’ve been reading through the forum as I think support forums tell an awful lot about a product, free or otherwise. It tells me that MIAB is actively supported and that the level of support is pretty informative. I also checked out some topics that are of interest to see what the answer might be.
So far I’ve installed MIAB on a Ubuntu 14.04 LTS virtual image on my Macbook. I thought I’d kick it around the block and see what it can do. I’ve not sent any emails or configured it as a MX server, but was interested in the admin pages and the functionality on them.
What I want any new mail server to do is:
Handle multiple email domains, e.g. domain1 dot com, domain2 dot com. I think MIAB does this but its a little confusing as some of the forum answers weren’t clear, yet the documentation seems pretty clear it can.
Handle somehow, no idea how, the hundreds of email address I have setup for my own use to handle things like mail list registration, e.g. if I want to subscribe to this email list, I’d use firstname.lastname@example.org. Clearly example.com is NOT the right domain, but I don’t want email scrapers to get another address. On my current Postfix installation, I have rules setup in /etc/postfix/virtual that map certain rules to a single email address, my own, this means I can subscribe to a mailing list with a unique address and then block that unique address if the mail gets harvested. I have high dozens of email address that simple goto /dev/null as the email address has been compromised. Adobe I’m looking at you!
This means I currently use regexp rules, the use of the ‘.’ as recipient_delimiter (mmm, already read the forum posts on changing from ‘+’ to ‘-’ or ‘.’), and blocking by recipient mail address blocking. I don’t think MIAB handles any of these BUT it might be possible to handle this through other means that MIAB may support. The problem is that the whole family uses this approach, and we have subscriptions going back 10 or more years. Whilst we can go forward with new ideas, I can’t simply throw away what we have done before
Multiple SSL certificates for each hosted domain. I know that LetsEncrypt can handle multi domains though the -d options as we’ve already tested that.
IMAP support, Dovecot is fine.
Sp the big issue for me is how to handle the old (and useful) email addresses. I can setup a catchall for each domain (I think) so the user can work it out, but I can’t see any way to block old addresses.
Any suggestions welcomed.