On Wednesday, December 7, 2005, 8:31:06 AM, Brian Leyton wrote: > Jeff Chan wrote: >> >> OK I can't remember if that one has the bug fix or not. 3.1 >> definitely does. >> >> What was the specific FP domain?
> Here's the scoring section of the SA report: > Content analysis details: (5.5 points, 5.0 required) > pts rule name description > ---- ---------------------- > -------------------------------------------------- > -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% > [score: 0.0000] > 2.0 URIBL_PH_SURBL Contains an URL listed in the PH SURBL blocklist > [URIs: americanbroadcastdx.com] > 0.4 URIBL_AB_SURBL Contains an URL listed in the AB SURBL blocklist > [URIs: americanbroadcastdx.com] > 1.5 URIBL_WS_SURBL Contains an URL listed in the WS SURBL blocklist > [URIs: americanbroadcastdx.com] > 4.3 URIBL_SC_SURBL Contains an URL listed in the SC SURBL blocklist > [URIs: americanbroadcastdx.com] > Brian Leyton > IT Manager > Commercial Petroleum Equipment Thanks. americanbroadcastdx.com was never on any SURBLs, so it's probably the bug. Please consider upgrading to 3.1 or possibly even 3.0.5 as this may fix the bug: http://issues.apache.org/SpamAssassin/show_bug.cgi?id=3997 The developers will know for sure about which versions the patch is in. Or you could perhaps apply the patch manually to 3.0.4. They would know that too. It may be worth asking if you have any unusual DNS arrangement such as proxying firewalls, etc. Jeff C. -- Jeff Chan mailto:[EMAIL PROTECTED] http://www.surbl.org/
