|
|
|
|
|
|
by maltalex
2909 days ago
|
|
|
> It's not tricky, it's tedious. There's nothing tricky about it. You need a static IP, reverse DNS set to system hostname, "regular" DNS for the system hostname, DNS SPF entry, DKIM, DMARC, and authentication - it can get complex but it's quite straightforward. Plus you need to know a thing or two about linux administration, security, high availability (kinda, since short outages are tolerated by smtp), backups, spam, dealing with having your IP blacklisted and probably a few other things. Oh, and then there are the periodic updates, hacking attempts, vm reboots... None of this is rocket science and it's probably fairly easy to get started, but it'll be hard to beat the security and reliability of a professionally managed service. |
|
|
Depends what kind of security, availability is a part of it. When you forget your password (or it gets hacked and someone changes it), you can just re-deploy the whole thing. On Gmail you might be screwed. On self-deploy backups seem mandatory, which mail user backs up his or her E-Mails?
As far as I have heard, if SPF, DKIM etc etc is properly configured, blocking won't happen. I don't have this running yet but this is my next project. Probably I'll go with postfix, there are bizillion plugins for exactly these things and the configuration will be automated with Ansible. So once it's up and running, I expect this to be pretty much care-free.