Matt Kettler writes: >At 12:42 AM 10/3/03 -0400, Christopher M. Iarocci wrote: >>Hi, I'm using SpamAssassin 2.60 being called through Amavisd-new. Dynablock >>(along with a few others) is scoring on lots of messages that it shouldn't >>because the first hop is a dial up. I put the following line in my >>/etc/mail/spamassassin/local.cf > >In 2.60 SA should ignore the first hop by default when doing dynablock. > >The standard RCVD_IN_DYNABLOCK rule already calls the eval with the >"dynablock-notfirsthop" parameter. > >If it's not working, then it's a bug in the spamassassin code itself, and >cannot be fixed by configuration options. > >I'd check the message very carefully.. are all the IPs beyond the first not >listed? Are you sure the 2nd, 3rd and 4th received lines contain IPs that >aren't listed?
If there's only *1* IP address outside your own trusted networks, SpamAssassin will check that, even for "notfirsthop" tests. It's only if there's 2 or more relays that "notfirsthop" applies. Sounds like these may be messages from your own dialup pool -- I'd suggest adding those IP ranges to "trusted_networks" in your conf file, and that'll mean they won't be checked against dynablock. --j. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
