https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6908
--- Comment #6 from David Hill <[email protected]> --- Hello again, If I remove the "reverse", it works ... but I don't know what else I broke! Feb 15 22:08:36.573 [4173] dbg: auto-whitelist: tie-ing to DB file of type DB_File R/W in /var/spool/MailScanner/spamassassin/auto-whitelist Feb 15 22:08:36.574 [4173] dbg: auto-whitelist: IP masking 197.148.38.241 -> 197.148 Feb 15 22:08:36.574 [4173] dbg: auto-whitelist: db-based [email protected]|ip=197.148 scores 0/0 Feb 15 22:08:36.574 [4173] dbg: auto-whitelist: db-based [email protected]|ip=none scores 0/0 Feb 15 22:08:36.574 [4173] dbg: auto-whitelist: AWL active, pre-score: 61.453, autolearn score: 61.453, mean: undef, IP: 197.148.38.241, address: [email protected] (not signed) Feb 15 22:08:36.574 [4173] dbg: auto-whitelist: add_score: new count: 1, new totscore: 61.453 Feb 15 22:08:36.574 [4173] dbg: auto-whitelist: DB addr list: untie-ing and unlocking Feb 15 22:08:36.575 [4173] dbg: auto-whitelist: DB addr list: file locked, breaking lock Dave (In reply to comment #5) > Hello, > > I'm not quite sure but if they are in the order they appear in the > headers, the reverse could be the culprit... is it? > > > Dave > > <<<SNIP>>> > foreach my $rly (reverse (@{$pms->{relays_trusted}}, > @{$pms->{relays_untrusted}})) > { > next if ($rly->{ip_private}); > if ($rly->{ip}) { > $origip = $rly->{ip}; last; > } > } > <<</SNIP>>> > > > (In reply to comment #4) > > He emailed me the debug output, don't think there's anything more private > > here than has already been provided: > > > > Feb 15 21:26:07.290 [22499] dbg: config: internal_networks not configured, > > using trusted_networks configuration for > > internal_networks; if you really want internal_networks to only contain the > > required 127/8 add 'internal_networks !0/0' to your > > configuration > > > > Feb 15 21:26:07.291 [22499] dbg: received-header: parsed as [ > > ip=197.148.38.241 rdns= helo=cust241-38.148.197.netcabo.co.ao > > by=mail01.ubisoft.com ident= envfrom= intl=0 id=53E2A6662F auth= msa=0 ] > > Feb 15 21:26:07.292 [22499] dbg: received-header: relay 197.148.38.241 > > trusted? no internal? no msa? no > > > > Feb 15 21:26:07.299 [22499] dbg: received-header: parsed as [ > > ip=199.101.160.34 rdns= helo=maila-cb.linkedin.com > > by=mailstore1.secureserver.net ident= envfrom= intl=0 id= auth= msa=0 ] > > Feb 15 21:26:07.299 [22499] dbg: received-header: relay 199.101.160.34 > > trusted? no internal? no msa? no > > > > Feb 15 21:26:07.300 [22499] dbg: metadata: X-Spam-Relays-Trusted: > > Feb 15 21:26:07.300 [22499] dbg: metadata: X-Spam-Relays-Untrusted: [ > > ip=197.148.38.241 rdns= helo=cust241-38.148.197.netcabo.co.ao > > by=mail01.ubisoft.com ident= envfrom= intl=0 id=53E2A6662F auth= msa=0 ] [ > > ip=199.101.160.34 rdns= helo=maila-cb.linkedin.com > > by=mailstore1.secureserver.net ident= envfrom= intl=0 id= auth= msa=0 ] > > > > Feb 15 21:26:07.300 [22499] dbg: metadata: X-Spam-Relays-Internal: > > Feb 15 21:26:07.300 [22499] dbg: metadata: X-Spam-Relays-External: [ > > ip=197.148.38.241 rdns= helo=cust241-38.148.197.netcabo.co.ao > > by=mail01.ubisoft.com ident= envfrom= intl=0 id=53E2A6662F auth= msa=0 ] [ > > ip=199.101.160.34 rdns= helo=maila-cb.linkedin.com > > by=mailstore1.secureserver.net ident= envfrom= intl=0 id= auth= msa=0 ] > > > > > > So 197.148.38.241, which should be used by AWL, shows up just fine as the > > last untrusted and last external relay. It's also the IP used for checking > > blacklists. Looks weird to me. -- You are receiving this mail because: You are the assignee for the bug.
