3 ms·
I've done both vanilla postfix, dovecot, rspamd, etc and mailcow. For me the reason I use mailcow is it's a few commands and I have a fully functional mail, ca
by rbut 3y ago
I've done both vanilla postfix, dovecot, rspamd, etc and mailcow.
For me the reason I use mailcow is it's a few commands and I have a fully functional mail, calendar, and contacts server with a web UI. It can then be updated with a single update.sh.
Using mailcow I don't need to mess around with virtual domains, connecting it to mysql, DKIM, etc which is far more than a few commands.
I also get a nice admin UI, web mail and CalDAV and CardDAV which you don't get with the above.
Also I'd consider the separate containers a good thing so that if rspamd, or clamav, for example, has a CVE they can't pivot to other parts of your mailserver.
- muppetman 3y agoYou make a good point, especially around isolation. While I use docker and I know the basics of it, I'd hate to try and debug it if something went wrong (i.e. postfix container wouldn't start). For that reason I've stayed clear of using it for "critical" life things, like our email. For a number of years there my wife's business email I was also sending through my mailserver, so it needed to be super reliable. I'm not saying docker/mailcow isn't reliable, only that if it did break in funky ways, I don't have the knowledge domain to fix it. But I'm familiar with all the individual programs and running them on a "flat" linux system, so that's what I did. But yes, you certainly make some good points that are worth considering if someone else is reading these comments and thinking about doing it themselves!