On 08/17/17 09:04, Tanstaafl wrote: > In the vast majority of cases, the perceived benefit is simply not worth > the trouble. If your server is down for more than 3 days, then you have > bigger problems, and the vast majority of the emails you would have held > will have lost their value (if they had any real value in the first > place), and the rest would have contacted the recipient by other means > when they saw the delivery warnings/failures. > > I used to set our local warning for 4 hours (before the boss decided to > migrate to Office365), because a lot of our business is time-sensitive. > > So, again, the actual benefit is generally far less than the perceived > benefit - and there is even a real cost in many cases (sender doesn't > know there is a problem), so running a backup MX, in the vast majority > of cases, is simply not a good idea.
This is nice in theory but doesn't work in practice, because not every sender particularly closely follows the applicable RFCs. Certain major mailing list hosts (not that I'd mention Sourceforge by name, for example) will, upon seeing multiple delivery failures, just drop subscribers from the list with no further attempt at notice. Depending on the mailing list this may have major real-world impact. -- Phil Stracchino Babylon Communications ph...@caerllewys.net p...@co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958
