Re: spamassassin -- cron.daily warning

[Camaleón <noelamac@gmail.com>]

On Sat, 02 Jul 2011 16:06:08 +1000, Andrew McGlashan wrote:

> On a server that still has lenny, I was getting a message (started on
> 27th June) as follows each day (from /etc/cron.daily/spamassassin
> script:
> 
> Jul  2 15:16:26.778 [17797] warn: netset: cannot include 127.0.0.0/8 as
> it has already been included
> 
> 
> 
> The /etc/spamassassin/local.cf had 127/8 in trusted networks, I've now
> removed that as it seems to be included by default now -- or at least it
> stops the warning at least.

Yes, or at least so it say the upstream docs:

http://spamassassin.apache.org/full/3.3.x/doc/Mail_SpamAssassin_Conf.html#network_test_options

"(.. )Note: 127/8 and ::1 are always included in trusted_networks, 
regardless of your config."

> I broke the following line into two lines and commented the 127/8 line.
> 
> #trusted_networks 192.168/16 127/8           # all in 192.168.*.* and 127.*.*.*
> 
> 
> trusted_networks 192.168/16
> #trusted_networks 127/8

Which seems fine as the doc continues:

"(...) This operates additively, so a trusted_networks line after another 
one will append new entries to the list of trusted networks."

(...)

> The spamassassin package hasn't changed for a long time, so the changes
> might be due to a data file that has updated for the package.  Perhaps I
> should re-enable 127/8 in trusted networks and wait for the data to fix
> itself .... advice?

I can't see the problem now that you made the change. Is there still 
anything wrong with your current setup? :-?

Greetings,

-- 
Camaleón