|
|
|
|
|
by gerdesj
266 days ago
|
|
DR: MX and retry email has easily one of the best responses to failure modes ever and its ancient! Most smtp daemons will put outbound emails in a queue and run the queue. If the other end is unavailable then it will generally retry on a schedule with some sort of increasing period and then give up after a week or so. You can easily define multiple inbound relays via your MX records which predate SRV and generic TXT and are supported everywhere. I've run a lot of other people's email, including my own vanity domains for decades. It really isn't rocket science. Google and MS and Co really don't screw you around if you follow the rules and that largely involves only SPF being compulsory and the rest (DKIM n that) are nice to have. If you do send spam then you will be crucified and rightly so. Email is not a critical (its important) service because of course you have several other means of communication starting off with the SIP n RTP server you also run ... 8) |
|
I've run a lot of other people's email, including my own vanity domains for decades. It really isn't rocket science.
Again, so have I, and as I said the happy path is always easy, it's when things go wrong, and I'm not even talking about IP reputation or any of the usual issues that people bring up running email.
Email is not a critical (its important) service
Really depends; I still have many services such as banking where I need to use auth codes, also a lot of security is tied to my email in terms of private comms and recovering services.
Suppose your email service went down and the people you run email for complain, do you tell them "oh don't worry it's not a critical service, you can still communicate over other mediums"? Would that work for say gmail?