M. wrote:
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.
3. mailserver$ echo "" | mail -s test [EMAIL PROTECTED]
at this point postfix doesn't check MX record for mydomain.com because
it exists in virtual domains maps so postfix performs local delivery.
4. user can add *any* domain he wants to my postfix's virtual domains
maps by perl script. If that particular domain is listed in virtual
domains maps postfix will not check MX record. I want to avoid it. I
need to force postfix to use DNS before checking internal maps.
what Brian tried to tell you is to make the checks in the script that
adds the domains, instead of doing this for every mail transaction.
That was my first guess, but it can't be done because there is huge
latency during updating DNS records. It is more complicated than it
seems to be.
Latency is part of DNS. so refusing to add the domain before it appears
in DNS is more than acceptable. if user wants to do testing, provide a
different server and tell them to use it.
last time I asked for a PTR, I was asked to set the corresponding A
first and wait until it propagates. I found this reasonable (I even
found it a good procedure!).
Trust me, this problem in my case, cannot be fixed in
scripts.
if you don't want to change the provisioning process, you'll need some
amount of work to get things right (multiple instances or servers, a
policy service, ... etc).