@Mail now supports migrations from the SurgeMail Webmail platform. The migration script can import previous Address-book data, Distribution lists, and Tasks from the flat-file database used by Surgemail.
When using CentOS, you may find yourself requiring to use the "yum" package manager, when you do not have Internet access, or your link to download packages is to slow.
When using the mail-server mode of @Mail, all messages are stored in "maildir" format on the system.
This creates the ability to share folders between other users, creating a "Public" folder feature where users can view/add/delete messages.
To implement, login to a local @Mail account where you want to share a specific folder.
Exim needs to write to at least four files when delivering one message. This can take a toll on your I/O writes. You can reduce this by turning off individual message logs, an inessential part of Exim:
- open up /usr/local/atmail/mailserver/configure
- add this line on top:
message_logs = false
- save changes, restart Exim:
% killall -HUP exim
This will then turn off msglogs.
Question: I have an SSL certificate signed by Verisign for my SSL Webserver. I would like to use the same certificate for my POP3/IMAP server using @Mail via SSL.
How can I used the certificate files generated from my SSL provider? This is required so users will not receive a security popup message when connecting via SSL, since the connection will be trusted automatically.
Answer: Obtain the certficiate.key and certificate.crt files that are generated by your SSL provider, these can be used to create the .pem format the POP3/IMAP server require when running via SSL.
By default @Mail uses the InnoDB database format via mySQL for the most frequently used database tables.
This increases performance for the application, however uses more memory and disk resources via MySQL.
If you experience problems using the InnoDB format you can switch to the default table format of MySQL ( MyISAM )
For technical details on the different database formats of MySQL see:
Excluding MySQL tables is not included in some versions of MySQL. Here's a bash script that can do just that:
- create a file called mysqldump.sh
- in the file, put:
#!/bin/sh
for TABLE in $(echo "show tables" | mysql -u [mysqluser] -p[mysqlpassword] [atmaildatabase] | grep -v Tables_in_ | grep -v [Excluded Tables])
do
mysqldump -v --add-drop-table -u [mysqluser] -p[mysqlpassword] [atmaildatabase] ${TABLE} > [mysqldumpfile.sql]
done
When installing @Mail Server on CPanel, keep the following in mind:
Make sure that your Cpanel-POP3 service is disabled. This, along with CPIMAP, must be disabled from your WHM. The configuration panel for it can be found in the Service Manager portion of your WebHost Panel.
Make sure that you have a separate VirtualHost for the @Mail installation. You can do this by creating a barebones VirtualHost in your Apache configuration (/etc/httpd/conf/httpd.conf):
DocumentRoot /usr/local/atmail/webmail ServerName yourdomain.com ServerAlias mail.yourdomain.com
Replace yourdomain.com with your hostname, and
mail.yourdomain.com with your ServerAlias.
Afterwards, restart Apache:
% /etc/init.d/httpd restart
Some users expressed the need to have the RBL-checking done on a per-domain basis. This can be done by running through the following steps:
- locate the following line in your /usr/local/atmail/mailserver/configure file;
MYSQL_CATCHALL = select AliasTo from MailAliases where AliasName='$domain'
- add the following below:
MYSQL_RBL = select Hostname from Domains where RBL='1'
After restarting @Mail via the sysv init, or init.d, you may have some errors with the clamdsocket not being able to connect. It looks like this:
malware acl condition: clamd: unable to connect to UNIX socket /usr/local/atmail/av/clamdsocket (Connection refused)
This may be caused by a stale clamd socket not being deleted. To fix, you can go through the following steps: (more...)