Amavisd-new on Email Server

carlosinfl · 08-11-2008, 01:22 PM

I installed Amavisd-new on my email server running Postfix as the MTA (Debian) and followed some online instructions on amavis.conf parameters and also some main.cf settings. Now that I am done, my question is how do I know if Amavisd is working? I want to use it with ClamAV but have not configured Clam as of yet as I want to make sure all the settings I added to Amavisd are working. Is there a way to know if the settings are working?

I added the following to /etc/amavis/conf.d/50-user

Code:

$sa_tag_level_deflt  = -5;  # add spam info headers if at, or above that level
$sa_tag2_level_deflt = 4; # add 'spam detected' headers at that level
$sa_kill_level_deflt = 10000; # triggers spam evasive actions
$sa_dsn_cutoff_level = 10;   # spam level beyond which a DSN is not sent

$forward_method = 'smtp:[127.0.0.1]:10025';
$notify_method = $forward_method;

$virus_admin = 'formorer@formorer.de'; # due to D_DISCARD default

#inform recipients about a blocked mail
$warnbannedrecip = 1;
$warnvirusrecip = 1;

$final_banned_destiny     = D_PASS;

$log_level = 2;            # (defaults to 0), -d

and also added the following to main.cf

Code:

content_filter = smtp-amavis:[127.0.0.1]:10024

**In Debian there is no one amavis.conf file but I was told by a Debian/Amavis developer to make changes to 50-user since it is the last file to be read.**

As you can see, all my services are running fine:

http://img227.imageshack.us/img227/1...rverrs6.th.png

Mr. C. · 08-11-2008, 02:16 PM

Set

$DO_SYSLOG = 1; # log via syslogd (preferred)

in one of the debian amavis config files and restart amavis. You'll then have messages logged via syslog.

You can also tell if amavis is working by examining the Receved headers of an email.

carlosinfl · 08-11-2008, 02:22 PM

Thanks for the fast reply! Does it matter where I add $DO_SYSLOG = 1; or can I simply append this to the bottom of what I provided above as my amavis config file? Will Amavis still show up in the headers even if no application like Spamassassin or Clamav have been configured yet?

Mr. C. · 08-11-2008, 02:33 PM

Debian splits the amavisd.conf file into several files. There is a name allocated for user's modifications, but I don't have the name at hand. It is 50* something. Add your modifications there, since the later numbered files are included in order. Its a last-one-wins policy.

Since amavis is acting as an MTA, it will add Received headers as mail passes through, regardless of ClamAV or SA.

Mr. C. · 08-11-2008, 02:35 PM

Ok, found the Debian info:
http://www200.pair.com/mecham/spam/d...new_2.4.2.html

carlosinfl · 08-11-2008, 02:46 PM

Quote:

Originally Posted by Mr. C.

Ok, found the Debian info:
http://www200.pair.com/mecham/spam/d...new_2.4.2.html

So according to the link, I should be making all my config changes to 50-user, correct? I have not touched any of the other files shown below.

Code:

email:/# cd /etc/amavis/conf.d/
email:/etc/amavis/conf.d# ls -l
total 56
-rw-r--r-- 1 root root  1458 2007-02-24 13:30 01-debian
-rw-r--r-- 1 root root   692 2007-02-24 13:30 05-domain_id
-rw-r--r-- 1 root root   235 2007-02-24 13:30 05-node_id
-rw-r--r-- 1 root root 13907 2007-02-24 13:30 15-av_scanners
-rw-r--r-- 1 root root   554 2007-02-24 13:30 15-content_filter_mode
-rw-r--r-- 1 root root  9187 2007-02-24 13:30 20-debian_defaults
-rw-r--r-- 1 root root   573 2007-02-24 13:30 25-amavis_helpers
-rw-r--r-- 1 root root  2130 2007-02-24 13:30 30-template_localization
-rw-r--r-- 1 root root   919 2008-08-06 14:13 50-user

Mr. C. · 08-11-2008, 02:47 PM

That's correct.

By the way, there's usually excellent help on the amavis list. I highly recommend signing up.

carlosinfl · 08-11-2008, 02:49 PM

OK - Being use to how CentOS / RHEL have one basic /etc/amavis.conf file...I was really confused why Debian had multiple config files and was not sure if this was the way to go but if I can make all my changes in 50-user and not worry about the rest, I should be fine. I will append what you suggested to the end of 50-user and restart amavis to start logs and check received headers.