what is "netset: cannot include 127.0.0.1/32 as it has already been included"

[Phibee Network Operation Center <no...@phibee.net>]

Hi

my logs of spamassassin put:

netset: cannot include 127.0.0.1/32 as it has already been included

anyone know what is this ?

thanks
jerome

Re: what is "netset: cannot include 127.0.0.1/32 as it has already been included"

[Mark Martinec <Ma...@ijs.si>]

On Saturday 25 April 2009 07:44:01 Matt Kettler wrote:
> Phibee Network Operation Center wrote:
> > my logs of spamassassin put:
> > netset: cannot include 127.0.0.1/32 as it has already been included
> > anyone know what is this ?
>
> I'd guess you tried to declare 127.0.0.1 in either your
> trusted_networks, or internal_networks. However, this is a hard-coded
> assumption, and doesn't need adding.

Indeed. I believe the change was made with 3.2.0, as a result of:

  https://issues.apache.org/SpamAssassin/show_bug.cgi?id=5259

  From a compatibility perspective this was a bit unfortunate,
as previously one HAD TO include the 127.0.0.0/8 in his
internal&trusted lists, but after the change one MUST NOT do so,
as otherwise you receive the above configuration error.
But that is history now, time to adapt.

  Mark

Re: what is "netset: cannot include 127.0.0.1/32 as it has already been included"

[Matt Kettler <mk...@verizon.net>]

Phibee Network Operation Center wrote:
> Hi
>
> my logs of spamassassin put:
>
> netset: cannot include 127.0.0.1/32 as it has already been included
>
> anyone know what is this ? 

I'd guess you tried to declare 127.0.0.1 in either your
trusted_networks, or internal_networks. However, this is a hard-coded
assumption, and doesn't need adding.

(If you can't trust yourself, who can you trust? :-)