1

Topic: amavis and local networks

Hi!
All messages from an other mailserver in the same network [172.16.0.100] not tagged as Spam. (iRedMail = irm05 172.16.0.101)
Doesn´t amavis scan mails comming from the same internal network like the log below? 

Aug 25 23:43:38 irm05 amavis[16050]: (16050-03) Passed CLEAN, MYNETS LOCAL [172.16.0.100] [189.78.236.8] <baccivorous@degramca.com> -> <postmaster@example.com>, Message-ID: <4A9454D5.8030907@degramca.com>, mail_id: vxLbOImcls7x, Hits: -10, size: 17424, queued_as: C375AB58, 337 ms

thx

2

Re: amavis and local networks

Amavisd considers servers listed in '@mynetworks' are MYNETS LOCAL, and 172.16.0.0/12 is listed in it be default.

You can remove '172.16.0.0/24' from '@mynetworks' in /etc/amavisd.conf (RHEL/CentOS) or add below lines in /etc/amavis/conf.d/50-user (Debian/Ubuntu):

@mynetworks = qw( 127.0.0.0/8 [::1] [FE80::]/10 [FEC0::]/10
                  10.0.0.0/8 172.16.0.0/12 192.168.0.0/16 );

Remove '172.16.0.0/12' to fit your need.

3 (edited by mbsouth 2009-08-26 20:02:56)

Re: amavis and local networks

It works! Thanks for your help.

4

Re: amavis and local networks

It looks like Spamassassin didn´t know something about Amavis´s "@mynetwork" settings.
I added

trusted_networks 127.0.0.0/8

to /etc/spamassassin/local.cf.
Works great, thanks!

5

Re: amavis and local networks

It doesn´t!
Got a Cron message after changing Spamassassins local.cf:

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


Got this message after adding "@mynetworks" to /etc/amavis/conf.d/50-user:

netset: cannot include 127.0.0.0/8 as it has already been included

Spamscore on my server is nearly NULL.
So I had decreased "score ALL_TRUSTED" from  -10.000 to -1.000. I hope it helps me a little bit.