>SIMS verifies what it can: that the claimed name resolves to the >connecting IP address.
But this is exactly the point. The claimed name (karabalta.kg) resolves to a private non-routable IP, which does not agree in any way with the connecting IP (195.38.186.2), and yet SIMS marked it as verified. And since the announced name of karabalta.kg is only a slight obfuscation of ns.karabalta.kg, I thought that SIMS might have done something more than a reverse lookup (since a reverse lookup fails) to finally give it a 'verified' mark. This is all perhaps a nitpick but the example got me to wondering just how SIMS does things in this regard. Am I missing something obvious here? > Doing more (i.e a reverse lookup) is pointless really, since you >already know that an SMTP sender using that IP claims the name, so >checking for agreement from whoever does DNS for the reverse zone is >a pretty small return at best. Understood :-) Thanks for the response. Stefan Jeglinski ############################################################# This message is sent to you because you are subscribed to the mailing list <[EMAIL PROTECTED]>. To unsubscribe, E-mail to: <[EMAIL PROTECTED]> To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]> To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]> Send administrative queries to <[EMAIL PROTECTED]>
