Software Support Documentation
@Mail Installation Guide
@Mail System Documentation : v 4.5
The latest version of this file can be found at:
http://support.atmail.com/

 

Server Mode @Mail RPM Installation and Configuration Guide

1. Pre-Installation

Before installing the Server Mode @Mail RPM, you should first check the following:

  • Verify that any existing smtp/pop3/imap servers are disabled. By default the installation utility will disable the previous SMTP servers ( for example: Sendmail / Postfix ) however you may need to manually disable these services if custom installed
  • Check that no other atmail installations are installed, including the evaluation version. For upgrading previous @Mail installations please reference the upgrade-guide
  • Verify that the system has PHP installed. ( default under any common Linux distribution )
  • Check that you are logged in as root before beginning the installation.

@Mail can be installed using two different RPM methods. These include using the "yum" command under Fedora, or the regular RPM command manually. Both installation methods are outlined below, it is recommended to use the "yum" method for Fedora systems.

2. Installing using Yum

By using the "yum" feature of RedHat Fedora the @Mail software can be easily installed, with any missing dependencies automatically installed. This is the easiest method to install @Mail and requires the least effort.

To install follow the steps below in the exact order

  1. Download the RPM package for your system, for example under the /tmp/ directory for the initial configuration.
  2. Next, import the @Mail Public-key. This is required to allow the "yum" installer to validate the RPM package of @Mail is trusted.

    Manually run the rpm command as follows:

    root# rpm --import http://atmail.com/atmailphp-publickey.pub

    Importing the PGP key for the @Mail package

    This is required to trust installing the @Mail package using the yum command. Note once the Public-key is loaded no output is returned.
  3. Next the @Mail package can be automatically installed using the "yum" command. The utility will connect to the yum-repository and automatically download any missing dependences to install the software.

    root# yum localinstall atmailserver.rpm

    Loading "installonlyn" plugin
    Setting up Local Package Process
    Examining atmailserver-demo.rpm: atmail-mailserver - 5.1demo-1.noarch
    Marking atmailserver-demo.rpm to be installed
    Setting up repositories
    Reading repository metadata in from local files
    Resolving Dependencies
    --> Populating transaction set with selected packages. Please wait.
    ---> Package atmail-mailserver.noarch 0:5.1demo-1 set to be updated
    --> Running transaction check

    Dependencies Resolved

    =============================
    Package Arch Version Repository Size
    =============================
    Installing:
    atmail-mailserver noarch 5.1demo-1 atmailserver-demo.rpm 101 M

    Transaction Summary
    =============================
    Install 1 Package(s)
    Update 0 Package(s)
    Remove 0 Package(s)

    Total download size: 101 M
    Is this ok [y/N]:

    Downloading Packages:

    Installed: atmailwebmail.rpm

    Using yum to install @Mail via the command-line

    The output of the yum command will be similar as above. If any missing dependencies are detected ( e.g mysql, apache, php ) a prompt via yum will appear to install the missing packages.
  4. Once the yum command is complete the software can be initially configured using the command-line install.php script. Follow the next step as outlined under Section 5 of the install tutorial.

3. Installing using RPM manually

  1. Download the RPM package for your system, for example RedHat 9, RedHat ES/WS/AS, Mandrake
  2. Manually run the rpm command on the @Mail RPM package, this will not install any dependencies that are missing on your system

    /tmp# rpm -vi atmailserver.rpm

    Please note the -vi flags, this is for 'verbose installation'. The installation will take between 1-5 minutes depending the speed of the hardware. Do not exit from the RPM command once run.

    If you receive an error during the RPM installation, validate you have the correct Dependencies installed for @Mail. See below for a complete listing.

4. Dependencies

@Mail requires the following dependant applications:

  • MySQL-Server ( if the @Mail Application will be accessing the MySQL server on the same system.)
  • MySQL-client - http://www.mysql.com/
  • Apache/httpd - Apache is required and is usually installed by default with most Linux Distributions and Unix Variants - http://httpd.apache.org/
  • PHP 5.0+ recommended . Minimum PHP 4.3+ required - PHP is required and is usually installed by default with most Linux Distributions and Unix Variants.
  • openssl and openssl-devel
  • Zlib and Zlib-devel
  • DB and DB-devel
  • GDBM and GDBM-devel (only if DB libraries are not available)
  • GCC-c++ (G++)
  • To locate a missing dependency please reference: rpmfind.net -- it will give you a list of packages and dependencies, each dependency is cross-linked to a list of packages which provide them.

    http://rpmfind.net

    You can also find the required dependencies from the Linux CD Installation discs

    5. The Install Script

    The Installation script is a PHP script that is run after a successful RPM install, in that : all the necessary files are in the correct places and necessary services have been installed.

    The purpose of this script is to configure the @Mail application and save the runtime settings to the main @Mail Configuration file (Config.php). You run the installation script by running the following commands:

    # cd /usr/local/atmail/webmail/
    # php server-install.php server

    After the welcome screen, the script goes through various sections regarding software and system dependencies. The first option for user input will be the Database Configuration

    SQL Database Configuration

    @Mail can be installed to use an SQL database backend to store user emails and account information. We recommend the use of mySQL for the Database backend for @Mail, which can be freely obtained at http://www.mysql.com/

    Select the database name to store email/account information
    Select Database Name: [atmail]:

    Enter which user to connect to the database server. The users needs
    full permissions over the table to modify/read/write
    Enter Username: [root]:

    Enter the password for root to connect
    Enter Password for root: []:

    Next, specify the hostname / IP address of the MySQL server.

    Using @Mail you can scale the software solution by storing user email/account information on a separate machine from the webserver.

    It is recommended to use @Mail and mySQL on the same machine for userbases under < 10,000 accounts.

    If the MySQL server is setup on the same machine leave the 'Hostname' field blank. This will make @Mail communicate with the database server directly rather then opening a TCP/IP connection.
    Enter Hostname: []:

    MySQL Database system configuration for @Mail

    After this step you will have the option of creating the tables for the @Mail database, and test the MySQL configuration details are correct. After the screens for enabling the Groupware module and specifying the Apache binary path, you will be given the option of entering the Domain name.

    Domain Configuration
    --------------------

    Please specify the domain names for which you wish to configure for @Mail. At
    least one domain name must be specified to complete the installation. Enter
    domain names for which you wish to host email accounts. Separate multiple
    domains by a comma.

    Specify Domains: [uno.calacode.com]:
    Domain Name Configuration

    Here you can enter your domains. Ensure that you separate your domains with a comma for example:

    mydomain.com, theirdomain.net, ourdomain.com, themdomain.org

    The install script will then restart the mail servers to recognize the domain/s you entered in the above step.

    @Mail Configuration

    @Mail Configuration
    -------------------

    Provide the following information to compile a libs/Atmail/Config.php file
    based on your server's unique configuration.

    Enter admin email address: [admin@yourdomain.com]:
    Entering the Admin Email

    You will be first asked to add the Email Administrator account. The purpose of this is to allow any @Mail error or notification emails to be sent to this account.

    The next step in configuration, will run an diagnostic utility to verify local mail delivery for your @Mail system .

    The following tests are preformed: Account signup, message sending, message viewing via WebMail, POP3 access, AV and Spam Scanning. The diagnostic utility can also be used via the graphical Webadmin to verify the installation.

    Running Email-Server tests.

    --- Creating account: OK

    --- Testing Mail Send: OK

    --- Accessing Mail: OK

    --- Viewing Mail messages: OK

    --- Checking remote POP3 for 427914305@yourdomain.com: OK

    --- Testing SMTP Virus scanner: OK

    --- Testing Anti-Spam scanner: OK

    --- 7 tests passed out of 7 ( 100 % )

    Successful result of the diagnosis utility
    6. Installed Directories and @Mail user.

    /usr/local/atmail/ - The base installation directory, this is fixed for the @Mail

    /usr/local/atmail/webmail/ - The Webmail/Webadmin application for @Mail.

    /usr/local/atmail/av/ - The optional AV scanner for @Mail

    /usr/local/atmail/spamassassin/ - The spamassassin installation directory, a custom build for @Mail.

    /usr/local/atmail/mailserver/ - The SMTP, POP3 and IMAP services

    The @Mail user is atmail this is the basic user required to navigate the ownership and permissions used for each part of the @Mail application, this user is created in the RPM install.

    7 Post Installation and Contact Support

        7.1 Post Installation

    Once the installation is complete, @Mail will startup the Mail-server and the software can be accessed via the address:

    http://youraddress.com/mail/

    Here you can access the WebMail interface of @Mail and setup a new email-account at your selected domain. To begin using the WebAdmin interface of @Mail visit the URL:

    http://youraddress.com/mail/webadmin/

    After visiting the Webadmin you must enable a password for the access using the Webadmin -> Security -> Admin Password menu

    Please note the following:

    • The file /etc/httpd/conf.d/phpatmail.conf is the webserver configuration file for @Mail.

    • The /mail/ part of the @Mail URL is an alias, this provides a link from the browser http://server.com/mail/ to the path on your system where the application is installed /usr/local/atmail/webmail/

    • The /etc/init.d/atmailserver startup script is used to stop/start/restart @Mail required services.

    • A note for Virtualhosts: the Alias /mail/ can also be accessed from VirtualHosts if the username which runs the host is the same as the main httpd user 'atmail'.

    Web Admin

    Webadmin Interface: the next step

        7.2 Troubleshooting

    1. SMTP server doesn't start / No Services are running

      Run the following command to start the necessary services for @Mail:

      # /etc/init.d/atmailserver start

    2. I can't access the @Mail URL

      Check that your Apache Server is running under the atmail user.

    3. Webadmin Interface appears does not prompt for a username/password

      Access the Webadmin and go to the Security -> Admin Password menu item and enter a new password: This script will update the /usr/local/atmail/webmail/webadmin/.htpasswd file, any subsequent action in the Webadmin Interface will bring up the authentication window.

    4. I can't access the Webadmin Interface since I forget the username/password

      On the command line, cd to the Webadmin Folder and delete the existing .htpasswd and .htaccess files:

      # cd /usr/local/atmail/webmail/webadmin/

      # rm .ht*


      and perform the Admin Password change in the solution above to secure the Webadmin Interface.

    5. Can't access POP3 / IMAP externally

      Review your firewall to allow the following ports:

      25 ( SMTP )
      80 ( Web )
      110 ( POP3 )
      143 ( IMAP )

    6. Permission errors or messages can't be received

      Check that your @Mail directories are owned by the user atmail . This is required to run as the single user, since the POP3, SMTP, and IMAP daemons run under this username for read/write access. The Webserver must be running as the same username, otherwise the WebMail interface cannot read/modify the users mail-messages.

    7. Can't IP relay or use the SMTP for outgoing messages

      Access the Webadmin to specify IP ranges for relay, or enable SMTP-authentication support under the WebAdmin -> Services -> SMTP Settings menu.

    8. I receive the following error when using the "yum" installation method.
      "Warning: rpmts_HdrFromFdno: V3 DSA signature: NOKEY, key ID 8df56d05
      Error: Could not find the GPG Key necessary to validate pkg ..."

      When installing the @Mail package using the yum command, the GPG public key must be installed to trust the software package. Using the following command to install the key:

      rpm --import http://atmail.com/atmailphp-publickey.pub

      Then re-install using the yum command to resume installation.

    8 Contact Support

    For additional support, please visit the @Mail Knowledge base at: http://kb.atmail.com/ for Hints/Tips and advice on how to install and administer the software.

    For technical support via email please contact: support@CalaCode.com

     

    877-4-ATMAIL (Sales) +1 773-451-8334 (USA) +61 245-730745 (Australia)

    home | email server | webmail client | email appliance | antivirus | anti spam | groupware | secure email | email admin | email sms | purchase | FAQ | support | KB | Blog | sitemap