Wietse Venema wrote, at 11/03/2008 03:06 PM:
> M.:
>> On Mon, 2008-11-03 at 19:32 +0100, mouss wrote:
>>> and the problem is? If they "control the domain", then you have no problem!
>> OK, I will try to explain that by example:
>>
>> 0. user buys domain mydomain.com
>>
>> 1. user adds mx record mailserver.com to his domain
>>
>> 2. user adds (by perl script) entry to virtual domains maps in my
>> postfix (mailserver.com) to inform postfix that it is final destination
>> for this domain. 
> 
> Before allowing step 2 to proceed, your provisioning system should
> check that your system is listed as MX server for this domain.
> 
> It makes no sense to do that check upon every mail transaction.
> 
>       Wietse

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.

Reply via email to