https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6494
--- Comment #3 from Hanz <[email protected]> 2010-09-21 17:18:30 UTC --- To make sure things are set, I do it twice so I can see the warning. Sep 21 17:13:21.466 [26116] warn: netset: cannot include 128.6.4.3/32 as it has already been included Sep 21 17:13:21.467 [26116] warn: netset: cannot include 128.6.72.254/32 as it has already been included Sep 21 17:13:21.468 [26116] warn: netset: cannot include 128.6.72.72/32 as it has already been included Sep 21 17:13:21.468 [26116] warn: netset: cannot include 165.230.79.235/32 as it has already been included Sep 21 17:13:21.469 [26116] warn: netset: cannot include 165.230.79.236/32 as it has already been included Sep 21 17:13:21.470 [26116] warn: netset: cannot include 165.230.132.104/32 as it has already been included Sep 21 17:13:21.471 [26116] warn: netset: cannot include 128.6.168.251/32 as it has already been included Sep 21 17:13:21.472 [26116] warn: netset: cannot include 128.6.4.3/32 as it has already been included Sep 21 17:13:21.473 [26116] warn: netset: cannot include 128.6.72.254/32 as it has already been included Sep 21 17:13:21.473 [26116] warn: netset: cannot include 128.6.72.72/32 as it has already been included Sep 21 17:13:21.474 [26116] warn: netset: cannot include 165.230.79.235/32 as it has already been included Sep 21 17:13:21.475 [26116] warn: netset: cannot include 165.230.79.236/32 as it has already been included Sep 21 17:13:21.476 [26116] warn: netset: cannot include 165.230.132.104/32 as it has already been included Sep 21 17:13:21.477 [26116] warn: netset: cannot include 128.6.168.251/32 as it has already been included Sep 21 17:13:21.478 [26116] warn: netset: cannot include 192.168.0.0/16 as it has already been included Sep 21 17:13:21.479 [26116] warn: netset: cannot include 128.6.31.0/24 as it has already been included Sep 21 17:13:21.480 [26116] warn: netset: cannot include 128.6.68.0/24 as it has already been included Sep 21 17:13:21.481 [26116] warn: netset: cannot include 192.168.0.0/16 as it has already been included Sep 21 17:13:21.482 [26116] warn: netset: cannot include 128.6.31.0/24 as it has already been included Sep 21 17:13:21.483 [26116] warn: netset: cannot include 128.6.68.0/24 as it has already been included However, it seems the debug still do not see my trusted and internal network correctly. None seems to be internal. Could the 'unknown' IP in the header caused this to break? Sep 21 17:13:23.333 [26116] dbg: received-header: parsed as [ ip=unknown rdns= helo=annwn23.rutgers.edu by=unknown ident= envfrom= intl=0 id= auth= msa=0 ] Sep 21 17:13:23.335 [26116] dbg: received-header: relay unknown trusted? no internal? no msa? no Sep 21 17:13:23.337 [26116] dbg: received-header: parsed as [ ip=127.0.0.1 rdns=localhost helo=localhost by=annwn23.rutgers.edu ident= envfrom= intl=0 id=34D7CABAC9 auth= msa=0 ] Sep 21 17:13:23.337 [26116] dbg: received-header: relay 127.0.0.1 trusted? no internal? no msa? no Sep 21 17:13:23.338 [26116] dbg: received-header: parsed as [ ip=127.0.0.1 rdns= helo=annwn23.rutgers.edu by=localhost ident= envfrom= intl=0 id=Fg0AoED3KKGU auth= msa=0 ] Sep 21 17:13:23.338 [26116] dbg: received-header: relay 127.0.0.1 trusted? no internal? no msa? no Sep 21 17:13:23.339 [26116] dbg: received-header: parsed as [ ip=128.6.31.86 rdns=rulink2.rutgers.edu helo=newsuit.rutgers.edu by=annwn23.rutgers.edu ident= envfrom= intl=0 id=E042CABAC5 auth= msa=0 ] Sep 21 17:13:23.339 [26116] dbg: received-header: relay 128.6.31.86 trusted? no internal? no msa? no Sep 21 17:13:23.340 [26116] dbg: received-header: parsed as [ ip=128.6.68.237 rdns= helo=annwn32.rutgers.edu by=rulink.rutgers.edu ident= envfrom= intl=0 [email protected] auth= msa=0 ] Sep 21 17:13:23.340 [26116] dbg: received-header: relay 128.6.68.237 trusted? no internal? no msa? no Sep 21 17:13:23.341 [26116] dbg: received-header: parsed as [ ip=127.0.0.1 rdns=localhost helo=localhost by=annwn32.rutgers.edu ident= envfrom= intl=0 id=B192B3FE01B auth= msa=0 ] Sep 21 17:13:23.341 [26116] dbg: received-header: relay 127.0.0.1 trusted? no internal? no msa? no Sep 21 17:13:23.342 [26116] dbg: received-header: parsed as [ ip=127.0.0.1 rdns= helo=annwn32.rutgers.edu by=localhost ident= envfrom= intl=0 id=FUbSBwmT7zCC auth= msa=0 ] Sep 21 17:13:23.342 [26116] dbg: received-header: relay 127.0.0.1 trusted? no internal? no msa? no Sep 21 17:13:23.343 [26116] dbg: received-header: parsed as [ ip=128.6.31.85 rdns=rulink.rutgers.edu helo=newsuit.rutgers.edu by=annwn32.rutgers.edu ident= envfrom= intl=0 id=45BF83FE016 auth= msa=0 ] Sep 21 17:13:23.343 [26116] dbg: received-header: relay 128.6.31.85 trusted? no internal? no msa? no Sep 21 17:13:23.344 [26116] dbg: received-header: parsed as [ ip=188.186.137.158 rdns= helo=net137.186.188-158.dynamic.omsk.ertelecom.ru by=rulink.rutgers.edu ident= envfrom= intl=0 [email protected] auth= msa=0 ] Sep 21 17:13:23.344 [26116] dbg: received-header: relay 188.186.137.158 trusted? no internal? no msa? no Sep 21 17:13:23.345 [26116] dbg: received-header: parsed as [ ip=66.231.92.249 rdns=elvnsvj.royalbowling.com helo=2xmc0a.royalbowling.com by=p.nsm.ctmail.com ident= envfrom= intl=0 id=BECF00CFF8 auth= msa=0 ] Here is what I put: #internal_networks !0/0 internal_networks 128.6.4.3 128.6.72.254 128.6.72.72 165.230.79.235 165.230.79.236 165.230.132.104 128.6.168.251 #local RU trusted_networks 128.6.4.3 128.6.72.254 128.6.72.72 165.230.79.235 165.230.79.236 165.230.132.104 128.6.168.251 #RUlink machines internal_networks 192.168/16 128.6.31/24 128.6.68/24 trusted_networks 192.168/16 128.6.31/24 128.6.68/24 -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
