Re: More spam than developer mail
In <[🔎] 1041017454.626.71.camel@altfrangg.fortytwo.ch> Adrian 'Dagurashibanipal' von Bidder <avbidder@fortytwo.ch> writes:
> On Fri, 2002-12-27 at 19:31, wayne wrote:
>
> > The various black lists that spamassassin uses also seems to help a
> > bunch. I don't know if the spamassassin for these lists enable them
> > or not.
>
> I've had to lower the scores on many of the blacklists, as some mails
> will trigger 3 of them or so...
Ugh.
I'm not sure why, but I spaced off mentioning that spamassassin
doesn't handle blacklists quite right and I've patched my EvalTests.pl
to work for my setup. Before I made the patch, I got a lot of false
positives from the blacklists also.
See: http://bugzilla.spamassassin.org/show_bug.cgi?id=904
I don't know if the debian listserver has a simple enough mail
environment for my patch to be useful, but here it is:
--- EvalTests.pm.~2~ 2002-10-04 07:54:16.000000000 -0500
+++ EvalTests.pm 2002-12-17 18:50:54.000000000 -0600
@@ -852,7 +852,14 @@
$self->load_resolver();
dbg("Got the following IPs: ".join(", ", @ips), "rbl", -3);
- if ($#ips > 1) {
+
+ # fix up for our secondary MX
+ # 206.222.212.218 is bald.unpythonic.net
+ if ( $#ips > 1 && $ips[0] == "206.222.212.218" ) {
+ shift @ips;
+ }
+
+ if ($#ips > 0) {
# If the set name is foo-lastN, check only the Received header that is
# N hops from the final MTA (where 0 only checks the final Received
# header).
@@ -865,7 +872,8 @@
@ips = ($ips[$#ips - $1]);
}
else {
- @ips = @ips[$#ips-$checklast .. $#ips]; # only check the originating IPs
+# @ips = @ips[$#ips-$checklast .. $#ips]; # only check the originating IPs
+ @ips = @ips[$checklast]; # only check the receiving IPs
}
}
dbg("But only inspecting the following IPs: ".join(", ", @ips), "rbl", -3);
Reply to: