>Unregistered domains are sometimes resolving, and sometimes not.  I wonder
>if it's because not all the root servers have updated with this new policy
>yet?

the root-servers.net are not involved.  the root-servers.net refer a query=
=20
for afalfdja=E6lfjadsj.com to gtld-servers.net that verisign runs.

There is no MX for alfja=E6lfjalfjalfjfd.com, only an A record so SAV would=
=20
run against  64.94.110.11:

# telnet 64.94.110.11 25
Trying 64.94.110.11...
Connected to 64.94.110.11.
Escape character is '^]'.
220 snubby3-wceast Snubby Mail Rejector Daemon v1.3 ready
helo angel of death
250 OK
mail from:<postmaster|a=E6lfjalfjdfa=E6lfjlkjflkd.com>
250 OK
rcpt to:<[EMAIL PROTECTED]>
550 User domain does not exist.
exit
250 OK

so SAV should still work when reject_unknown_sender_domain fails for .com=20
and .net,  unless they start having Snubby Mail Rejector accept all mail to=
=20
all users and /dev/null it, but they could be a DoS for them.

Len



Reply via email to