Sahil Tandon wrote:
Skip <[EMAIL PROTECTED]> wrote:
But I want to stop the test from even being done at all. I guess I should
have included more of the previous post. Sorry :(
Please do not top-post (google if you are unfamiliar with the term). And as
already advised, just set score to 0 to disable individual DNSBLs. To
disable all checks, set skip_rbl_checks to 1. This functionality is noted in
the documentation:
http://wiki.apache.org/spamassassin/DnsBlocklists
Sorry about that :) I am actually quite familiar with bottom posting
and wish it were used in the workplace, but I doubt we'll ever see
that. And thanks for the answer to my question.
Anyway, please bear with me as I do have a few more questions. In this
thread before, some people thought I should look at a possible DNS
problem, or perhaps my system is exceeding the daily threshold for
spamhaus. All they say at the spamhaus FAQ is that if you exceed the
threshold "your access to Spamhaus's public DNSBL servers is very likely
to be cut off without warning". We already established that since I am
on a shared hosting system, it is entirely possible that we (as a
system, but not as a domain) may be exceeding the threshold, but I don't
know how to go about checking at spamhaus to see if that is indeed the
case. Anyway, I'd like to show one more snippet from my log, to see
what you guys think.
>grep spamhaus Procmail/pmlog-skip|grep 8874
[8874] dbg: dns: checking RBL zen.spamhaus.org., set zen-lastexternal
[8874] dbg: dns: launching DNS A query for 95.2.18.64.zen.spamhaus.org.
in background
[8874] dbg: async: starting: DNSBL-A, dns:A:95.2.18.64.zen.spamhaus.org.
(timeout 15.0s, min 3.0s)
[8874] dbg: dns: checking RBL zen.spamhaus.org., set zen-lastexternal
[8874] dbg: dns: checking RBL zen.spamhaus.org., set zen
[8874] dbg: dns: launching DNS A query for
222.84.98.85.zen.spamhaus.org. in background
[8874] dbg: async: starting: DNSBL-A,
dns:A:222.84.98.85.zen.spamhaus.org. (timeout 15.0s, min 3.0s)
[8874] dbg: async: starting: URI-DNSBL,
DNSBL:sbl.spamhaus.org.:100.142.44.89 (timeout 15.0s, min 3.0s)
[8874] dbg: async: completed in 5.040 s: URI-DNSBL,
DNSBL:sbl.spamhaus.org.:100.142.44.89
[8874] dbg: async: aborting after 7.527 s, deadline shrunk: DNSBL-A,
dns:A:222.84.98.85.zen.spamhaus.org.
[8874] dbg: async: aborting after 7.534 s, deadline shrunk: DNSBL-A,
dns:A:95.2.18.64.zen.spamhaus.org.
[8874] dbg: async: timing: 5.040 . DNSBL:sbl.spamhaus.org.:100.142.44.89
[8874] dbg: async: timing: 7.527 X dns:A:222.84.98.85.zen.spamhaus.org.
[8874] dbg: async: timing: 7.534 X dns:A:95.2.18.64.zen.spamhaus.org.
Here you can see that three calls to spamhaus were going to be made for
this message. The first call made it and was completed in 5.040 s. The
other two were aborted after 7.5 s with that mysterious "deadline
shrunk" message. Since I got a successful return on the first test, I
don't think it could be a DNS problem on my end, but please correct me
if I am mistaken and overlooking something. By the way, I googled
"deadline shrunk". Twenty five hits total with the majority of them
pointing to this thread and the spamassassin source code. No real
help. Anyway, back to my log here. The one completed call is
interesting because if you go to the spamhaus website, that IP address
actually hits positive
http://www.spamhaus.org/query/bl?ip=89.44.142.100
*89.44.142.100 is listed in the SBL*, in the following records:
* SBL65873 <http://www.spamhaus.org/sbl/sbl.lasso?query=SBL65873>
* SBL65994 <http://www.spamhaus.org/sbl/sbl.lasso?query=SBL65994>
But you'll notice that I don't get the hit message here in my log. In
fact, I have never gotten a hit from spamhaus on ANY message.
So, my question for the community is, what could I possibly have
misconfigured here? Or is it most certainly that we (me and all
customers using the same hosting company as me) are banned from spamhaus
lookups do to our volume and I should look for resolution that way?
Anyone know who I would email at spamhaus to find out? What information
would I need to give them?
Btw, I am using ver 3.2.4.
Sorry for being such a pest, but before I go knocking on spamhaus'
and/or bluehost's (my hosting company) door, I'd like to be as sure as
possible about these things, and possibly even point them to this thread.
Skip
--
Get my PGP Public key here:
http://pelorus.org/[EMAIL PROTECTED]
