3.3. Amavisd-new

Now we'll configure amavisd-new, the actual content filter. Postfix will pass email to amavisd-new which will then redirect the mail to a virus scanner and a spam scanner based on the default configuration found in the file /etc/amavisd.conf. There are several parameters that you will need to modify in this file. "$myhostname" must be the fully qualified domain name of the server and "$mydomain" should be one of the domains that the server will be processing mail for. In most cases it will be the same domain that the server is in. Here I show the lines that I have added for the server salle1.test.com.

"$myhostname" must be the fully qualified domain name of the server and "$mydomain" should be one of the domains that the server will be processing mail for. In most cases it will be the same domain that the server is in. Here I show the lines that I have added for the server salle1.test.com.

    $myhostname = 'salle1.test.com'; 
    $mydomain = 'test.com';

The $sa_tag_level_deflt, $sa_tag_level_defl, $sa_kill_level_deflt and $final_spam_destiny parameters in amavisd.conf are SpamAssassin related.

Should you want to make changes to the configuration you would edit /etc/amavisd.conf and then restart amavisd by running the command "/etc/init.d/amavisd start".

    [root@salle1 ~]# /etc/init.d/amavisd start
    [ SUCCESSFUL ] Starting amavisd
    [root@salle1 ~]# 

You can verify that the amavisd daemon is running by doing a process listing that looks for amavisd.

    [root@salle1 ~]# ps auxwww| grep amavisd
    vscan     2286  0.9 16.5  46876 41988 ?        Ss   13:13   0:00 amavisd (master)
    vscan     2289  0.0 16.5  47612 42076 ?        S    13:13   0:00 amavisd (virgin child)
    vscan     2290  0.0 16.5  47612 42076 ?        S    13:13   0:00 amavisd (virgin child)
    root      2312  0.0  0.2   1800   560 ttyp2    S+   13:15   0:00 grep amavisd
    [root@salle1 ~]#