On Mon, Nov 03, 2008 at 09:41:17PM +0100, M. wrote:
> 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?
You are looking for the solution in the wrong place. Don't enroll
unverified domains. Requiring the MX to change first is not the
only way to verify a domain (though it is reasonable for new
domains).
--
Viktor.
Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the "Reply-To" header.
To unsubscribe from the postfix-users list, visit
http://www.postfix.org/lists.html or click the link below:
<mailto:[EMAIL PROTECTED]>
If my response solves your problem, the best way to thank me is to not
send an "it worked, thanks" follow-up. If you must respond, please put
"It worked, thanks" in the "Subject" so I can delete these quickly.
