3 ms·
I can second this, but it’s a full 8 hour day once per year when some spamassassin or amavis config breaks in an update... not to mention the normal sysadmin st
by sneak 8y ago
I can second this, but it’s a full 8 hour day once per year when some spamassassin or amavis config breaks in an update... not to mention the normal sysadmin stuff of backups, verifying backups, logging, monitoring, et c. It’s a big project to run a mailserver. (Source: been doing so for 21 years.)
- zAy0LfpBZLC8mAC 8y agoWell, you also need backups with a "cloud" solution, so that's no difference. As for monitoring: If you only run it for yourself or a small org, really, you can do just fine without monitoring. If the mail access side breaks, you'll notice, if the inbound side breaks, you'll probably also notice soon enough. But then, setting up a minimal monit that tells you when storage runs low or the MX is down really isn't that difficult either. So, no, it's not a big project. It's as much of a big project as owning a car, probably less so, if you consider the amount of effort/time required (assuming you have an IT background, obviously).