View source for Amavis-new and ClamAV

= ClamAV =
First get this installed
<pre>
apt-get install clamav clamav-testfiles
</pre>
Update using:
<pre>
freshclam
</pre>
test using:
<pre>
clamscan --infected --recursive /usr/share/clamav-testfiles/
</pre>
To get it to go:
<pre>
clamscan --infected --remove --recursive /usr/share/clamav-testfiles/
</pre>

From [http://www.server-world.info/en/note?os=Debian_6.0&p=mail&f=6]

= Amavis =
Then we install Amavis, which sends mail from postfix to clamav and spamassassin and then into procmail after scanning

<pre> 
aptitude -y install clamav-daemon amavisd-new spamassassin altermime ripole arj cabextract cpio lhasa lzop nomarch p7zip rpm unrar unrar-free zoo
</pre>

Also install the suggested unzip packages

vi /etc/default/spamassassin 

line 8: turn '1' if you use spam filter

ENABLED=1

vi /etc/amavis/conf.d/15-content_filter_mode 

line 13: uncomment
<pre>

@bypass_virus_checks_maps = (
  \%bypass_virus_checks, \@bypass_virus_checks_acl, \$bypass_virus_checks_re);
</pre>


line 24: uncomment ( if you use spam filter )
<pre>@bypass_spam_checks_maps = (
  \%bypass_spam_checks, \@bypass_spam_checks_acl, \$bypass_spam_checks_re);
</pre>

vi /etc/postfix/main.cf add at the last line

content_filter=smtp-amavis:[127.0.0.1]:10024
vi /etc/postfix/master.cf 


add at the last line

<pre>
smtp-amavis unix -       -       n      -     2  smtp
      -o smtp_data_done_timeout=1200
      -o smtp_send_xforward_command=yes
      -o disable_dns_lookups=yes
127.0.0.1:10025 inet n     -     n     -     -  smtpd
     -o content_filter=
     -o smtpd_delay_reject=no
     -o smtpd_client_restrictions=permit_mynetworks,reject
     -o smtpd_helo_restrictions=
     -o smtpd_sender_restrictions=
     -o smtpd_recipient_restrictions=permit_mynetworks,reject
     -o smtpd_data_restrictions=reject_unauth_pipelining
     -o smtpd_end_of_data_restrictions=
     -o smtpd_restriction_classes=
     -o mynetworks=127.0.0.0/8
     -o smtpd_error_sleep_time=0
     -o smtpd_soft_error_limit=1001
     -o smtpd_hard_error_limit=1000
     -o smtpd_client_connection_count_limit=0
     -o smtpd_client_connection_rate_limit=0
     -o receive_override_options=no_header_body_checks,no_unknown_recipient_checks,no_milters
     -o local_header_rewrite_clients=
     -o smtpd_milters=
     -o local_recipient_maps=
     -o relay_recipient_maps=
</pre>

If you don't have it yet, then:

touch /etc/mailname 


<pre> 
chmod -R 775 /var/lib/amavis/tmp usermod -G amavis clamav </pre>


<pre>
/etc/init.d/clamav-daemon restart 
/etc/init.d/spamassassin start 
/etc/init.d/postfix restart 
/etc/init.d/amavis restart
</pre>

More info in /usr/share/doc/amavisd-new

== Spamassassin settings ==

Amavis overrides some spamassassing settings, such as:
<pre>
$sa_local_tests_only = 0;
$sa_mail_body_size_limit = 400*1024;
$sa_tag_level_deflt  = 2.0;
</pre>
and more

== Tuning ==
You can set a higher number of servers in /etc/amavis/conf.d/50-user '''not in''' /etc/amavis/amavisd.conf
<pre>
$max_servers = 10;
</pre>

This number has to be the same as the maxproc column in /etc/postfix/master.cf, ie:

<pre>
smtp-amavis unix -       -       n      -     10 smtp
</pre>

where the 10 = $max_servers. The number in master.cf should definitely not be higher than $max_servers.

You can see if this is working by doing
<pre>
ps ax | grep amavis
</pre>

You will see the amavis processes as well as the postfix processes sending info to the amavis children:
<pre>
26805 ?        Ss     0:01 amavisd (master)
26844 ?        S      0:28 amavisd (ch2-26844-02-16)
26990 ?        S      0:00 smtp -n smtp-amavis -t unix -u -o smtp_data_done_timeout=1200 -o smtp_send_xforward_command=yes -o disable_dns_lookups=yes
</pre>

There should '''not''' be more smtp processes running than amavisd children!

Also in amavisd-nanny you should see as many processes as you have specified:
<pre>
PID 26844: 26844-02-16   0:00:02 ===
PID 26845: 26845-01-20   0:00:02 ==
PID 26846: 26846-02-17   0:00:04 =====
PID 26847: 26847-02-17   0:00:12 m========:==
PID 26848: 26848-01-16   0:00:01 =
PID 26849: 26849-01-16   0:00:02 ===
PID 26850: 26850-01-15   0:00:06 ======
PID 26851: 26851-01-16   0:00:03 ====
PID 26852: 26852-02-16   0:00:04 ====
PID 26853: 26853-02-17   0:00:01 ==
</pre>

== Testing ==
Check if amavis is up:
<pre>
netstat -nap | grep 10024
</pre>

See what amavisd-new is doing:
<pre>
amavisd-nanny
</pre>
and
<pre>
amavisd-agent
</pre>

Now your messages should have an X-header line saying it was scanned by Amavis