MISCELLANEOUS

  1. To handle multiple POP3 domains, the server makes a reverse lookup of the IP address upon which it receives the connection. Suppose the reverse lookup results in 'xxxx.yyyy.zzzz'. AfterLogic XMail Server checks if 'xxxx.yyyy.zzzz' is handled, then it checks 'yyyy.zzzz', and then 'zzzz'. The first resolved (in the given order) is the POP3 domain. To avoid the above behavior, it's sufficient that the POP3 client supply the entire email address as POP3 login username:

     foo@foodomain.net   ==> foo@foodomain.net

    and not:

     foo@foodomain.net   ==> foo

    This enables AfterLogic XMail Server to handle multiple domains in cases where more nic-names are mapped over a single IP address.

    To run finger queries you must specify:

     foo@foodomain.net@foodomain.net

    or as general rule:

     username@pop3domain@hostname

    You can use the optional configuration variable 'POP3Domain' (see SERVER.TAB VARIABLES above) to set the default domain for POP3 clients connections. This means that users of 'POP3Domain' can use only the name part of their email address as POP3 login, while users of other hosted domains must use their entire email as POP3 login.

  2. Important!

  3. The main cause of bugs with AfterLogic XMail Server is due a bad line termination of configuration files, so check that these files being correctly line terminated for your OS. Linux uses the standard <CR> while M$ uses <CR><LF>.

  4. If you get a bind error in Linux,you must comment pop3, smtp and finger entries in your /etc/inetd.conf.

  5. Remember to compile the file CTRL.IPMAP.TAB to restrict the access to the IPs you use to remote administer AfterLogic XMail Server server.

  6. If you have an heavily loaded server remember to setup the best number of XMAIL threads by specifying the '-Qn nthreads' option (you must do some tentatives to find the best value for your needs). Also you can limit the number of SMTP, POP3 and CTRL service threads by specifying the options '-SX maxthreads', '-PX maxthreads' and '-CX maxthreads'.

  7. If you have enabled logging, remember to setup the '-Mr hours' option depending on the traffic you get in your server. This avoids AfterLogic XMail Server having to work with very large log files and can improve server performance.

  8. If you are unable to start AfterLogic XMail Server (even if you followed this document's instructions), check the MailRoot directory with the one listed above. More than one unzipper does not restore empty directories by default.

Please report AfterLogic XMail Server errors and errors in this document. If you successfully run AfterLogic XMail Server please let us know at support@afterlogic.com

[top]