Re: DSN:Re: [Declude.JunkMail] Spamdomains lookup timeout

[R. Scott Perry]

Here is a comment on the web site www.dnsreport.com
When you check a site on this web site the first revdns check can fail and
the explanation is as follow
--
Reverse DNS entries for MX records
 This may be a false positive due to the nasty BIND bug (client side) that
causes reverse DNS entries to fail the first time (if you ever see long
delays in reverse DNS lookups, that's because of this bug). You can
double-check using the 'Reverse DNS Lookup' tool at the DNSstuff site.

I have too many timeout when cheking the first time REVDNS for non-existing
revdns .
FWIW, Declude JunkMail has a technique built into it so that if BIND v8 or 
earlier is used locally (the ones that have the reverse DNS bug), Declude 
JunkMail will still receive the reverse DNS entry.  So the only time that a 
timeout should occur in reverse DNS entry lookups in Declude JunkMail is if 
all the authoritative nameservers are unreachable, which should not be common.

   -Scott
---
Declude JunkMail: The advanced anti-spam solution for IMail mailservers.
Declude Virus: Catches known viruses and is the leader in mailserver 
vulnerability detection.
Find out what you have been missing: Ask for a free 30-day evaluation.

---
[This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]
---
This E-mail came from the Declude.JunkMail mailing list.  To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail".  The archives can be found
at http://www.mail-archive.com.

DSN:Re: [Declude.JunkMail] Spamdomains lookup timeout

[Rifat Levis]

Here is a comment on the web site www.dnsreport.com
When you check a site on this web site the first revdns check can fail and
the explanation is as follow

--
Reverse DNS entries for MX records
 This may be a false positive due to the nasty BIND bug (client side) that
causes reverse DNS entries to fail the first time (if you ever see long
delays in reverse DNS lookups, that's because of this bug). You can
double-check using the 'Reverse DNS Lookup' tool at the DNSstuff site.

I have too many timeout when cheking the first time REVDNS for non-existing
revdns .

Rifat Levis





- Original Message - 
From: "Markus Gufler" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, June 15, 2003 4:21 AM
Subject: [Declude.JunkMail] Spamdomains lookup timeout


Hi all,

I'm not sure about this, but I've seen some spam messages coming from
domains contained in our sd-file. (hotmail.com) However the messages
hasn't failed the SPAMDOMAINS test.

For example from the Sender-IP: 218.25.255.18

Can it be, because it's not possible to finish the REVDNS-query?

http://www.dnsstuff.com/tools/ptr.ch?ip=218.25.255.18


Question?
If it's so, that a timeout in a REVDNS-query doesn't trigger the test,
can we change this, so that a timeout triggers the test?
What if a query for a legit sender-IP times out?
Why a REVDNS-query can time out? Isn't so, that any reachable IP is
assigned to someone?

Markus


---
[This E-mail was scanned for viruses by Declude Virus
(http://www.declude.com)]

---
This E-mail came from the Declude.JunkMail mailing list.  To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail".  The archives can be found
at http://www.mail-archive.com.

---
[This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]

---
This E-mail came from the Declude.JunkMail mailing list.  To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail".  The archives can be found
at http://www.mail-archive.com.