Appending by: www.soportelinux.com
MailWatch for MailScanner is developed on RedHat 9 & RHEL 3.0, so these docs will reflect this and I will make note on anything that will be required to run on other distros or operating systems.
For a Debian install try this (beta)
You must have a working MailScanner set-up and running copies of MySQL, Apache, and PHP (with MySQL and GD support). You must also have the Perl DBD-MySQL package installed for the Perl portions of MailScanner to utilize the MySQL database.
If you need help please use the mailing-list firstname.lastname@example.org or the forums on Sourceforge. NOTE: You will likely get faster support from the mailing list than from the forum.
PHP should have the following set in php.ini (possibly others too….)
Special consideration for RHEL 4.x / Centos 4.x users. The PHP GD support has been moved into a different module. You need to ensure that PHP-GD is installed. On Centos 4.1 the command is:
yum install php-gd
All commands below should be run as root.
# mysql -p < create.sql
NOTE: you will need to modify the above as necessary for your system if you have a root password for your MySQL database (recommended!) - RH9 is blank by default.
# mysql mysql> GRANT ALL ON mailscanner.* TO mailwatch@localhost IDENTIFIED BY '<password>';
Edit MailWatch.pm and change the $db_user and $db_pass values accordingly and move MailWatch.pm to /usr/lib/MailScanner/MailScanner/CustomFunctions (this could be /opt/MailScanner/lib/MailScanner/MailScanner/CustomFunctions on non-RPM systems).
# mysql mailscanner -u mailwatch -p Enter password: ****** mysql> INSERT INTO users VALUES ('<username>',md5('<password>'),'<name>','A','0','0','0','0','0');
*** remove the < and > around the username/password/name (It seems silly to have to say it, but some don't get it).
From within the unpacked mailwatch directory move the directory called 'mailscanner' to the web server's root.
# mv mailscanner /var/www/html/
Check the permissions of /var/www/html/mailscanner/images and /var/www/html/images/cache - they should be ug+rwx and owned by root and in the same group as the web server user (apache on RedHat 9).
# chown root:apache images # chmod ug+rwx images # chown root:apache images/cache # chmod ug+rwx images/cache
In the newly installed/moved html/mailscanner directory, create conf.php by copying conf.php.example and edit the values to suit, you will need to set DB_USER and DB_PASS to the MySQL user and password that you created earlier.
Note that MailWatch 1.0 can use the quarantine more effectively when used with MailScanner version 4.43 or later as Julian added some code for me to keep track of messages quarantined by using a flag in the maillog table. This means that MailWatch 1.0 is *much* faster when you have a large quarantine directory. The new quarantine report requires the use of the new functionality - so you must upgrade if you want to run this.
The new quarantine flag is not used by default - if you have MailScanner verions 4.43 or later, you can activate the new functionality by setting QUARANTINE_USE_FLAG to true in conf.php - if you do this, you must disable the clean.quarantine script supplied by MailScanner and use the new quarantine_maint.php script in the tools directory instead.
To disable the clean.quarantine script edit /pathtomailmailscanner/bin/cron/clean.quarantine.cron and change
$disabled = 0;
$disabled = 1;
To clean the quarantine, set 'QUARANTINE_DAYS_TO_KEEP' in conf.php and run './quarantine_maint –clean'.
This should then be run daily from cron: you can do this by running
echo "/pathtomailwatch/tools/quarantine_maint.php --clean" > /etc/cron.daily/mailwatch_quarantine_maint.sh chmod +x /etc/cron.daily/mailwatch_quarantine_maint.sh
To keep the MySQL database clean from old records, you should run tools/db_clean.php daily (as a cron job). Be sure the first line is
# service MailScanner stop
Next edit /etc/MailScanner/MailScanner.conf - you need to make sure that the following options are set:
Spam Actions and High Scoring Spam Actions should also have 'store' as one of the keywords if you want to quarantine those items for bayes learning or viewing from within MailWatch.
If you would like to manage the MailScanner whitelist and blacklist from within the MailWatch web interface perform the following steps.
1. Edit the MySQL connection values within the CreateList subroutine of SQLBlackWhiteList.pm to match the values you entered previous into MailWatch.pm. Both files should contain the same values. (Look for the following lines in SQLBlackWhiteList.pm and enter your own data.)
my($db_user) = '<username>'; my($db_pass) = '<password>';
2. Copy SQLBlackWhiteList.pm to /usr/lib/MailScanner/MailScanner/CustomFunctions/
3. Edit MailScanner.conf and set:
Edit /etc/MailScanner/spam.assassin.prefs.conf and set:
Create the 'new' bayes directory, make the directory owned by the same group as the web server user and make the directory setgid:
# mkdir /etc/MailScanner/bayes # chown root:apache /etc/MailScanner/bayes # chmod g+rws /etc/MailScanner/bayes
Copy the existing bayes databases and set the permissions:
# cp /root/.spamassassin/bayes_* /etc/MailScanner/bayes # chown root:apache /etc/MailScanner/bayes/bayes_* # chmod g+rw /etc/MailScanner/bayes/bayes_*
Test SpamAssassin to make sure that it is using the new databases correctly:
# spamassassin -D -p /etc/MailScanner/spam.assassin.prefs.conf --lint
and you should see something like:
debug: using "/etc/MailScanner/spam.assassin.prefs.conf" for user prefs file debug: bayes: 28821 tie-ing to DB file R/O /etc/MailScanner/bayes/bayes_toks debug: bayes: 28821 tie-ing to DB file R/O /etc/MailScanner/bayes/bayes_seen debug: bayes: found bayes db version 2 debug: Score set 3 chosen.
Start MailScanner up again.
# service MailScanner start && tail -f /var/log/maillog
You should see something like:
Jun 13 12:18:23 hoshi MailScanner: MailScanner E-Mail Virus Scanner version 4.20-3 starting... Jun 13 12:18:24 hoshi MailScanner: Config: calling custom init function MailWatchLogging Jun 13 12:18:24 hoshi MailScanner: Initialising database connection Jun 13 12:18:24 hoshi MailScanner: Finished initialising database connection
Congratulations - you now have MailScanner logging to MySQL.
Point your browser to http:<hostname>/mailscanner/ - you should be prompted for a username and password - enter the details of the MailWatch web user that you created earlier, and you should see a list of the last 50 messages processed by MailScanner. ==Update the SpamAssassin Rules table== MailWatch keeps a list of all the SpamAssassin rules and descriptions which are displayed on the 'Message Detail' page - to show the descriptions, you need to run the updater every time you add new rules or upgrade SpamAssassin. Click on the 'Tools/Links' menu and select 'Update SpamAssassin Rule Descriptions' and click 'Run Now'. ==Update the GeoIP database== Make Sure you have allow_url_fopen = On in your php.ini set. mkdir yourwwwroot/mailscanner/temp chown (your www server user and group) yourwwwroot/mailscanner/temp chmod gu+wr yourwwwroot/mailscanner/temp Click on the 'Tools/Links' menu and select 'Update GeoIP database' and click 'Run Now'. ==Setup the Mail Queue watcher (optional)== You can get MailWatch to watch and display your sendmail or exim queue directories - all you need to do is copy mailq.php (from the root of the mailwatch tarball - not from the mailscanner directory - they are different!) to /usr/local/bin and set-up a cron-job to run it. Edit mailq.php first to change the require line to point to the location of functions.php, then: # cp mailq.php /usr/local/bin # crontab -e 0-59 * * * * /usr/local/bin/mailq.php Note: mailq.php re-creates all entries on each run, so for busy sites you will probably want to change this to run every 5 minutes or greater. ==Setup the Sendmail Relay Log watcher (optional)== You can get MailWatch to watch your sendmail logs and store all message relay information which is then displayed on the 'Message Detail' page which helps debugging and makes it easy for a Helpdesk to actually see where a message was delivered to by the MTA and what the response back was (e.g. the remote queue id etc.). # cp tools/sendmail_relay.php /usr/local/bin # nohup /usr/local/bin/sendmail_relay.php 2>&1 > /dev/null & FINISHED!! (Phew!) Please send any errors or omissions to the mailing-list or directly to me. Thanks! Steve. – If you find MailWatch useful then consider buying something from my wishlist at amazon.co.uk - you can find my list using my e-mail address email@example.com. Thanks! resume service resume writing