Installing Maia Mailguard On Debian Squeeze (Virtual Users/Domains With Postfix/MySQL) - Page 3

10 Configuring Amavisd-new

Maia Mailguard comes with its own amavisd-new configuration and amavisd binary, so we must replace our existing amavisd-new with it.

First stop your current amavisd processes:

/etc/init.d/amavis stop

First we need to download amavisd-maia to /usr/src... Please remember about updating Maia's revision number (1578).

cd /usr/src/
svn -r 1578 checkout https://www.maiamailguard.com/svn/trunk/

We copy amavisd-maia to /usr/local/sbin/amavisd-new...

cd /usr/src/trunk/
cp amavisd-maia /usr/local/sbin/amavisd-new
chown root /usr/local/sbin/amavisd-new
chmod 755 /usr/local/sbin/amavisd-new

... and adjust our /etc/init.d/amavis init script as follows:

nano /etc/init.d/amavis

[...]
#DAEMON=/usr/sbin/amavisd-new
DAEMON=/usr/local/sbin/amavisd-new
[...]
#START="--start --quiet --pidfile /var/run/amavis/${NAME}.pid --name ${DAEMONNAME} --startas ${DAEMON}"
#STOP="--stop --quiet --pidfile /var/run/amavis/${NAME}.pid --name ${DAEMONNAME}"
START="--start --quiet --pidfile /var/lib/amavis/${NAME}.pid --name ${DAEMONNAME} --startas ${DAEMON}"
STOP="--stop --quiet --pidfile /var/lib/amavis/${NAME}.pid --name ${DAEMONNAME}"
[...]

Then we copy /usr/src/trunk/amavisd.conf.dist to /etc/amavisd.conf...

cp /usr/src/trunk/amavisd.conf.dist /etc/amavisd.conf

... and edit that file:

nano /etc/amavisd.conf

[...]
$mydomain = 'localhost';
#$mydomain = 'yourdomain.tld'; # a convenient default for other settings

$MYHOME   = '/var/lib/amavis';
#$MYHOME   = '/var/amavisd';   # a convenient default for other settings
[...]
$log_level = 5;
#$log_level = 0;              # verbosity 0..5
[...]
# Database connection string
@lookup_sql_dsn = ( ['DBI:mysql:maia:localhost', 'amavis', 'amavismysqlpasswd'] );
[...]
$myhostname = 'mail.example.com';
#$myhostname = 'host.domain.tld';  # must be a fully-qualified domain name!
[...]
$final_virus_destiny      = D_DISCARD;
$final_banned_destiny     = D_DISCARD;
$final_spam_destiny       = D_DISCARD;
$final_bad_header_destiny = D_DISCARD;
[...]
# See https://secure.renaissoft.com/maia/wiki/VirusScannerConfig
# for more virus scanner definitions.
@av_scanners = (

### http://www.clamav.net/
['ClamAV-clamd',
   \&ask_daemon, ["CONTSCAN {}\n", "/var/run/clamav/clamd.ctl"],
   qr/\bOK$/m, qr/\bFOUND$/m,
   qr/^.*?: (?!Infected Archive)(.*) FOUND$/m ],
# NOTE: run clamd under the same user as amavisd;  match the socket
# name (LocalSocket) in clamav.conf to the socket name in this entry
# When running chrooted one may prefer: ["CONTSCAN {}\n","$MYHOME/clamd"],

);
[...]

Make sure you fill in the correct password for the amavis MySQL user in the @lookup_sql_dsn line. In the ClamAV-clamd stanza, you must change the socket - the correct socket on Debian Squeeze is /var/run/clamav/clamd.ctl.

Start amavisd afterwards:

/etc/init.d/amavis start

You should now check /var/lib/amavis/amavis.log for errors - please make sure that the database connection is working.

11 Log Into Maia Mailguard

You can now access Maia Mailguard under http://www.example.com/maia/ - this is where you and your users can log in with an existing email address/password:

If you use Maia Mailguard for the first time, you should register yourself as the Maia super-administrator. Go to http://www.example.com/maia/login.php?super=register and log in with your existing email address and password - this will automatically make you the super-administrator of the Maia system:

As super-administrator, you have all the privileges of administrators (e.g. "impersonating" other users, and deleting users), but also the ability to grant administrator privileges to others (and revoke them, if desired).

Should the super-administrator ever wish to give up his privileges, he has to do so by logging in at http://www.example.com/maia/login.php?super=unregister (after a super-administrator "unregisters" himself, the system effectively has no super-administrator, so the next user to login with the ?super=register argument will become the super-administrator).

After your login, you should read the notes on the welcome page:

At the bottom of the welcome page, you can set your protection level (this is only for the account that you used to log in - each user can set his protection level individually). High is recommended:

These are the available protection levels:

Off:

Low:

Medium:

High: