Thanks - this seems to have done the trick - I only had one of these set (trusted_networks at the last try). There's a subtle difference between the two I'll obviously have to investigate.
mouss-4 wrote: > > fjl_london a écrit : >> Spam arrives at server A. Server A is whitelisted. Server A sends it >> (with a >> .forward) to server B, which is running Spamassassin. Server B looks up >> server A in the whitelist and knocks 4 of the spam score. >> >> What's the cure? There's an implication that adding the IP of server A to >> 'internal_networks' will cause it to be ignored, but it doesn't seem to >> be >> working in this case. >> > > I use this > > #liszt.debian.org [82.195.75.100] > trusted_networks 82.195.75.100 > internal_networks 82.195.75.100 > > (among other entries) and it works. > >> I checked the source code and there's something in >> _check_whitelist_rcvd() >> that appears intended to get around this problem (WLBLEval.pm). This >> suggests that either it's broken, or I'm not configuring it correctly >> (i.e. >> setting the wrong option entirely?) > > P.S. Apologies if this message looks a mess - first time using Nabble and I don't know what it'll do -- View this message in context: http://www.nabble.com/RCVD_IN_DNSWL_MED-test---I%27m-on-the-whitelist-so-spam-gets-through-tp23231790p23232097.html Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
