The problem here is that your DNS server is reporting that it is failing. However, in most cases it seems that these warnings are caused by DNS servers that pass through a "server failure" error from a remote DNS server (this is an example of how RFCs can be flawed -- they say that this message is supposed to be reported only when there is a failure on the DNS server returning the response, but it doesn't say how DNS servers should respond if they receive this error from another mailserver).Scott, I found the following entries in my JunkMail log file. First, I have many entries like the following and was wondering why a DNS lookup was done on an IP address that is whitelisted:========== 01/21/2003 07:20:27 Q65310f86012666ad WARNING: DNS server 206.114.137.8 returned a SERVER FAILURE error for MX or A for local.com.
The whitelisting in many cases will occur after the E-mail is scanned, which is why the DNS lookup occurred for this E-mail.
Second, I also have entries in the log file like this: ========== 01/21/2003 08:06:21 Q6ffa06980092867d L0 Message OK 01/21/2003 08:06:21 Q6ffa06980092867d L0 Message OK
...
The multiple entries will occur if there are multiple recipients. There is a bug with the latest interim release that will cause the "L0" to always appear -- it should increment for each log file entry ("L1" meaning the first recipient for an incoming E-mail, "L2" meaning the second recipient, and so forth). This behavior will be fixed for the next release.========== and I was wondering why the same entry is getting repeated multiple time. I am running Declude v1.66i7 with my loglevel set to low.
-Scott
---
[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.
