Creating smarthosts with Exim is easy, but you may want to enable SMTP authentication during transactions for additional security. Just go through the following steps:

1.) Open up your /usr/local/atmail/mailserver/configure file, and find:

dnslookup:
driver = dnslookup
domains = ! +local_domains
transport = remote_smtp
ignore_target_hosts = 0.0.0.0 : 127.0.0.0/8
no_more

2.) Comment out this line so it looks like:

#dnslookup:
# driver = dnslookup
# domains = ! +local_domains
# transport = remote_smtp
# ignore_target_hosts = 0.0.0.0 : 127.0.0.0/8
# no_more

3.) Add this line below:

divertnonlocal:
driver = manualroute
domains = ! +local_domains
transport = remote_smtp
route_list = * 192.168.0.6
ignore_target_hosts = 0.0.0.0 : 127.0.0.0/8
no_more

4.) Replace "192.168.0.6" with your SMTP relay host (your smarthost destination).

5.) Find this line afterwards:

remote_smtp:
driver = smtp

6.) Change it to:

remote_smtp:
driver = smtp
 hosts_require_auth = 192.168.0.6
hosts_try_auth = 192.168.0.6

7.) Change "192.168.0.6" to your smarthost server.

8.) At the bottom of the file, find this line:

begin authenticators

9.) Below this, add:

login:

driver = plaintext

public_name = LOGIN

 (more...)

	

Ok so you've tried Atmail Open and liked the experience but now want the full Atmail experience and have purchased the commercial version. Now you ask "how can I upgrade from Atmail Open to Atmail commercial and not loose all my users' data?" Well follow these simple steps and you'll quickly be on your way to running Atmail.

First of all you will need to make sure you are running the lastest version of Atmail Open so that you have the up to date version of the upgrade script. Then if you haven't already you will need to purchase and download the commercial version. You will then need to extract the files into place. Where you extract the files will depend on what version you purchased, server+client or client only.

If you have purchased the server+client version then extract the tgz into /usr/local, this will extract out the Atmail files under /usr/local/atmail.

If you have purchased the client only version then extract the files into your existing Atmail Open directory.

Once the files are extracted you need to run the upgrade2atmail.php script found in your Atmail Open directory, this script will make all necessary modifications to your Atmail Open database so it can be used by the commercial version:

# cd /path/to/atmailopen
# php upgrade2atmail.php

NB: This script can only be run from the command line and should only be run once you are ready to install Atmail commercial version.

Once the script has completed you should run the relevant installer for the version you purchased. If you purchased the client only version you may need to remove the .htaccess file from the install/ directory before you can run the web based installer.

Webmail client install instructions

Server version install instruction

Vital!: When you get to the database set up section be sure to select or enter the name of the database used by Atmail Open so that all your user info will be available

Migrating users (Server Version only)

If you are upgrading to the full Atmail server version then you will need to migrate your users and their email into the Atmail system. How to achieve this depends on the formats used by the old mail server. You will find info on migrating from many different mail systems here on the KB under the Migration category and also several migrate scripts can be found in your /usr/local/atmail/webmail/modules directory.

Under a fresh installation of RedHat Fedora Core3 ( FC3 ) , a compile of the Clam/@Mail Anti-virus daemon can fail with the following:

gcc: /usr/lib/libidn.so: No such file or directory
make[2]: *** [libclamav.la] Error 1
make[2]: Leaving directory `/usr/local/atmail/webmail/libs/src/clamav/libclamav'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory

root# ln -s /usr/lib/libidn.so.11.4.6 /usr/lib/libidn.so

ClamAV, at times, fails and puts mail delivery and the processing of emails in the spool to a stop. This can be avoided by using ClamAV with supervise, a Unix tool that comes with the daemontools (http://cr.yp.to/daemontools.html) package, which basically checks if a service is running, then re-runs it if found inactive.
Implementing supervise with ClamAV is pretty straightforward. Just go through the following steps:

(more...)

When you want to upgrade SpamAssassin 2.63 for @Mail to 3.0, keep in mind that the two versions have different SQL querying schemas. Also, you may need to take out some lines in the local.cf file, as many options have been deprecated.To upgrade your SpamAssassin installation, just run through the following steps:

(more...)

Should you want to see if your Spam filter is working, just send an email with the following string:

XJS*C4JDBQADN1.NSBN3*2IDNEN*GTUBE-STANDARD-ANTI-UBE-TEST-EMAIL*C.34X

This is the GTUBE - the Generic Test for Unsolicited Bulk Email. If your spam filter supports it, the GTUBE provides a test by which you can verify that the filter is installed correctly and is detecting incoming spam, in a similar fashion to the EICAR anti-virus test file.

Question:We are using @Mail in the mail-server mode with the AV scanner. We'd like all incoming messages that are clean via the AV scanner to append a header "X-Virus-Scanned: Clean" to each message in the users mailbox.

Answer:This is possible by editing the transport router in Exim to append the new header for each incoming message.

(more...)

Should you want to disable SpamAssassin for some domains or users, just do the following:- open up your /usr/local/atmail/mailserver/configure
- find the following lines:

domains = ${lookup mysql {MYSQL_CHECKSPAM}{$value}}

- replace this with:

domains = lsearch;/usr/local/atmail/mailserver/domains

- create a file /usr/local/atmail/mailserver/domains, and put your desired domains to enable SpamAssassin with, in the following format:

domain1.com
domain2.com

- restart Exim:

% /etc/init.d/atmailserver restart

This will then limit the SpamAssassin filtering to the users in the domains listed.