On 03/11/02 at 16:59, Stefan Jeglinski wrote:
> >>That is apparently not the case here (since karabalta.kg. resolves
> >>to 192.168.0.1 not 195.38.186.2), so it's unclear to me why SIMS
> >>would mark it as verified. That would seem to be erroneous.
>
> And more interestingly, how exactly did SIMS figure that 195.38.186.2
> is related to karabalta.kg? I've heard here that SIMS doesn't use any
> kind of special lookup method. But without doing a more extravagant
> search, how does SIMS proceed when karabalta.kg returns a private
> address and 195.38.186.2 has no PTR record?
I've already trashed the original message of this thread, but IIRC it quoted a
'Received:' header line with something like 'karabalta.kg ([195.38.186.2]
verified)'. That would indicate that SIMS received a connection from
195.38.186.2 and the HELO/EHLO in the subsequent SMTP conversation had an
argument of 'karabalta.kg' (i.e., the connecting host claimed to be
karabalta.kg). A query for karabalta.kg. returns an A record pointing to
192.168.0.1, so if I understand SIMS' procedure correctly, it should not have
considered the HELO/EHLO to have been verified.
--
Christopher Bort | [EMAIL PROTECTED]
Webmaster, Global Homes | [EMAIL PROTECTED]
<http://www.globalhomes.com/> | PGP public key available on request
#############################################################
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]>
