On Mon, 2008-11-03 at 15:26 -0500, Jorey Bump wrote: > Although checking the MX record before provisioning would provide the > ultimate verification, it would expose the domain to the possibility of > lost mail, since it requires the customer to change the MX before the > destination is ready to accept mail (resulting in a permanent error). > This could cause problems if the customer is migrating from a working > system (but is obviously less of a problem if this is the first MX for > the domain and addresses aren't in circulation, yet). It seems to me > that, for many cases, best practice mandates that the MX record should > not point to the destination until it is ready.
Yep, this is exactly what I was thinking about ;) Maybe there is workaround to this problem using transports, relays or whatever? -- M.
