You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am new to mailwatch ... please help me to have working instructions for How to configure MailScanner to log to a remote MySQL database
As per provided documentation in source code Remote_DB.md file is referencing some steps in INSTALL file and there is file available having following output. Where I can find the steps to completely configure MailScanner to log to a remote MySQL database.
File Name: INSTALL.md
INSTALLATION INSTRUCTIONS
Installation instruction has moved to http://docs.mailwatch.org --> Neither any step referenced in Remote_DB.md mentioned here nor on provided URL
File Name: Remote_DB.md
How to configure MailScanner to log to a remote MySQL database
This document presumes that you will have a server acting as a database with PHP and MySQL installed on it, and multiple MailScanner gateways logging to the database server.
1) Follow steps 1 to 6 from the INSTALL document on the database server.
Create a mailscanner user and password on the database server:
% mysql mailscanner
mysql> GRANT ALL ON mailscanner.* TO mailscanner IDENTIFIED BY 'password';
mysql> flush privileges;
On each MailScanner gateway, you'll need to make sure that the mysql client, perl, perl DBI and perl DBD-Mysql, are installed:
% rpm -qa | grep "mysql"
mysql-3.23.54a-11
% rpm -qa | grep "perl-DB"
perl-DBD-MySQL-2.1021-3
perl-DBI-1.32-5
From one of the MailScanner gateway, verify you can connect to the db:
% mysql mailscanner -u mailscanner -h <db_hostname> -p
Enter password: *******
If you get a mysql> prompt, you can connect correctly (enter \q to quit).
On each MailScanner gateway, do steps 7 to 10 from the INSTALL document, for step 7, you will also need to edit CustomConfig.pm and change the $db_host, $db_user and $db_pass variables to your local settings.
6) To complete the set-up run steps 11 to 15 on the database server.
On each MailWatch system set RPC_ALLOWED_CLIENTS in conf.php to a list of IP addresses of each MailWatch system.
The text was updated successfully, but these errors were encountered:
Hi,
I am new to mailwatch ... please help me to have working instructions for How to configure MailScanner to log to a remote MySQL database
As per provided documentation in source code Remote_DB.md file is referencing some steps in INSTALL file and there is file available having following output. Where I can find the steps to completely configure MailScanner to log to a remote MySQL database.
File Name: INSTALL.md
INSTALLATION INSTRUCTIONS
Installation instruction has moved to http://docs.mailwatch.org
--> Neither any step referenced in Remote_DB.md mentioned here nor on provided URL
File Name: Remote_DB.md
How to configure MailScanner to log to a remote MySQL database
This document presumes that you will have a server acting as a database with PHP and MySQL installed on it, and multiple MailScanner gateways logging to the database server.
1) Follow steps 1 to 6 from the INSTALL document on the database server.
Create a mailscanner user and password on the database server:
% mysql mailscanner
mysql> GRANT ALL ON mailscanner.* TO mailscanner IDENTIFIED BY 'password';
mysql> flush privileges;
On each MailScanner gateway, you'll need to make sure that the mysql client, perl, perl DBI and perl DBD-Mysql, are installed:
% rpm -qa | grep "mysql"
mysql-3.23.54a-11
% rpm -qa | grep "perl-DB"
perl-DBD-MySQL-2.1021-3
perl-DBI-1.32-5
From one of the MailScanner gateway, verify you can connect to the db:
% mysql mailscanner -u mailscanner -h <db_hostname> -p
Enter password: *******
If you get a mysql> prompt, you can connect correctly (enter \q to quit).
On each MailScanner gateway, do steps 7 to 10 from the INSTALL document, for step 7, you will also need to edit CustomConfig.pm and change the $db_host, $db_user and $db_pass variables to your local settings.
6) To complete the set-up run steps 11 to 15 on the database server.
The text was updated successfully, but these errors were encountered: