XMail - Internet/Intranet mail server.
[top]
This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation (http://www.gnu.org); either version 2 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
[top]
XMail is an Internet and Intranet mail server featuring an SMTP server, POP3 server, finger server, multiple domains, no need for users to have a real system account, SMTP relay checking, RBL/RSS/ORBS/DUL and custom (IP based and address based) spam protection, SMTP authentication (PLAIN LOGIN CRAM-MD5 POP3-before-SMTP and custom), a POP3 account synchronizer with external POP3 accounts, account aliases, domain aliases, custom mail processing, direct mail files delivery, custom mail filters, mailing lists, remote administration, custom mail exchangers, logging, and multi-platform code.
XMail sources compile under GNU/Linux, FreeBSD, OpenBSD, NetBSD, OSX, Solaris and NT/2K.
This server was born due to the need of having a free and stable Mail Server to be used inside my old company, which used a Windows Network. I don't like to reinvent the wheel but the need of some special features drive me to start a new project. Probably if I could use a Linux server on my net, I would be able to satisfy my needs without writing code, but this is not the case. It should be also portable to other OSs, like Linux and other Unixes.
Another reason that drove me to write XMail is the presence of the same steps in setting up a typical mail server, i.e.:
sendmail + qpopper + fetchmail
if one needs SMTP, POP3 and external synchronization, or:
sendmail + qpopper
for only SMTP and POP3 (I've quoted sendmail, qpopper and fetchmail, but there are many other packages you can use to reach these needs). With XMail you get an all-in-one package with a central administration that can simplify the above common steps.
The first code of XMail Server is started on Windows NT and Linux, and now, the FreeBSD and Solaris version ready. The compilers supported are gcc for Linux, FreeBSD, OpenBSD and Solaris and M$ Visual C++ for NT/2K.
[top]
1.27
Gnu Public License http://www.gnu.org
Feb 25, 2010
Davide Libenzi <[email protected]> http://www.xmailserver.org/
Michael Hartle <[email protected]>
Shawn Anderson <[email protected]>
Dick van der Kaaden <[email protected]>
Beau E, Cox <[email protected]>
************************************************************ * <<WARNING>> * * If you're upgrading an existing version of XMail it's * * strongly suggested that you read all the ChangeLog * * notes that range from existing version to the new one. * ************************************************************
See the Change Log.
[top]
This document contains various examples of entries you must make to the XMail configuration tables. These examples are written in a
mono-spaced font like this.
The prototype statement is shown with explicit '[TAB]' and '[NEWLINE]' characters:
"aliasdomain"[TAB]"realdomain"[NEWLINE]
while examples omit these characters:
"simpson.org" "simpson.com" "*.homer.net" "homer.net"
'YOU MUST ALWAYS ENTER THE DATA EXACTLY AS SHOWN IN THE PROTOTYPE.'
When a prototype or example statement is too long to be easily shown on the screen or printed, the line is split into multiple lines by showing '=>' at the end of continued lines and indenting the continuation line(s):
"domain"[TAB]"account"[TAB]"enc-passwd"[TAB]"account-id"[TAB]"account-dir"[TAB]=> "account-type"[NEWLINE]
'DO NOT ENTER THE => CHARACTERS. ENTER THE ENTIRE ENTRY AS ONE LINE.'
[top]
ESMTP/ESMTPS server
POP3/POP3S server
Finger server
Multiple domains
Users don't need a real system account
SMTP relay checking
Custom SMTP maps check
SMTP protection over spammers (IP based and address based)
SMTP authentication (PLAIN LOGIN CRAM-MD5 POP3/SMTP and custom)
SMTP ETRN command support
POP3 account synchronizer with external POP3 accounts
Account aliasing
Domain aliasing
Mailing lists
Custom mail processing
Locally generated mail files delivery
Remote administration
Custom mail exchangers
Logging
Multi platform (any Windows and almost any Unix OSs)
Fine grained message filters
Custom (external) POP3/SMTP authentication
TLS support for SMTP and POP3, both server and client side
[top]
Right now the Linux and NT ports are stable, while the Solaris, FreeBSD, OpenBSD and OSX ones have not been tested as well as the previous OSs.
[top]
Any version of Linux that has glibc.
Windows NT with ws2_32.dll correctly installed.
A working DNS and gateway to the Internet (if you plan to use it).
To build from source for Linux you need any version of gcc and glibc installed.
To build from source for Windows you need MS Visual C++ (makefile included).
-or- any other working compiler that provides support for the Win32 SDK.
[top]
Always get the latest sources at the XMail home page http://www.xmailserver.org/ because otherwise you may be using an old version.
Use the correct distribution for your system and don't mix Unix files with Windows ones because this is one of the most common cause of XMail bad behavior.
When you unzip (or untar) the package you've to check that the MailRoot directory contained inside the package itself is complete (look at the directory tree listed below) because some unzippers don't restore empty directories.
[top]
XMail depends on OpenSSL to provide SSL support, so the development package of OpenSSL (in Debian called libssl-dev) must be installed on your system. For Windows, the XMail source already contains a pre-built version of the OpenSSL libraries, include files, and executable. The OpenSSL web site can be found here http://www.openssl.org.
[Windows]
You have to have the command line environment setup before (usually the vcvars32.bat script inside the Visual C++ directory). You also need to copy the openSSL DLLs (located in "win32ssl\dll") inside the same folder where the XMail.exe binary resides.
C:> nmake /f Makefile.win If once you run the XMail binaries, Windows complains about missing DLLs, your system is probably missing the Microsoft CRT redistributable package, that you can download here L<http://www.xmailserver.org/vcredist_x86.exe>;.
[Linux]
# make -f Makefile.lnx
[FreeBSD]
# setenv OSTYPE FreeBSD # gmake -f Makefile.bsd
or (depending on the shell):
# OSTYPE=FreeBSD gmake -f Makefile.bsd
[OpenBSD]
# setenv OSTYPE OpenBSD # gmake -f Makefile.bsd
or (depending on the shell):
# OSTYPE=OpenBSD gmake -f Makefile.bsd
[NetBSD]
# setenv OSTYPE NetBSD # gmake -f Makefile.bsd
or (depending on the shell):
# OSTYPE=NetBSD gmake -f Makefile.bsd
[OSX]
# OSTYPE=Darwin make -f Makefile.bsd
or (depending on the shell):
# setenv OSTYPE Darwin # make -f Makefile.bsd
[Solaris]
# make -f Makefile.sso
Under Linux an init.d startup script is supplied (xmail) to allow you to run XMail as a standard rc? daemon. You must put it into /etc/init.d (it depends on which distro you're using) directory and then create K??xmail - S??xmail links into the proper directories.
Under Windows NT/2000/XP the XMail's executable is a Win32 service by default and if you want to have it built like a standard executable you've to comment the statement:
"#define SERVICE" in MainWin.cpp
When it's built as a service (default) you can run:
XMail --install
to install XMail as a manual startup service or:
XMail --install-auto
to install XMail as an automatic startup service.
If you run '--install' and you want XMail to run at NT boot, you must go in ControlPanel->Services and edit the startup options of XMail. Once you have the service version of XMail you can run it in a 'normal' way by executing:
XMail --debug [options]
[top]
Build XMail.
Log as root.
Copy the supplied MailRoot directory where you want it to reside (normally /var).
Do a # chmod 700 /var/MailRoot to setup MailRoot directory access rights.
Strip XMail executables if you want to reduce their sizes (strip filename).
Copy XMail executables to /var/MailRoot/bin.
Optionally, you can setup a dedicated temporary files directory for XMail, by setting the environment variable XMAIL_TEMP, which defaults to /tmp/. XMail uses such directory when it has to create files that must be accessible to external programs like filters.
If you have 'inetd' installed, comment out the lines of '/etc/inetd.conf' that involve SMTP, POP3, and Finger. Restart 'inetd' (kill -HUP ...).
Since XMail uses syslog to log messages, enable syslogd if it's not running.
Setup the 'SERVER.TAB' configuration file (after reading the rest of this document well).
Add your users and domains (after reading the rest of this document well).
Change or comment out (#) the example account in 'ctrlaccounts.tab' by using a non-trivial username and password.
Copy the xmail startup script to your init.d directory (it's position depends on your distro). If you've setup XMail to work in a subdirectory other than '/var/MailRoot' you must edit the xmail startup script to customize its boot parameters.
Use the 'sysv_inst.sh' shell script (from root user) to create SysV boot script - unless your distro has other tools to do this.
To start XMail without reboot you can run (from root): /etc/rc.d/init.d/xmail start otherwise reboot your machine.
Setup the file 'smtprelay.tab' if you want to extend mail relaying to IPs outside of the internet's private IP blocks (or you want to deny even those - that comes enabled by default with XMail).
Look at [SSL CONFIGURATION] for information about how to create the required 'server.key' and 'server.cert' files.
For further configuration options, please see the [COMMAND LINE] section.
[configuration] [top]
Build XMail.
Copy the supplied MailRoot directory where you want it to reside (normally 'C:\MailRoot').
Setup the MailRoot directory (and subdirectories and file) permissions to allow access only to System and Administrators. Doing this you can run XMail as a console startup only if you're Administrator (service startup as System).
Copy XMail executables to 'C:\MailRoot\bin'. Also copy the OpenSSL DLLs located in "win32ssl\dll" to 'C:\MailRoot\bin'.
With 'regedit', create 'GNU' key inside 'HKEY_LOCAL_MACHINE\SOFTWARE\' and then 'XMail' key inside 'HKEY_LOCAL_MACHINE\SOFTWARE\GNU'. Note: If you are using a 32bit binary with a 64bit Windows, replace 'HKEY_LOCAL_MACHINE\SOFTWARE\' with 'HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\' here, and in the points below.
Create a new string value named 'MAIL_ROOT' inside 'HKEY_LOCAL_MACHINE\SOFTWARE\GNU\XMail\' with value 'C:\MailRoot'.
Optionally create a new string value named 'MAIL_CMD_LINE' inside 'HKEY_LOCAL_MACHINE\SOFTWARE\GNU\XMail\' to store your command line options (read well the rest of this document).
Open an NT console (command prompt).
Go inside 'C:\MailRoot\bin' and run: XMail --install for a manual startup, or: XMail --install-auto for an automatic startup.
If you have other services that provide the same functionality as XMail, that is SMTP, POP3, or Finger servers, you must stop these services.
Setup the 'SERVER.TAB' configuration option after reading the rest of this document well.
Add your users and domains (after reading to the rest of this document well).
Setup file permissions of the 'C:\MailRoot' directory to grant access only to 'SYSTEM' and 'Domain Admins'.
Change or comment out (#) the example account in ctrlaccounts.tab by using a non-trivial username and password.
To start XMail without reboot you can go to: ControlPanel -> Services -> XMail server and start the service, otherwise reboot your machine.
Setup the file 'smtprelay.tab' if you want to extend mail relaying to IPs outside of the internet's private IP blocks (or you want to deny even those - that comes enabled by default with XMail).
Look at [SSL CONFIGURATION] for information about how to create the required 'server.key' and 'server.cert' files.
For further configuration options, please see the [COMMAND LINE] section.
[configuration] [top]
If you want to start XMail as a simple test you must setup an environment variable MAIL_ROOT that points to the XMail Server root directory.
Linux/etc.:
export MAIL_ROOT=/var/XMailRoot
Windows:
set MAIL_ROOT=C:\MailRoot
Allows the user to specify extra command line parameters (they will be appended to the ones specified in the command line).
Allows the user to specify the PID directory (Unix only ports). The specified directory must NOT have the final slash (/) appended to the path.
[configuration] [top]
Mail root directory contain these files:
aliases.tab <file> aliasdomain.tab <file> domains.tab <file> dnsroots <file> extaliases.tab <file> mailusers.tab <file> message.id <file> pop3links.tab <file> server.tab <file> server.cert <file> server.key <file> smtpgw.tab <file> smtpfwd.tab <file> smtprelay.tab <file> smtpauth.tab <file> smtpextauth.tab <file> userdef.tab <file> ctrlaccounts.tab <file> spammers.tab <file> spam-address.tab <file> pop3.ipmap.tab <file> smtp.ipmap.tab <file> ctrl.ipmap.tab <file> finger.ipmap.tab <file> filters.in.tab <file> filters.out.tab <file> filters.post-rcpt.tab <file> filters.pre-data.tab <file> filters.post-data.tab <file> smtp.ipprop.tab <file> smtp.hnprop.tab <file>
and these directories:
bin <dir>
cmdaliases <dir>
tabindex <dir>
dnscache <dir>
mx <dir>
ns <dir>
custdomains <dir>
filters <dir>
logs <dir>
pop3locks <dir>
pop3linklocks <dir>
pop3links <dir>
spool <dir>
local <dir>
temp <dir>
0 <dir>
0 <dir>
mess <dir>
rsnd <dir>
info <dir>
temp <dir>
slog <dir>
lock <dir>
mprc <dir>
froz <dir>
...
...
userauth <dir>
pop3 <dir>
smtp <dir>
domains <dir>
msgsync <dir>
and for each domain DOMAIN handled a directory (inside domains):
DOMAIN <dir>
userdef.tab <file>
mailproc.tab <file> [ optional ]
inside of which reside, for each account ACCOUNT:
ACCOUNT <dir>
user.tab <file>
mlusers.tab <file> [ mailing list case ]
mailproc.tab <file> [ optional ]
pop3.ipmap.tab <file> [ optional ]
and
mailbox <dir>
for mailbox structure, while:
Maildir <dir>
tmp <dir>
new <dir>
cur <dir>
for Maildir structure. The msgsync directory is used to store UIDL lists for PSYNC accounts that require leaving messages on the server. Inside the msgsync other directories will be created with the name of the remote server, directories that will store UIDL DB files.
[configuration] [top]
TAB ('something.tab') files are text files (in the sense meant by the OS in use: <CR><LF> for NT and <CR> for Linux) with this format:
"value1"[TAB]"value2"[TAB]...[NEWLINE]
The following sections explain each file's structure and use.
[configuration] [top]
"domain"[TAB]"alias"[TAB]"realaccount"[NEWLINE]
Example:
"home.bogus" "davidel" "dlibenzi"
define 'davidel' as alias for 'dlibenzi' in 'home.bogus' domain.
"home.bogus" "foo*bog" "[email protected]"
define an alias for all users whose name starts with 'foo' and ends with 'bog' that points to the locally handled account 'homer@internal-domain.org'.
"home.bogus" "??trips" "travels"
define an alias for all users whose names start with any two chars and end with 'trips'. You can even have wildcards in the domain field, as:
"*" "postmaster" "[email protected]"
You 'CANNOT' edit this file while XMail is running because it is an indexed file.
[table index] [configuration] [top]
"aliasdomain"[TAB]"realdomain"[NEWLINE]
where 'aliasdomain' can use wildcards:
"simpson.org" "simpson.com" "*.homer.net" "homer.net"
The first line defines 'simpson.org' as an alias of 'simpson.com' while the second remaps all subdomains of 'homer.net' to 'homer.net'.
You 'CANNOT' edit this file while XMail is running because it is an indexed file.
[table index] [configuration] [top]
"domain"[NEWLINE]
defines domains handled by the server.
[table index] [configuration] [top]
host
This is a file that lists a root name server in each line (this is not a TAB file). This can be created from a query via nslookup for type=ns and host = '.'.
[table index] [configuration] [top]
"external-domain"[TAB]"external-account"[TAB]"local-domain"[TAB]"local-user"[NEWLINE]
Example:
"xmailserver.org" "dlibenzi" "home.bogus" "dlibenzi"
This file is used in configurations in which the server does not run directly on Internet (like my case) but acts as internal mail exchanger and external mail gateway. This file defines 'Return-Path: <...>' mapping for internal mail delivery. If you are using an Mail client like Outlook, Eudora, KMail ... you have to configure your email address with the external account say 'dlibenzi@xmailserver.org'. When you post an internal message to 'foo@home.bogus' the mail client puts your external email address ('dlibenzi@xmailserver.org') in the 'MAIL FROM: <...>' SMTP request. Now if the user 'foo' replies to this message, it replies to 'dlibenzi@xmailserver.org', and then is sent to the external mail server. With the entry above in 'EXTALIASES.TAB' file the 'Return-Path: <...>' field is filled with 'dlibenzi@home.bogus' that leads to an internal mail reply.
You 'CANNOT' edit this file while XMail is running because it is an indexed file.
[table index] [configuration] [top]
"domain"[TAB]"account"[TAB]"enc-passwd"[TAB]"account-id"[TAB]"account-dir"[TAB]=> "account-type"[NEWLINE]
(remember, enter as one line.) Example:
"home.bogus" "dlibenzi" "XYZ..." 1 "dlibenzi" "U"
defines an account 'dlibenzi' in domain 'home.bogus' with the encrypted password 'XYZ...', user id '1' and mail directory 'dlibenzi' inside '$MAIL_ROOT/domains/home.bogus'. To allow multiple domain handling the POP3 client must use the entire email address for the POP3 user account; for example, if a user has email user@domain it must supply:
user@domain
as POP3 account login.
The directory 'account-dir' 'must' case match with the field 'account-dir' of this file. Note that user id 'must' be unique for all users (duplicate user ids are not allowed). The user id 0 is reserved by XMail and cannot be used.
The last field 'U' is the account type:
"U" = User account "M" = Mailing list account
The encrypted password is generated by 'XMCrypt' whose source is 'XMCrypt.cpp'. Even if external authentication is used (see External Authentication) this file 'must' contain an entry for each user handled by XMail.
You 'CANNOT' edit this file while XMail is running because it is an indexed file.
[table index] [configuration] [top]
A file storing a sequential message number. Set it at 1 when you install the server and leave it be handled by the software.
[table index] [configuration] [top]
"local-domain"[TAB]"local-account"[TAB]"external-domain"[TAB]=> "external-account"[TAB]"external-crypted-password"[TAB]"authtype"[NEWLINE]
(remember, enter as one line) where:
'authtype' = Comma-separated list of options:
Use clear-text USER/PASS authentication
Use POP3 APOP authentication (that does not send clear-text passwords over the wire). Fall back to 'CLR' if 'APOP' is not supported
Use POP3 APOP authentication (that does not send clear-text passwords over the wire).
Establish an SSL link with the server by issuing a POP3 STLS command. Continue with the non-encrypted link if STLS is not supported
Establish an SSL link with the server by issuing a POP3 STLS command.
Establish a full POP3S connection with the remote server. Note that the POP3S port (default 995) must be set inside the external domain declaration.
Leave messages on the server, and download only the new ones. In order for this functionality to work, the remote POP3 server must support the UIDL command.
Sets the IP address of the network interface that should be used when connecting to the remote host. This configuration should be used carefully, because XMail will fail if the selected IP of the interface does not have a route to the remote host using such IP.
Examples:
"home.bogus" "dlibenzi" "xmailserver.org" "dlibenzi" "XYZ..."=> "APOP"
This entry is used to synchronize the external account 'dlibenzi@xmailserver.org' with encrypted password 'XYZ...' with the local account 'dlibenzi@home.bogus' using 'APOP' authentication. It connects with the 'xmailserver.org' POP3 server and downloads all messages for 'dlibenzi@xmailserver.org' into the local account 'dlibenzi@home.bogus'. The remote server must support 'APOP' authentication to specify 'APOP' as authtype. Even if using APOP authentication is more secure because clear usernames and password do not travel on the network, when you're not sure about it, specify 'CLR' as authtype. For non local POP3 sync you've to specify a line like this one (@ as the first domain char):
"@home.bogus.com" "dlibenzi" "xmailserver.org:110" "dlibenzi" "XYZ..."=> "CLR"
This entry is used to synchronize the external account 'dlibenzi@xmailserver.org' with encrypted password 'XYZ...' with the account 'dlibenzi@home.bogus.com' using 'CLR' authentication. The message is pushed into the spool having as destination dlibenzi@home.bogus.com , so you've to have some kind of processing for that user or domain in your XMail configuration (for example custom domain processing). you can also have the option to setup a line like this one:
"?home.bogus.com,felins.net,pets.org" "dlibenzi" "xmailserver.org"=> "dlibenzi" "XYZ..." "CLR"
and messages are dropped inside the spool by following these rules:
XMail parses the message headers by searching for To:, Cc: and Bcc: addresses.
Each address's domain is compared with the list of valid domains (felins.net, pets.org).
For each valid address the username part is taken and joined with the '@' and the masquerade domain name (the name following '?').
The message is spooled with the above built destination address.
Obviously the masquerade domain ('home.bogus.com') MUST be handled by the server or MUST be a valid external mail domain. So if a message having as To: address graycat@felins.net is fetched by the previous line a message is pushed into the spool with address graycat@home.bogus.com. Particular attention must be paid to prevent creating mail loops. Another option is:
"&.local,felins.net,pets.org" "dlibenzi" "xmailserver.org" "dlibenzi"=> "XYZ..." "CLR"
where a fetched message whose To: address is graycat@felins.net is replaced with graycat@felins.net.local. You can avoid the matching domain list after the masquerading domain but, in that case, you may have bad destination addresses inside the spool. The list MUST be comma separated WITHOUT spaces. XMail starts PSYNC session with a delay that you can specify with the -Yi nsec command line parameter (default 120). XMail also checks for the presence (inside MAIL_ROOT) of a file named '.psync-trigger' and, when this file is found, a PSYNC session starts and that file is removed.
[table index] [configuration] [top]
"varname"[TAB]"varvalue"[NEWLINE]
This file contains server configuration variables. See SERVER.TAB variables below for details.
[table index] [configuration] [top]
"domain"[TAB]"smtp-gateway"[NEWLINE]
Examples:
"foo.example.com" "@xmailserver.org"
sends all mail for 'foo.example.com' through the 'xmailserver.org' SMTP server, while:
"*.dummy.net" "@relay.xmailserver.org"
sends all mail for '*.dummy.net' through 'relay.xmailserver.org'.
The 'smtp-gateway' can be a complex routing also, for example:
"*.dummy.net" "@relay.xmailserver.org,@mail.nowhere.org"
sends all mail for '*.dummy.net' through '@relay.xmailserver.org,@mail.nowhere.org', in this way: relay.xmailserver.org --> mail.nowhere.org --> @DESTINATION.
[table index] [configuration] [top]
"domain"[TAB]"smtp-mx-list"[NEWLINE]
The "smtp-mx-list" is a semicolon separated list of SMTP relays, and can also contain options as a comma-separated list (see [SMTP GATEWAY CONFIGURATION] for more information).
Examples:
"foo.example.com" "mail.xmailserver.org:7001;192.168.1.1:6123,NeedTLS=1;mx.xmailserver.org"
sends all mail for 'foo.example.com' using the provided list of mail exchangers, while:
"*.dummy.net" "mail.xmailserver.org,NeedTLS=1;192.168.1.1;mx.xmailserver.org:6423"
sends all mail for '*.dummy.net' through the provided list of mail exchangers. If the port (:nn) is not specified the default SMTP port (25) is assumed. you can also enable XMail to random-select the order of the gateway list by specifying:
"*.dummy.net" "#mail.xmailserver.org;192.168.1.1;mx.xmailserver.org:6423"
using the character '#' as the first char of the gateway list.
[table index] [configuration] [top]
"ipaddr"[TAB]"netmask"[NEWLINE]
Example:
"212.131.173.0" "255.255.255.0"
allows all hosts of the class 'C' network '212.131.173.XXX' to use the server as relay.
[table index] [configuration] [top]
"username"[TAB]"password"[TAB]"permissions"[NEWLINE]
is used to permit SMTP client authentication with protocols PLAIN, LOGIN, CRAM-MD5 and custom. With custom authentication a file containing all secrets (username + ':' + password) is passed as parameter to the custom authentication program which tests all secrets to find the one matching (if exist). For this reason it's better to keep the number of entries in this file as low as possible. Permissions are a string that can contain:
open mailing features
open relay features (bypass all other relay blocking traps)
VRFY command enabled (bypass SERVER.TAB variable)
ETRN command enabled (bypass SERVER.TAB variable)
disable mail size checking (bypass SERVER.TAB variable)
ease SSL requirement for this user (bypass the "WantTLS" mail config variable)
When PLAIN, LOGIN or CRAM-MD5 authentication mode are used, first a lookup in 'MAILUSERS.TAB' accounts is performed to avoid duplicating information with 'SMTPAUTH.TAB'. Therefore when using these authentication modes a user must use as username the full email address (the : separator is permitted instead of @) and as password his POP3 password. If the lookup succeeds, the 'SERVER.TAB' variable 'DefaultSmtpPerms' is used to assign user SMTP permissions (default MR). If the lookup fails then 'SMTPAUTH.TAB' lookup is done.
[table index] [configuration] [top]
The 'SMTPEXTAUTH.TAB' file enables the XMail administrator to use external authentication methods to verify SMTP clients. If the 'SMTPEXTAUTH.TAB' does not exist, or it is empty, XMail standard authentication methods are used, and those will use either the 'MAILUSERS.TAB' or the 'SMTPAUTH.TAB' to verify account credentials. If the file 'SMTPEXTAUTH.TAB' is not empty, then the XMail standard authentication methods are not advertised in the AUTH response of the EHLO SMTP command. Instead, only the ones listed inside the 'SMTPEXTAUTH.TAB' are reported to the SMTP client. The 'SMTPEXTAUTH.TAB' file can contain multiple lines with the following format:
"auth-name"[TAB]"program-path"[TAB]"arg-or-macro"...[NEWLINE]
This file can contain multiple lines whose 'auth-name' are listed during the EHLO command response. Where 'arg-or-macro' can be (see [MACRO SUBSTITUTION]):
authentication method (PLAIN, LOGIN, CRAM-MD5, ...)
SMTP client supplied username (available in PLAIN, LOGIN and CRAM-MD5)
SMTP client supplied password (available in PLAIN and LOGIN)
challenge used by the server (available in CRAM-MD5)
client response to server challenge (@CHALL - available in CRAM-MD5)
a file path where the external authentication binary might supply extra information/credentials about the account (available in all authentications)
The RFILE file is composed by multiple lines with the following format:
VAR=VALUE
Currently supported variables inside the RFILE file are:
Supply SMTP permissions for the account (see [SMTPAUTH.TAB] for detailed information)
Example:
"PLAIN" "/usr/bin/my-auth" "-a" "@@AUTH" "-u" "@@USER" "-p" "@@PASS" "-r" "@@RFILE"
The external authentication binary may or may not fill a response file. If the authentication has been successful, the binary should exit with a code equal to zero. Any other exit code different from zero, will be interpreted as failure.
[table index] [configuration] [top]
"varname"[TAB]"varvalue"[NEWLINE]
Example:
"RealName" "??" "HomePage" "??" "Address" "??" "Telephone" "??" "MaxMBSize" "10000"
contains user default values for new users that are not set during the new account creation. This file is looked up in two different places, first in '$MAIL_ROOT/domains/DOMAIN' then in '$MAIL_ROOT', where 'DOMAIN' is the name of the domain where we're going to create the new user.
For each 'domain' handled by the server we'll create a directory 'domain' inside $MAIL_ROOT. Inside $MAIL_ROOT/'domain' reside 'domain'->'account' directories ($MAIL_ROOT/'domain'/'account'). This folder contains a sub folder named 'mailbox' (or 'Maildir/(tmp,new,cur)') that stores all 'account' messages. It also contains a file named 'USER.TAB' that stores "account" variables, for example:
"RealName" "Davide Libenzi" "HomePage" "http://www.xmailserver.org/davide.html"; "MaxMBSize" "30000"
[table index] [configuration] [top]
"username"[TAB]"password"[NEWLINE]
This file contains the accounts that are enabled to remote administer XMail. The password is encrypted with the 'XMCrypt' program supplied with the source distro.
'REMEMBER THAT THIS FILE HOLDS ADMIN ACCOUNTS, SO PLEASE CHOOSE COMPLEX USERNAMES AND PASSWORDS AND USE CTRL.IPMAP.TAB TO RESTRICT IP ACCESS! REMEMBER TO REMOVE THE EXAMPLE ACCOUNT FROM THIS FILE!'
[table index] [configuration] [top]
"ipaddr"[TAB]"netmask"[NEWLINE]
or:
"ipaddr"[TAB]"netmask"[TAB]"params"[NEWLINE]
or:
"ipaddr/bits"[NEWLINE]
or:
"ipaddr/bits"[TAB]"params"[NEWLINE]
Example:
"212.131.173.0" "255.255.255.0" "212.131.173.0/24"
registers all hosts of the class 'C' network '212.131.173.XXX' as spammers, and blocks them the use of XMail SMTP server. If a match is found on one of those records, XMail will reject the incoming SMTP connection at an early stage. It is possible to specify optional parameters to tell XMail which behaviour it should assume in case of a match. An example of such a setup is:
"212.131.173.0/24" "code=0"
In this case a code=0 tells XMail to flag the connection as possible spammer, but to await later SMTP session stages to reject the connection itself. In this case an authenticated SMTP session can override the SPAMMERS.TAB match. The optional "params" field lists parameters associated with the record, separated by a comma:
"param1=value1,param2=value2,...,paramN=valueN"
Currently supported parameters are:
Specify the rejection code for the record. If the value is greater than zero, the connection is rejected soon, and the remote SMTP client is disconnected. If the value is zero, the connection is flagged as spammer but awaits later stages for rejection, by allowing authenticated SMTP connections to bypass the SPAMMERS.TAB match. If the value is less than zero, XMail will insert an "absolute value" seconds delay between SMTP commands. Default value for code is greater than zero (immediate rejection).
[table index] [configuration] [top]
"spam-address"[NEWLINE]
Example:
"*@rude.net" "*[email protected]"
blocks mails coming from the entire domain 'rude.net' and coming from all addresses that end with '-admin@'even.more.rude.net.
[table index] [configuration] [top]
"ipaddr"[TAB]"netmask"[TAB]"permission"[TAB]"precedence"[NEWLINE]
This file controls the global IP access permission to the POP3 server if located in the MAIL_ROOT path, and user IP access to its POP3 mailbox if located inside the user directory.
Example:
"0.0.0.0" "0.0.0.0" "DENY" "1" "212.131.173.0" "255.255.255.0" "ALLOW" "2"
This configuration denies access to all IPs except the ones of the class 'C' network '212.131.173.XXX'.
Higher precedences win over lower ones.
[table index] [configuration] [top]
"ipaddr"[TAB]"netmask"[TAB]"permission"[TAB]"precedence"[NEWLINE]
This file controls IP access permission to SMTP server.
Example:
"0.0.0.0" "0.0.0.0" "DENY" "1" "212.131.173.0" "255.255.255.0" "ALLOW" "2"
This configuration denies access to all IPs except the ones of the class 'C' network '212.131.173.XXX'.
Higher precedences win over lower ones.
[table index] [configuration] [top]
"ipaddr"[TAB]"netmask"[TAB]"permission"[TAB]"precedence"[NEWLINE]
This file control IP access permission to CTRL server. Example:
"0.0.0.0" "0.0.0.0" "DENY" "1" "212.131.173.0" "255.255.255.0" "ALLOW" "2"
This configuration deny access to all IPs except the ones of the class 'C' network '212.131.173.XXX'. Higher precedences win over lower ones.
[table index] [configuration] [top]
"ipaddr"[TAB]"netmask"[TAB]"permission"[TAB]"precedence"[NEWLINE]
This file controls IP access permission to FINGER server. Example:
"0.0.0.0" "0.0.0.0" "DENY" "1" "212.131.173.0" "255.255.255.0" "ALLOW" "2"
This configuration denies access to all IPs except the ones of the class 'C' network '212.131.173.XXX'. Higher precedences win over lower ones.
[table index] [configuration] [top]
"variable"[TAB]"value"[NEWLINE]
store user information such as:
"RealName" "Davide Libenzi" "HomePage" "http://www.xmailserver.org/davide.html"; "MaxMBSize" "30000" "ClosedML" "0"
Please refer to USER.TAB variables below.
[table index] [configuration] [top]
If the user is a mailing list this file must exist inside the user account subdirectory and contain a list of users subscribed to this list. The file format is:
"user"[TAB]"perms"[NEWLINE]
where:
subscriber email address.
subscriber permissions:
read.
write (check done using the 'MAIL FROM:<...>' SMTP return path).
write (check done using the email address used for SMTP authentication).
Example:
"[email protected]" "RW" "[email protected]" "R" "[email protected]" "RA"
If the 'USER.TAB' file defines the 'ClosedML' variable as '1' then a client can post to this mailing list only if it's listed in 'MLUSERS.TAB' with RW permissions.
[table index] [configuration] [top]
"command"[TAB]"arg-or-macro"[TAB]...[NEWLINE]
stores commands (internals or externals) that have to be executed on a message file. The presence of this file is optional and if it does not exist the default processing is to store the message in user mailbox. The 'MAILPROC.TAB' file can be either per user or per domain, depending where the file is stored. If stored inside the user directory it applies only to the user whose directory hosts the 'MAILPROC.TAB', while if stored inside the domain directory it applies to all users of such domain. Each argument can be a macro also (see [MACRO SUBSTITUTION]):
is substituted for the sender of the message
is substituted for the recipient of the message
is substituted for the real recipient ($(RCPT) could be an alias) of the message
is substituted for the message file path (the external command _must_ only read the file)
is substituted for the (XMail unique) message id
is substituted for the reference SMTP message id
creates a copy of the message file to a temporary one. It can be used with 'external' command but in this case it's external program responsibility to delete the temporary file. Do not use it with 'filter' commands since the filter will have no way to modify the real spool file
name of the SMTP authenticated user, or "-" if no authentication has been supplied
Supported commands:
[EXTERNAL]
"external"[TAB]"priority"[TAB]"wait-timeout"[TAB]"command-path"[TAB]=> "arg-or-macro"[TAB]...[NEWLINE]
where:
command keyword
process priority: 0 = normal -1 = below normal +1 = above normal
wait timeout for process execution in seconds: 0 = nowait
Be careful if using $(FILE) to give the external command enough timeout to complete, otherwise the file will be removed by XMail while the command is processing. This is because such file is a temporary one that is deleted when XMail exits from 'MAILPROC.TAB' file processing. In case the external command exit code will be '16', the command processing will stop and all the following commands listed inside the file will be skipped.
[FILTER]
"filter"[TAB]"priority"[TAB]"wait-timeout"[TAB]"command-path"[TAB]=> "arg-or-macro"[TAB]...[NEWLINE]
where:
command keyword
process priority: 0 = normal -1 = below normal +1 = above normal
wait timeout for process execution in seconds: 0 = nowait
With filters, it is not suggested to use $(TMPFILE), since the filter will never have the ability to change the message content in that way. Also, to avoid problems very difficult to troubleshoot, it is suggested to give the filter 'ENOUGH' timeout to complete (90 seconds or more). See [MESSAGE FILTERS] for detailed information about return codes. In the filter command, the "Stop Filter Processing" return flag will make XMail to stop the execution of the current custom processing file.
The 'filter' command will pass the message file to a custom external filter, that after inspecting it, has the option to accept, reject or modify it. Care should be taken to properly re-format the message after changing it, to avoid message corruption. The 'filter' command 'CANNOT' successfully change the private XMail's header part of the spool message.
[MAILBOX]
"mailbox"[NEWLINE]
With this command the message is pushed into local user mailbox.
[REDIRECT]
"redirect"[TAB]"domain-or-emailaddress"[TAB]...[NEWLINE]
Redirect message to internal or external domain or email address. If the message was for foo-user@custdomain.net and the file custdomain.net.tab contains a line:
"redirect" "target-domain.org"
the message is delivered to 'foo-user@target-domain.org'.
While the line:
"redirect" "[email protected]"
redirects the message to user@target-domain.org.
[LREDIRECT]
"lredirect"[TAB]"domain-or-emailaddress"[TAB]...[NEWLINE]
Redirect the message to internal or external domain (or email address) impersonating local domain during messages delivery. If the message was for foo-user@custdomain.net and the file custdomain.net.tab contains a line:
"redirect" "target-domain.org"
the message is delivered to 'foo-user@target-domain.org'.
While the line:
"redirect" "[email protected]"
redirects the message to 'user@target-domain.org'. The difference between "redirect" and "lredirect" is the following. Suppose A@B sends a message to C@D, that has a redirect to E@F. With "redirect" E@F will see A@B has sender while with "lredirect" he will see C@D.
[SMTPRELAY]
"smtprelay"[TAB]"server[:port][,options];server[:port][,options];..."[NEWLINE]
Send mail to the specified SMTP server list by trying the first, if fails the second and so on. Otherwise You can use this syntax:
"smtprelay"[TAB]"#server[:port][,options];server[:port][,options];..."[NEWLINE]
to have XMail random-select the order the specified relays. Each gateway definition can also contain options as a comma-separated list (see [SMTP GATEWAY CONFIGURATION] for more information).
[table index] [configuration] [top]
This file lists SMTP properties to be associated with the remote SMTP peer IP. The format of the file is:
"ip-addr"[TAB]"var0=value0"...[TAB]"varN=valueN"[NEWLINE]
Example:
"192.168.0.7/32" "WhiteList=1"
Address selection mask are formed by an IP address (network) plus the number of valid bits inside the network mask. No space are allowed between the variable name and the '=' sign and between the '=' sign and the value. These are the currently defined variables:
If set to 1, all peer IP based checks will be skipped.
If set to 1, drops the TLS requirement for SMTP sessions coming from the matched network.
If set to 0, bypasses the "CheckMailerDomain" 'SERVER.TAB' variable.
If set to 1, release the authentication policy for this IP.
If set to 1, enable VRFY commands from this IP.
If set to 1, enable ETRN commands from this IP.
[table index] [configuration] [top]
This file lists SMTP properties to be associated with the remote SMTP peer host name. The format of the file is:
"host-spec"[TAB]"var0=value0"...[TAB]"varN=valueN"[NEWLINE]
If the "host-spec" starts with a dot ('.'), the properties listed for that record will be applied to all sub-domains of the "host-spec" domain. Since applying the 'SMTP.HNPROP.TAB' rules requires a DNS PTR lookup of the peer IP, you should be aware that this might introduce latencies into the XMail processing. If you do not have any hostname-based rules, do not create the 'SMTP.HNPROP.TAB' file at all, since the simple existence of the file would trigger the DNS PTR lookup. Example:
"xmailserver.org" "WhiteList=1" "EaseTLS=1"
or:
".xmailserver.org" "WhiteList=1" "EaseTLS=1"
See [SMTP.IPPROP.TAB] for information about the properties allowed to be listed in this file.
[table index] [configuration] [top]
See [MESSAGE FILTERS]
[table index] [configuration] [top]
See [MESSAGE FILTERS]
[table index] [configuration] [top]
See [SMTP MESSAGE FILTERS]
[table index] [configuration] [top]
See [SMTP MESSAGE FILTERS]
[table index] [configuration] [top]
See [SMTP MESSAGE FILTERS]
[table index] [configuration] [top]
XMail support two kinds of macro declaration inside its TAB file. The old macro declaration done by prefixing the macro name with the '@@' sequence is still supported for backward compatibility, and has to be used when the macro is the only content of the parameter. Macro can also be declared as '$(MACRO)' and this form can be used anywhere inside the parameter declaration, like:
"/var/spool/mail/$(USER).dat"
[top]
You can use external modules (executables) to perform user authentication instead of using XMail 'mailusers.tab' lookups. Inside the userauth directory you'll find one directory for each service whose authentication can be handled externally (see SMTPEXTAUTH.TAB for SMTP). Suppose We must authenticate 'USERNAME' inside 'DOMAIN', XMail first tries to lookup (inside userauth/pop3) a file named:
'DOMAIN.tab'
else:
'.tab'
If one of these files is found, XMail authenticates 'USERNAME' - 'DOMAIN' using that file. The authentication file is a TAB file (see at the proper section in this document) which has the given structure:
"auth-action"[TAB]"command"[TAB]"arg-or-macro"[TAB]...[NEWLINE]
Each argument can be a macro also (see [MACRO SUBSTITUTION]):
the USERNAME to authenticate
the DOMAIN to authenticate
the user password
user path
The values for 'auth-action' can be one of:
item userauth
executed when user authentication is required
executed when a user need to be added
executed when a user change is required
executed when a user deletion is required
executed when all domain users need to be deleted
The first line that stores the handling command for the requested action is executed as:
command arg0 ... argN
that must return zero if successful. Any other exit code is interpreted as authentication operation failure, that. in 'userauth' case, means such user is not authenticated.
If the execution of the command fails for system reasons (command not found, access denied, etc ...) then the user is not authenticated.
If none of this file's id are found, then usual authentication is performed ('mailusers.tab'). The use of external authentication does not avoid the presence of the user entry in 'mailusers.tab'.
[top]
When a message is to be sent through an SMTP server that requires authentication, XMail provides a way to handle this task by if the 'userauth/smtp' subdirectory is set up properly.
Suppose a mail is to be sent through the SMTP server 'mail.foo.net', this makes XMail to search for a file named (inside userauth/smtp):
'mail.foo.net.tab'
then:
'foo.net.tab'
then:
'net.tab'
If one of these files is found its content is used to authenticate the SMTP client session. The structure of this file, as the extension says, is the TAB one used for most of the configuration files inside XMail. Only the first valid line (uncommented #) is used to choose the authentication method and lines has this format:
"auth-type"[TAB]"param1"...[TAB]"paramN"[NEWLINE]
Valid lines are:
"PLAIN" "username" "password"
or
"LOGIN" "username" "password"
or
"CRAM-MD5" "username" "password"
[top]
If a message that has as target domain of 'sub1.sub2.domain.net' arrives at the XMail server, 'AND' XMail does not have a real domain 'sub1.sub2.domain.net' inside its domain list, XMail decides if this domain gets a custom domain processing by trying to lookup:
sub1.sub2.domain.net.tab .sub2.domain.net.tab .domain.net.tab .net.tab .tab
inside the 'custdomains' directory.
If one of these files is found the incoming mail gets custom domain processing by executing commands that are stored in such a file.
The format is:
"command"[TAB]"arg-or-macro"[TAB]...[NEWLINE]
These tables store commands (internals or externals) that have to be executed on the message file. The presence of one of these files is optional and if none exist the default processing is applied to the message via SMTP.
Each argument can be a macro also (see [MACRO SUBSTITUTION]):
the sender of the message
the target of the message
the message file path (the external command 'must only read' the file)
the (XMail unique) message id
the reference SMTP message id
creates a copy of the message file to a temporary one. It can be used with 'external' command but in this case it's external program's responsibility to delete the temporary file
name of the SMTP authenticated user, or "-" if no authentication has been supplied
Supported commands:
"external"[TAB]"priority"[TAB]"wait-timeout"[TAB]"command-path"[TAB]=> "arg-or-macro"[TAB]...[NEWLINE]
where:
command keyword
process priority: 0 = normal -1 = below normal +1 = above normal
wait timeout for process execution in seconds: 0 = nowait
Be careful if using $(FILE) to give the external command enough timeout to complete, otherwise the file will be removed by XMail while the command is processing. This is because such file is a temporary one that is deleted when XMail exits from file processing. In case the external command exit code will be '16', the command processing will stop and all the following commands listed inside the file will be skipped.
"filter"[TAB]"priority"[TAB]"wait-timeout"[TAB]"command-path"[TAB]=> "arg-or-macro"[TAB]...[NEWLINE]
where:
command keyword
process priority: 0 = normal -1 = below normal +1 = above normal
wait timeout for process execution in seconds: 0 = nowait
With filters, it is not suggested to use $(TMPFILE), since the filter will never have the ability to change the message content in that way. Also, to avoid problems very difficult to troubleshoot, it is suggested to give the filter 'ENOUGH' timeout to complete (90 seconds or more). See [MESSAGE FILTERS] for detailed information about return codes. In the filter command, the "Stop Filter Processing" return flag will make XMail to stop the execution of the current custom processing file.
The 'filter' command will pass the message file to a custom external filter, that after inspecting it, has the option to accept, reject or modify it. Care should be taken to properly re-format the message after changing it, to avoid message corruption. The 'filter' command 'CANNOT' successfully change the private XMail's header part of the spool message.
"redirect"[TAB]"domain-or-emailaddress"[TAB]...[NEWLINE]
Redirect message to internal or external domain or email address. If the message was for foo-user@custdomain.net and the file custdomain.net.tab contains a line:
"redirect" "target-domain.org"
the message is delivered to 'foo-user@target-domain.org'.
While the line:
"redirect" "[email protected]"
redirects the message to user@target-domain.org.
"lredirect"[TAB]"domain-or-emailaddress"[TAB]...[NEWLINE]
Redirect the message to internal or external domain (or email address) impersonating local domain during messages delivery. If the message was for foo-user@custdomain.net and the file custdomain.net.tab contains a line:
"redirect" "target-domain.org"
the message is delivered to 'foo-user@target-domain.org'.
While the line:
"redirect" "[email protected]"
redirects the message to 'user@target-domain.org'. The difference between "redirect" and "lredirect" is the following. Suppose A@B sends a message to C@D, that has a redirect to E@F. With "redirect" E@F will see A@B has sender while with "lredirect" he will see C@D.
"smtprelay"[TAB]"server[:port][,options];server[:port][,options];..."[NEWLINE]
Send mail to the specified SMTP server list by trying the first, if fails the second and so on. Otherwise You can use this syntax:
"smtprelay"[TAB]"#server[:port][,options];server[:port][,options];..."[NEWLINE]
to have XMail random-select the order the specified relays. Each gateway definition can also contain options as a comma-separated list (see [SMTP GATEWAY CONFIGURATION] for more information).
"smtp"[NEWLINE]
Do SMTP delivery.
[top]
CmdAliases implement aliases that are handled only through commands and can be thought of as a user level implementation of custom domain processing commands. The command set is the same of the one that is described above (Custom domain mail processing) and won't be explained again here.
For every handled domain (listed inside 'domains.tab') a directory with the same domain name is created inside the 'cmdaliases' subdirectory. This directory is automatically created and removed when you add/remove domains through the CTRL protocol (or 'CtrlClnt').
When a mail for 'USER@DOMAIN' is received by the server, the domain 'DOMAIN' is to be handled locally, and the standard users/aliases lookup fails, a file named 'USER.tab' is searched inside '$MAIL_ROOT/cmdaliases/DOMAIN'. If such file is found, commands listed inside the file (whose format must follow the one described in the previous section) are executed by the server as a matter of mail message processing. An important thing to remember is that all domain and user names, when applied to the file system, must be lower case.
The use of the command '[SMTP]' must be implemented with great care because it could create mail loops within the server.
[top]
The following variables are for use int the SERVER.TAB configuration file.
Indicate the primary domain for the server.
If set, forces the domain name XMail uses inside the ESMTP greeting used to support CRAM-MD5 ESMTP authentication.
Set the default domain for POP3 client connections.
Set the postmaster address.
The email address that receives notification messages for every message that has had delivery errors. If it is empty (allowed), the notification message is sent to the sender only.
The email address that receives notification for temporary delivery failures. In case it's empty the notification message is sent to the sender only.
A semicolon separated list of SMTP servers XMail 'must' use to send its mails. The definition can also contain options as a comma-separated list (see [SMTP GATEWAY CONFIGURATION] for more information). Example:
"192.168.0.1,NeedTLS=2;192.168.0.2"
This has the precedence over MX records.
If this variable is specified and is not empty, its content is sent as HELO domain. Otherwise the reverse lookup of the local IP is sent as HELO domain. This helps to deal with remote SMTP servers that are set to check the reverse lookup of the incoming IP.
Enable validation of the sender domain ('MAIL FROM:<...@xxx>') by looking up DNS/MX entries.
Indicate if mail has to be removed or stored in 'froz' directory after a failure in delivery or filtering.
Number of lines of the bounced message that have to be listed inside the notify message (lines after the headers section). Default is zero.
Enable/Disable sending the message log file inside the notify message to the sender. Default is off (zero).
List of delivery attempts that require the system to send a notification to the sender (and eventually to 'TempErrorsAdmin'). The list is a comma separated list of numbers (with no extra spaces) as in:
"1,4,9"
Default is empty which means no notification is sent upon a delivery attempt failure.
Enable null sender ('MAIL FROM:<>') messages to be accepted by XMail.
When building bounce messages, use the null SMTP sender ('MAIL FROM:<>') instead of the 'PostMaster' address. This will affect only the SMTP sender, while the message RFC822 headers will still contain the correct From: header.
Set the maximum number of MTA relay steps before to declare the message as looped (default 16).
Set the verbosity of the Received: message headers tag.
Standard (client IP shown , server IP not). Default.
Verbose (client IP shown , server IP shown)
Strict (no IP shown)
Same as 0 but the client IP is not shown if the client authenticate itself.
Same as 1 but the client IP is not shown if the client authenticate itself.
Set the list of headers tags to be used to extract addresses from POP3 fetched messages (POP3LINKS.TAB). This is a comma delimited list (no extra space or TABs must be included inside the list) as in:
"+X-Deliver-To,To,Cc"
Tags preceded by a '+' character make XMail stop scanning when an address is found inside the header tag.
Tags preceded by a '+' character must be listed before other tags.
The string "+X-Deliver-To,To,Cc" is the default if nothing is specified.
Set the maximum number of errors allowed in a single SMTP session. When the maximum number of allowed errors is exceeded, the connection will be automatically dropped. If such variable is not set, or it is set to zero, the maximum number of errors will be unlimited.
Used to set the message that is sent to the SMTP client when the client IP is listed inside the file SPAMMER.TAB.
Used to set the message that is sent to the SMTP client when the client IP is listed inside the file SPAM-ADDRESS.TAB.
Used to set the message that is sent to the SMTP client when the client IP is listed inside one of the "CustMapsList".
Used to set the message that is sent to the SMTP client when the client IP is listed inside the file SMTP.IPMAP.TAB.
Set this to the message that you want to follow the standard SMTP error response sent by XMail, as in (one line, remember the =>):
"Please open http://www.xmailserver.test/smtp_errors.html to get=>
more information about this error"
Please be aware the RFC821 fix the maximum reply line length to 512 bytes.
Set the drop code for IPs blocked by the SMTP.IPMAP.TAB file:
the connection is dropped soon
the connection is kept alive but only authenticated users can send mail
the peer can send messages but a delay of S seconds is introduced between commands
Enable the use of VRFY SMTP command. This flag may be forced by SMTP authentication.
Enable the use of ETRN SMTP command. This flag may be forced by SMTP authentication.
Minimum disk space (in Kb) that is requested before accepting an SMTP connection.
Minimum virtual memory (in Kb) that is requested before accepting an SMTP connection.
Minimum virtual memory (in Kb) that is requested before accepting a POP3 connection.
This defines the email account (MUST be handled locally) that receives all fetched email that XMail has not been able to deliver.
Enable SMTP after POP3 authentication (default on).
Set the maximum message size in Kb that is possible to send through the server.
This list SMTP permissions assigned to users looked up inside MAILUSERS.TAB during SMTP authentication. It also defines the permissions for users authenticated with SMTP after POP3.
This is a list a user can use to set custom maps checking. The list has the given (strict) format:
maps-root:code,maps-root:code...
Where maps-root is the root for the DNS query (i.e. dialups.mail-abuse.org.) and the code can be:
the connection is dropped soon
the connection is kept alive but only authenticated users can send mail
the peer can send messages but a delay of S seconds is introduced between commands
Indicate if XMail must do an RDNS lookup before accepting a incoming SMTP connection. If 0, the check is not performed; if 1 and the check fails, the user receives a 'server use forbidden' at MAIL_FROM time; if -S (S > 0) and the check fails, a delay of S seconds between SMTP commands is used to prevent massive spamming.
SMTP authentication overrides the denial set by this option by giving authenticated users the ability to access the server from 'mapped' IPs.
Setup a list of smart DNS hosts to which are directed DNS queries with recursion bit set to true. Such DNS hosts must support DNS recursion in queries. The format is:
dns.home.bogus.net:tcp,192.168.1.1:udp,...
Enable/disable the emission the the 'X-AuthUser:' mail header for authenticated users. Valid values are "0" or '1', default is "0" (emission enabled).
Sets global SMTP gateway options. Those can be overridden by specific gateway options. See [SMTP GATEWAY CONFIGURATION] for information.
Control if POP3 passwords are logged into the POP3 log file. Set to "0" to disable password logging, set to "1" to enable logging of failed logins, and the to "2" to always enable password logging. Default is "0".
Lists a comma-separated sequence of SMTP authentications that are allowed while the connections is in non-TLS mode (clear text). Do not set this variable if you do not want to impose any restriction, or set it to the empty string if you do not want any authentication method to be allowed in clear-text mode.
Enable CTRL TLS negotiation (default "1").
Enable POP3 TLS (STLS) negotiation (default "1").
Enable SMTP TLS (STARTTLS) negotiation (default "1").
See [SSL CONFIGURATION] for information.
Default SMTP server config loaded if specific server IP[,PORT] config is not found.
Specific IP or IP,PORT SMTP server config. Examples:
"SmtpConfig-192.168.1.123" "..." "SmtpConfig-192.168.1.17,1025" "..."
The variable value is a comma separated sequence of configuration tokens whose meaning is:
authentication required to send mail to the server. Please note that by setting this value everything requires authentication, even for sending to local domains, and this is probably not what you want. The "mail-auth" is also synonym of "MailAuth".
TLS connection needed to talk to this server. This is either done by issuing a STARTTLS command over a standard SMTP session, or by using an SMTPS port
[top]
This feature offers a way to filter messages by providing the ability to execute external programs, such as scripts or real executables. These 'filters' may examine and/or modify messages and inform XMail of their actions with a return value.
This feature offers the ability to inspect and modify messages, giving a way to reject messages based on content, alter messages (address rewriting) and so on.
If this filters returns '4, 5 or 6' the message is rejected and is stopped in its travel. If the filter modifies the message it must return '7'.
Additional flags are allowed to be returned to XMail as a result of filter processing by adding the flags value to the exits code above listed. The currently defined flags are :
Stop selected filter list processing.
Filter flags are additive and if more than one flag need to be specified, their values must be added together. If a filter "raw" exit code is RC and the filter needs to return extra flags FILTER-SUM, the final return code FRC must be :
FRC = RC + FILTER-SUM
Example. Suppose a filter modified the message and hence needs to return 7 as return code. Suppose also that a filter wants to block the filter selection list processing by specifying a flags value of 16, the value to be returned will be :
FRC = 7 + 16 = 23
Filter selection is driven by two files 'FILTERS.IN.TAB' and 'FILTERS.OUT.TAB' located inside the $MAIL_ROOT/ directory and that have the following format:
"sender"[TAB]"recipient"[TAB]"remote-addr"[TAB]"local-addr"[TAB]"filename"[NEWLINE]
For example:
"*@bad-domain.com" "*" "0.0.0.0/0" "0.0.0.0/0" "av-filter.tab" "*" "[email protected]" "0.0.0.0/0" "0.0.0.0/0" "spam-block.tab" "*" "*" "192.168.1.0/24" "0.0.0.0/0" "archive.tab"
where the file "av-filter.tab" must be present inside the $MAIL_ROOT/filters directory. The "sender" and the "recipient" are resolved to the real account when possible. Address selection mask are formed by an IP address (network) plus the number of valid bits inside the network mask. The file 'FILTERS.IN.TAB' lists filters that have to be applied to inbound messages (going to local mailboxes) while the file 'FILTERS.OUT.TAB' lists filters that have to be applied to outbound messages (delivered remotely). All four (sender+recipient+remote-addr+local-addr) selection fields must have a match in order "filename" to be evaluated. The syntax of the filter file is:
"command"[TAB]"arg-or-macro"[TAB]...[NEWLINE]
or:
"!flags"[TAB]"command"[TAB]"arg-or-macro"[TAB]...[NEWLINE]
Each file may contain multiple commands, that will be executed in strictly sequential order. The first command that will trigger a rejection code will make the filtering process to end. The 'flags' parameter is a comma-separated list of flags that drives the filter execution. The syntax of each flag is either FLAG or FLAG=VAL. Currently supported flags are:
exclude filter execution in case of authenticated sender
exclude filter execution in case the client IP is white-listed inside the SMTP.IPPROP.TAB file. This flag works only for SMTP filters.
sets the timeout value for this filter execution
Each argument can be a macro also (see [MACRO SUBSTITUTION]):
the sender of the message
the sender of the message resolved to the real account, when possible (alias resolution)
the target of the message
the target of the message resolved to the real account, when possible (alias resolution)
remote IP address and port of the sender
local IP address and port where the message has been accepted
the message file path (the external command may modify the file if it returns '7' as command exit value.)
with the (XMail unique) message id
the reference SMTP message id
name of the SMTP authenticated user, or "-" if no authentication has been supplied
Here 'command' is the name of an external program that processes the message and returns its processing result. If it returns '6' the message is rejected and a notification message is sent to the sender. By returning '5' the message is rejected without notification. While returning '4' the message is rejected without notification and without being frozen (a '5' response could lead to a frozen message if the SERVER.TAB configuration enables this). If all filters return values different from '6, 5 and 4' the message continues its trip. The filter command may also modify the file (AV scanning, content filter, message rewriting, etc) by returning '7'. The filter 'MUST' return '7' in case it modifies the message. If the filter changes the message file it 'MUST' keep the message structure and it 'MUST' terminate all line with <CR><LF>. The filter has also the ability to return a one-line custom return message by creating a file named $(FILE).rej holding the message in the very first line. This file should be created 'ONLY' when the filter returns a rejection code ('6, 5 and 4')and 'NEVER' in case of passthrough code ('7') or modify code.
The spool files has this structure:
Info Data [ 1th line ] SmtpDomain [ 2nd line ] SmtpMessageID [ 3rd line ] MAIL FROM:<...> [ 4th line ] RCPT TO:<...> [ 5th line ] <<MAIL-DATA>> [ 6th line ] ...
After the '<<MAIL-DATA>>' tag (5th line) the message follows. The message is composed of a headers section and, after the first empty line, the message body. The format of the "Info Data" line is:
[ClientIP]:ClientPort;[ServerIP]:ServerPort;Time
'EXTREME' care must be used when modifying the message because the filter will be working on the real message, and a badly reformatted file will lead to message loss. The spool file header (any data before <<MAIL-DATA>>) 'MUST' be preserved as is by the filter in case of message rewrite happens.
[top]
Besides having the ability to perform off-line message filtering, XMail gives the user the power to run filters during the SMTP session. Three files drive the SMTP on-line filtering, and these are 'FILTERS.POST-RCPT.TAB', 'FILTERS.PRE-DATA.TAB' and 'FILTERS.POST-DATA.TAB'. The file 'FILTERS.POST-RCPT.TAB', contains one or more commands to be executed after the remote SMTP client sends the RCPT_TO command(s), and before XMail sends the response to the command. The file 'FILTERS.PRE-DATA.TAB' contains one or more commands to be executed after the remote SMTP client sends the DATA command, and before XMail sends the response to the command. Using such filters, the user can tell XMail if or if not accept the following transaction and, in case of rejection, the user is also allowed to specify a custom message to be sent to the remote SMTP client. The file 'FILTERS.POST-DATA.TAB' contains one or more commands to be executed after XMail received the whole client DATA, and before XMail sends the final response to the DATA command (final messages ack). The files 'FILTERS.POST-RCPT.TAB', 'FILTERS.PRE-DATA.TAB' and 'FILTERS.POST-DATA.TAB' contains zero or more lines with the following format:
"command"[TAB]"arg-or-macro"[TAB]...[NEWLINE]
or:
"!flags"[TAB]"command"[TAB]"arg-or-macro"[TAB]...[NEWLINE]
Each file may contain multiple commands, that will be executed in strictly sequential order. The first command that will trigger a rejection code will make the filtering process to end. The 'flags' parameter is a comma-separated list of flags that drives the filter execution. The syntax of each flag is either FLAG or FLAG=VAL. Currently supported flags are:
exclude filter execution in case of authenticated sender
exclude filter execution in case the client IP is white-listed inside the SMTP.IPPROP.TAB file.
Each argument can be a macro also (see [MACRO SUBSTITUTION]):
message file path
name of the SMTP authenticated user, or "-" if no authentication has been supplied
remote IP address and port of the sender
local IP address and port where the message has been accepted
message sender address
last recipient submitted by the client. For post-rcpt filters, this will be used as to-validate recipient
last recipient submitted by the client, translated to the real account (in case of aliases)
Filter commands have the ability to inspect and modify the content of the message (or info) file. The exit code of commands executed by XMail are used to tell XMail the action that has to be performed as a consequence of the filter. The exit code is composed by a raw exit code and additional flags. Currently defined flags are:
Stop selected filter list processing.
Currently defined raw exit codes are:
Reject the message.
Any other exit codes will make XMail to accept the message, and can be used also when changing the content of the $(FILE) file. 'EXTREME' care must be used when changing the $(FILE) file, since XMail expect the file format to be correct. Also, it is important to preserve the <CR><LF> line termination of the file itself. When rejecting the message, the filter command has the ability to specify the SMTP status code that XMail will send to the remote SMTP client, by creating a file named $(FILE).rej containing the message in the very first line. Such file will be automatically removed by XMail. The data passed to filter commands inside $(FILE) varies depending if the command is listed inside 'FILTERS.POST-RCPT.TAB', 'FILTERS.PRE-DATA.TAB' or inside 'FILTERS.POST-DATA.TAB'. Commands listed inside 'FILTERS.POST-RCPT.TAB' and 'FILTERS.PRE-DATA.TAB' will receive the following data stored inside $(FILE):
Info Data [ 1th line ]
SmtpDomain [ 2nd line ]
SmtpMessageID [ 3rd line ]
MAIL FROM:<...> [ 4th line ]
RCPT TO:<...> {...} [ 5th line ]
...
The file can have one or more "RCPT TO" lines. The format of the "Info Data" line is:
ClientDomain;[ClientIP]:ClientPort;ServerDomain;[ServerIP]:ServerPort;Time;Logo
Note that in case of 'FILTERS.POST-RCPT.TAB', the $(FILE) data does not yet contain the current recipient to be validated. This needs to be fetched and passed to the external program using the $(CRCPT) macro (or $(RRCPT)). Commands listed inside 'FILTERS.POST-DATA.TAB' will receive the following data stored inside $(FILE):
Info Data [ 1th line ]
SmtpDomain [ 2nd line ]
SmtpMessageID [ 3rd line ]
MAIL FROM:<...> [ 4th line ]
RCPT TO:<...> {...} [ 5th line ]
...
<<MAIL-DATA>>
...
After the '<<MAIL-DATA>>' tag the message follows. The message is composed of a headers section and, after the first empty line, the message body. The format of the RCPT line is:
RCPT TO:<address> {ra=real-address}
where "real-address" is the "address" after it has been translated (if aliases applies) to the real local address. Otherwise it holds the same value of "address". In case one or more SMTP filter operations are not needed, avoid to create zero sized files altogether, since this will result in faster processing.
[top]
The following variables are for use in the USER.TAB configuration file.
Full user name, i.e.:
"RealName" "Davide Libenzi"
User home page, i.e.:
"HomePage" "http://www.xmailserver.org/davide.html";
Max user mailbox size in Kb, i.e.:
"MaxMBSize" "30000"
Specify if the mailing list is closed only to subscribed users, i.e.:
"ClosedML" "1"
Specify the mailing list sender or administrator:
"ListSender" "[email protected]"
This variable should be set to avoid delivery error notifications to reach the original message senders.
User SMTP permissions (see SMTPAUTH.TAB for info).
Set to '1' if the account can receive email, '0' if you want to disable the account from receiving messages.
Set to '1' if you want to enable the account to fetch POP3 messages, '0' otherwise.
Enable/Disable the emission of the Reply-To: header for mailing list's messages (default 1).
Set the maximum message size (in Kb) that the user is able to send through the server. Overrides the SERVER.TAB variable.
Enable/disable the emission the the 'X-AuthUser:' mail header for authenticated users. Valid values are '0' or '1', default is '0' (emission enabled). This variable overrides the SERVER.TAB one when present.
In case of Maildir mailbox structure, scan the "cur" directory during POP3 message list build. Set to "0" to disable "cur" directory scanning, or to "1" to enable it.
[top]
A full implementation of SMTP protocol allows the ability to perform mail routing bypassing DNS MX records by means of setting, in a ruled way, the 'RCPT TO: <>' request. A mail from 'xuser@hostz' directed to '@hosta,@hostb:foouser@hostc' is received by '@hosta' then sent to '@hostb' using 'MAIL FROM: <@hosta:xuser@hostz>' and 'RCPT TO: <@hostb:foouser@hostc>'. The message is then sent to '@'hostc using 'MAIL FROM: <@hostb,@hosta:xuser@hostz>' and 'RCPT TO: <foouser@hostc>'.
[top]
The new spool filesystem tree format has been designed to enable XMail to handle very large queues. Instead of having a single spool directory (like versions older than 0.61) a two layer deep splitting has been introduced so that its structure is:
0 <dir>
0 <dir>
mess <dir>
rsnd <dir>
info <dir>
temp <dir>
slog <dir>
cust <dir>
froz <dir>
...
...
When XMail needs to create a new spool file a spool path is chosen in a random way and a new file with the format:
mstime.tid.seq.hostname
is created inside the 'temp' subdirectory. When the spool file is ready to be committed, it's moved into the 'mess' subdirectory that holds newer spool files. If XMail fails sending a new message (the ones in mess subdirectory) it creates a log file (with the same name of the message file) inside the 'slog' subdirectory and move the file from 'mess' to 'rsnd'. During the message sending the message itself is locked by creating a file inside the 'lock' subdirectory (with the same name of the message file). If the message has permanent delivery errors or is expired and if the option 'RemoveSpoolErrors' of the 'SERVER.TAB' file is off, the message file is moved into the 'froz' subdirectory.
[top]
An SMTP gateway definition inside XMail can be followed by a set of configuration options, that are in the form of a comma-separated VAR=VAL or FLAG definitions. Currently defined options are:
If set to 1, instruct XMail to try to establish a TLS session with the remote host (by the means of a STARTTLS SMTP command). If set to 2, XMail will try to establish a TLS session, but it will fail if not able to do so (the remote server does not support STARTTLS, or reject our attempt to negotiate the TLS link).
Sets the IP address of the network interface that should be used when connecting to the remote host. This configuration should be used carefully, because XMail will fail if the selected IP of the interface does not have a route to the remote host using such IP.
[top]
XMail uses to identify itself during SSL negotiations, by the mean of the two files 'server.cert' and 'server.key'. These files 'MUST' be available inside the 'MAIL_ROOT' directory. Both are in PEM format, and one represent the server certificate file/chain ('server.cert') while the other represent the server private key file ('server.key'). XMail uses the OpenSSL libraries for its SSL operations. http://www.openssl.org/docs/HOWTO/certificates.txt contains examples about how to create certificates to be use by XMail, while http://www.openssl.org/docs/HOWTO/keys.txt describes own to generate keys. In order to properly manage your XMail server when using SSL support, you need to have access to the OpenSSL binary. For Unix ports, this is available as a package, whose name varies depending on the distribution. For Windows, pre-built versions of theOpenSSL libraries and binary are supplied inside the "win32ssl" directory of the XMail source package. For example, to create a self-signed certificate, you first have to create a private key with:
$ openssl genrsa 2048 > server.key
After you have created the private key, you can create you own copy of the self-signed certificate with:
$ openssl req -new -x509 -key server.key -out server.cert
C:> openssl req -new -x509 -key server.key -out server.cert -config openssl.cnf
Remeber that the Common Name (CN) that you supply to the OpenSSL binary, is the fully qualified host name that answers to the IP where your XMail server is listening. If you want to have a certificate signed by an authority, you need to generate a certificate request file:
$ openssl req -new -key server.key -out cert.csr C:> openssl req -new -key server.key -out cert.csr -config openssl.cnf
The 'openssl.cnf' file is supplied inside the Xmail's Windows binary package, and inside the 'win32ssl\conf' directory of the source package. The 'cert.csr' file needs then to be submitted to the certificate authority in order to obtain a root-signed certificate file (that will be your 'server.cert'). The behaviour of the XMail SSL module is controlled by a few 'SERVER.TAB' variables:
Tells the SSL link negotiation code to verify the remote peer certificate. If this is enabled, you need to use either SSLUseCertsFile or SSLUseCertsDir to provide a set of valid root certificates. You can also add your own certificates in the set, in order to provide access to your servers by clients using certificates signed by you.
Tells the SSL link negotiation code to fail if the remote peer does not supply a certificate.
Allows self-signed certificates supplied by remote peers.
Set the maximum certificate chain depth for the verification process.
When using SSLWantVerify, the SSL code will verify the peer certificate using standard SSL certificate chain verification rules. It is possible to supply to XMail an extra list of valid certificates, by filling up a 'CERTS.PEM' file and setting SSLUseCertsFile to 1. The 'CERTS.PEM' is a concatenation of certificates in PEM format.
In the same way as SSLUseCertsFile does, setting SSLUseCertsDir to 1 enables the usage of extra valid certificates stored inside the 'CERTS' XMail sub-directory. The 'CERTS' contains hashed file names that are created by feeding the directory path to the 'c_rehash' OpenSSL Perl script (a Windows-friendly version of 'c_rehash', named 'c_rehash.pl' is contained inside the 'win32ssl\bin' subdirectory of the source package). Unix users will find proper CA certificates inside the standard install paths of OpenSSL, while Windows users will find them inside the 'win32ssl\certs' subdirectory of the source package. To use 'c_rehash' you need to have the OpenSSL binaries (executable and shared libraries) correctly installed in your system, and the executable reachable from your PATH. Then you simply run it by passing the path to the PEM certificates directory ('CERTS'). The 'c_rehash' script will call the OpenSSL binary and will generated hashed file names (that are either symlinks or copies) that point/replicate the mapped certificate.
[top]
These are commands understood by ESMTP server:
[top]
These are commands understood by POP3 server:
[top]
Most of XMail configuration settings are command line tunables. These are command line switches organized by server.
Mail root path (also settable with MAIL_ROOT environment).
Activate debug (verbose) mode.
Set log rotate hours step.
Set the queue split level. The value you set here is rounded to the lower prime number higher or equal than the value you've set.
Set the size of the socket's receive buffer in bytes (rounded up to 1024).
Set the size of the socket's send buffer in bytes (rounded up to 1024).
Setup XMail to use 'Maildir' delivery (default on Unix).
Setup XMail to use 'mailbox' delivery (default on Windows).
Set the number of subdirectories allocated for the DNS cache files storage ( default 101 ).
Use only IPV4 records for host name lookups (default).
Use only IPV6 records for host name lookups.
Use IPV4 records if present, or IPV6 records otherwise, for host name lookups.
Use IPV6 records if present, or IPV4 records otherwise, for host name lookups.
Disable the service.
Bind to IPV6 address (in case no -PI option is specified)
Set POP3 server port (if you change this you must know what you're doing).
Set POP3 session timeout (seconds) after which the server closes. the connection if it does not receive any commands.
Enable POP3 logging.
Set the delay timeout in response to a bad POP3 login. Such time is doubled at the next bad login.
Hang the connection in bad login response.
Bind server to the specified ip address and (optional) port (can be multiple).
Set the maximum number of threads for POP3 server.
Disable the service.
Bind to IPV6 address (in case no -BI option is specified)
Set POP3S server port (if you change this you must know what you're doing).
Bind server to the specified ip address and (optional) port (can be multiple).
Disable the service.
Bind to IPV6 address (in case no -SI option is specified)
Set SMTP server port (if you change this you must know what you're doing).
Set SMTP session timeout (seconds) after which the server closes the connection if no commands are received.
Enable SMTP logging.
Bind server to the specified ip address and (optional) port (can be multiple).
Set the maximum number of threads for SMTP server.
Set the maximum number of recipients for a single SMTP message (default 100).
Set the expire timeout for a POP3 authentication IP (default 900).
Disable the service.
Bind to IPV6 address (in case no -XI option is specified)
Set SMTPS server port (if you change this you must know what you're doing).
Bind server to the specified ip address and (optional) port (can be multiple).
Set the number of mailer threads.
Set the time to be wait for a next try after send failure. Default 480.
Set the increment ratio of the reschedule time in sending a messages. At every failure in delivery a message, reschedule time T is incremented by (T / ratio), therefore :
T(i) = T(i-1) + T(i-1)/ratio.
If you set this ratio to zero, T remain unchanged over delivery tentatives. Default 16.
Set the maximum number of times to try to send the message. Default 32.
Enable SMAIL logging.
Timeout value for filters commands in seconds. Default 90.
Enable filter logging.
Disable the service.
Set external POP3 accounts sync interval. Setting this to zero will disable the PSYNC task. Default 120.
Set the number of POP3 sync threads.
Sets the timeout for POP3 client connections.
Enable PSYNC logging.
Disable the service.
Bind to IPV6 address (in case no -FI option is specified)
Set FINGER server port (if you change this you must know what you're doing).
Enable FINGER logging.
Bind server to the specified ip address and (optional) port (can be multiple).
Disable the service.
Bind to IPV6 address (in case no -CI option is specified)
Set CTRL server port (if you change this you must know what you're doing).
Set CTRL session timeout (seconds) after which the server closes the connection if no commands are received.
Enable CTRL logging.
Bind server to the specified ip address and (optional) port (can be multiple).
Set the maximum number of threads for CTRL server.
Disable the service.
Bind to IPV6 address (in case no -WI option is specified)
Set CTRLS server port.
Bind server to the specified ip address and (optional) port (can be multiple).
Set the number of local mailer threads.
Set the sleep timeout for LMAIL threads (in seconds, default 2).
Enable local mail logging.
[top]
It's possible to remote admin XMail due to the existence of a 'controller server' that runs with XMail and waits for TCP/IP connections on a port (6017 or tunable via a '-Cp nport') command line option.
Admin protocol details:
The XMail admin server 'speaks' a given protocol that can be used by external GUI utilities written with the more disparate scripting languages, to remote administer the mail server. The protocol is based on sending formatted command and waiting for formatted server responses and error codes. All the lines, commands, and responses are delimited by a <CR><LF> pair. The error code string (I'll call it RESSTRING) has the given format:
"+DDDDD OK"<CR><LF>
if the command execution is successful while:
"-DDDDD ErrorString"<CR><LF>
if the command failed.
The " character is not included in responses. DDDDD is a numeric error code while ErrorString is a description of the error. If DDDDD equals 00100, a lines list, terminated by a line with a single point (<CR><LF>.<CR><LF>), follows the response.
The input format for commands is similar to the one used in TAB files:
"cmdstring"[TAB]"param1"[TAB]..."paramN"<CR><LF>
where 'cmdstring' is the command string identifying the action to be performed, and param1,... are the parameters of the command.
Immediately after the connection with XMail controller server is established the client receives a RESSTRING that is:
+00000 <TimeStamp> XMail ...
if the server is ready, while:
-DDDDD ...
(where DDDDDD is an error code) if not.
The TimeStamp string has the format:
currtime.pid@ipaddress
and is used in MD5 authentication procedure.
As the first action immediately after the connection the client must send an authentication string with this format:
"user"[TAB]"password"<CR><LF>
where user must be enabled to remote admin XMail. Clear text authentication should not be used due server security. Using MD5 authentication instead, the client must perform an MD5 checksum on the string composed by (<> included):
<TimeStamp>password
and then send to the server:
"user"[TAB]"#md5chksum"<CR><LF>
where md5chksum is the MD5 checksum (note '#' as first char of sent digest). The result of the authentication send is a RESSTRING. If the user does not receive a positive authentication response, the connection is closed by the server. It is possible to establish an SSL session with the server by issuing the "#!TLS" string as login string. In response to that, the server will send back a RESSTRING. In case of success RESSTRING, the client can proceed with the SSL link negotiation with the server.
[admin protocol] [top]
"useradd"[TAB]"domain"[TAB]"username"[TAB]"password"[TAB]"usertype"<CR><LF>
where:
domain name (must be handled by the server).
username to add.
user password.
'U' for normal user and 'M' for mailing list.
The result is a RESSTRING.
[admin protocol] [top]
"userdel"[TAB]"domain"[TAB]"username"<CR><LF>
where:
domain name (must be handled by the server).
username to delete.
The result is a RESSTRING.
[admin protocol] [top]
"userpasswd"[TAB]"domain"[TAB]"username"[TAB]"password"<CR><LF>
where:
domain name (must be handled by the server).
username (must exist).
new password.
The result is a RESSTRING.
[admin protocol] [top]
"userauth"[TAB]"domain"[TAB]"username"[TAB]"password"<CR><LF>
where:
domain name.
username.
password.
The result is a RESSTRING.
[admin protocol] [top]
"userstat"[TAB]"domain"[TAB]"username"<CR><LF>
where:
domain name.
username/alias.
The result is a RESSTRING. If successful (00100), a formatted matching users list follows terminated by a line containing a single dot (<CR><LF>.<CR><LF>). This is the format of the listing:
"variable"[TAB]"value"<CR><LF>
Where valid variables are:
real address (maybe different is the supplied username is an alias).
total size of the mailbox in bytes.
total number of messages.
last user login IP address.
time of the last login.
[admin protocol] [top]
"aliasadd"[TAB]"domain"[TAB]"alias"[TAB]"account"<CR><LF>
where:
domain name (must be handled by the server).
alias to add.
real email account (locally handled). This can be a fully qualified email address or a username inside the same domain.
The result is a RESSTRING.
[admin protocol] [top]
"aliasdel"[TAB]"domain"[TAB]"alias"<CR><LF>
where:
domain name (must be handled by the server).
alias to delete.
The result is a RESSTRING.
[admin protocol] [top]
"aliaslist"[TAB]"domain"[TAB]"alias"[TAB]"account"<CR><LF>
or
"aliaslist"[TAB]"domain"[TAB]"alias"<CR><LF>
or
"aliaslist"[TAB]"domain"<CR><LF>
or
"aliaslist"<CR><LF>
where:
domain name, optional (can contain wild cards).
alias name, optional (can contain wildcards).
account, optional (can contain wildcards).
Example:
"aliaslist"[TAB]"foo.bar"[TAB]"*"[TAB]"mickey"<CR><LF>
lists all aliases of user 'mickey' in domain 'foo.bar'.
The result is a RESSTRING. In successful cases (00100) a formatted matching users list follows, terminated by a line containing a single dot (<CR><LF>.<CR><LF>). This is the format of the listing:
"domain"[TAB]"alias"[TAB]"username"<CR><LF>
[admin protocol] [top]
"exaliasadd"[TAB]"local-address"[TAB]"remote-address"<CR><LF>
where:
local email address.
remote email address.
For example, the following command string:
"exaliasadd"[TAB]"[email protected]"[TAB]"[email protected]"<CR><LF>
will link the external email address 'dlibenzi@xmailserver.org' with the local email address 'dlibenzi@home.bogus'. The result is a RESSTRING.
[admin protocol] [top]
"exaliasdel"[TAB]"remote-address"<CR><LF>
where:
remote email address.
The result is a RESSTRING.
[admin protocol] [top]
"exaliaslist"[TAB]"local-address"[TAB]"remote-address"<CR><LF>
or
"exaliaslist"[TAB]"local-address"<CR><LF>
or
"exaliaslist"<CR><LF>
where:
local email address. This can contain wildcard characters.
remote email address. This can contain wildcard characters.
Example:
"exaliaslist"[TAB]"*@home.bogus"<CR><LF>
lists all the external aliases linked to local accounts in domain 'home.bogus'.
The result is a RESSTRING. In successful cases (00100) a formatted matching users list follows, terminated by a line containing a single dot (<CR><LF>.<CR><LF>). This is the format of the listing:
"rmt-domain"[TAB]"rmt-name"[TAB]"loc-domain"[TAB]"loc-name"<CR><LF>
[admin protocol] [top]
"uservars"[TAB]"domain"[TAB]"username"<CR><LF>
where:
domain name.
username.
The result is a RESSTRING. In successfully cases (00100) a formatted list of user vars follow, terminated by a line containing a single dot (<CR><LF>.<CR><LF>). This is the format of the listing:
"varname"[TAB]"varvalue"<CR><LF>
[admin protocol] [top]
"uservarsset"[TAB]"domain"[TAB]"username"[TAB]"varname"[TAB]"varvalue" ... <CR><LF>
where:
domain name.
username.
variable name.
variable value.
There can be multiple variable assignments with a single call. If 'varvalue' is the string '.|rm' the variable 'varname' is deleted. The result is a RESSTRING.
[admin protocol] [top]
"userlist"[TAB]"domain"[TAB]"username"<CR><LF>
or
"userlist"[TAB]"domain"<CR><LF>
or
"userlist"<CR><LF>
where:
domain name, optional (can contain wild cards).
username, optional (can contain wild cards).
Example:
"userlist"[TAB]"spacejam.foo"[TAB]"*admin"<CR><LF>
lists all users of domain 'spacejam.foo' that end with the word 'admin'.
The result are a RESSTRING. If successful (00100), a formatted matching users list follows terminated by a line containing a single dot (<CR><LF>.<CR><LF>). This is the format of the listing:
"domain"[TAB]"username"[TAB]"password"[TAB]"usertype"<CR><LF>
[admin protocol] [top]
"usergetmproc"[TAB]"domain"[TAB]"username"<CR><LF> or
"usergetmproc"[TAB]"domain"[TAB]"username"[TAB]"flags"<CR><LF>
where:
domain name.
username.
flags specifying which mailproc to retrieve. Use 'U' for user mailproc, or 'D' for domain mailproc (or 'DU' for a merge of both). If not specified, 'DU' is assumed.
Example:
"usergetmproc"[TAB]"spacejam.foo"[TAB]"admin"<CR><LF>
gets mailproc.tab file for user 'admin' in domain 'spacejam.foo'.
The result is a RESSTRING. In successful cases (00100) the mailproc.tab file is listed line by line, terminated by a line containing a single dot (<CR><LF>.<CR><LF>).
[admin protocol] [top]
"usersetmproc"[TAB]"domain"[TAB]"username"<CR><LF> or
"usersetmproc"[TAB]"domain"[TAB]"username"[TAB]"which"<CR><LF>
where:
domain name.
username.
which mailproc.tab should be set. Use 'U' for the user one, and 'D' for the domain one. If not specified, 'U' is assumed.
Example:
"usersetmproc"[TAB]"spacejam.foo"[TAB]"admin"<CR><LF>
sets mailproc.tab file for user 'admin' in domain 'spacejam.foo'.
The result is a RESSTRING. If successful (00101), the client must list the mailproc.tab file line by line, ending with a line containing a single dot (<CR><LF>.<CR><LF>). If a line of the file begins with a dot, another dot must be added at the beginning of the line. If the file has zero length the mailproc.tab is deleted. The client then gets another RESSTRING indicating the final command result.
[admin protocol] [top]
"mluseradd"[TAB]"domain"[TAB]"mlusername"[TAB]"mailaddress"[TAB]"perms"<CR><LF>
or
"mluseradd"[TAB]"domain"[TAB]"mlusername"[TAB]"mailaddress"<CR><LF>
where:
domain name (must be handled by the server).
mailing list username.
mail address to add to the mailing list 'mlusername@domain'.
user permissions (R or RW or RA). When 'perms' is not specified the default is RW.
The result is a RESSTRING.
[admin protocol] [top]
"mluserdel"[TAB]"domain"[TAB]"mlusername"[TAB]"mailaddress"<CR><LF>
where:
domain name (must be handled by the server).
mailing list username.
mail address to delete from the mailing list 'mlusername@domain'.
The result is a RESSTRING.
[admin protocol] [top]
"mluserlist"[TAB]"domain"[TAB]"mlusername"<CR><LF>
where:
domain name (must be handled by the server).
mailing list username.
The result is a RESSTRING. If successful (00100), a formatted list of mailing list users follows terminated by a line containing a single dot (<CR><LF>.<CR><LF>).
[admin protocol] [top]
"domainadd"[TAB]"domain"<CR><LF>
where:
domain name to add.
The result is a RESSTRING.
[admin protocol] [top]
"domaindel"[TAB]"domain"<CR><LF>
where:
domain name to delete.
The result is a RESSTRING. This is not always a safe operation.
[admin protocol] [top]
"domainlist"<CR><LF>
or:
"domainlist"[TAB]"wildmatch0"[TAB]...[TAB]"wildmatchN"<CR><LF>
The result is a RESSTRING. The wild match versions simply returns a filtered list of domains. If successful (00100), a formatted list of handled domains follows, terminated by a line containing a single dot (<CR><LF>.<CR><LF>).
[admin protocol] [top]
"aliasdomainadd"[TAB]"realdomain"[TAB]"aliasdomain"<CR><LF>
Example:
"aliasdomainadd"[TAB]"xmailserver.org"[TAB]"xmailserver.com"<CR><LF>
defines 'xmailserver.com' as an alias of 'xmailserver.org', or:
"aliasdomainadd"[TAB]"xmailserver.org"[TAB]"*.xmailserver.org"<CR><LF>
defines all subdomains of 'xmailserver.org' as aliases of 'xmailserver.org'.
[admin protocol] [top]
"aliasdomaindel"[TAB]"aliasdomain"<CR><LF>
Example:
"aliasdomaindel"[TAB]"*.xmailserver.org"<CR><LF>
removes the '*.xmailserver.org' domain alias.
[admin protocol] [top]
"aliasdomainlist"<CR><LF>
or:
"aliasdomainlist"[TAB]"wild-dom-match"<CR><LF>
or:
"aliasdomainlist"[TAB]"wild-dom-match"[TAB]"wild-adom-match"<CR><LF>
The result is a RESSTRING. The wild match version simply returns a filtered list of alias domains. If successful (00100), a formatted list of alias domains follows, terminated by a line containing a single dot (<CR><LF>.<CR><LF>). The output format is:
"real-domain"[TAB]"alias-domain"<CR><LF>
[admin protocol] [top]
"custdomget"[TAB]"domain"<CR><LF>
where:
domain name.
Example:
"custdomget"[TAB]"spacejam.foo"<CR><LF>
gets the custom domain file for domain 'spacejam.foo'.
The result is a RESSTRING. If successful (00100), the custom domain file is listed line by line terminated by a line containing a single dot (<CR><LF>.<CR><LF>).
[admin protocol] [top]
"custdomset"[TAB]"domain"<CR><LF>
where:
domain name.
Example:
"custdomset"[TAB]"spacejam.foo"<CR><LF>
sets custom domain file for domain 'spacejam.foo'.
The result is a RESSTRING. If successful (00101), the client must list the custom domain file line by line, ending with a line containing a single dot (<CR><LF>.<CR><LF>). If a line of the file begins with a dot, another dot must be added at the begin of the line. If the file has zero length the custom domain file is deleted. The client then gets another RESSTRING indicating the final command result.
[admin protocol] [top]
"custdomlist"<CR><LF>
The result is a RESSTRING. If successful (00100), a formatted list of custom domains follows, terminated by a line containing a single dot (<CR><LF>.<CR><LF>).
[admin protocol] [top]
"poplnkadd"[TAB]"loc-domain"[TAB]"loc-username"[TAB]"extrn-domain"=> [TAB]"extrn-username"[TAB]"extrn-password"[TAB]"authtype"<CR><LF>
where:
local domain name (must be handled by the server).
local username which receives mails.
external domain.
external username.
external user password.
authentication method (see [POP3LINKS.TAB]).
The remote server must support 'APOP' authentication to specify APOP as authtype. Using APOP authentication is more secure because clear usernames and passwords do not travel on the network; if you're not sure about it, specify 'CLR' as authtype.
The result is a RESSTRING.
[admin protocol] [top]
"poplnkdel"[TAB]"loc-domain"[TAB]"loc-username"[TAB]"extrn-domain"=> [TAB]"extrn-username"<CR><LF>
where:
local domain name (must be handled by the server).
local username which receives mails.
external domain.
external username.
The result is a RESSTRING.
[admin protocol] [top]
"poplnklist"[TAB]"loc-domain"[TAB]"loc-username"<CR><LF>
or
"poplnklist"[TAB]"loc-domain"<CR><LF>
or
"poplnklist"<CR><LF>
The result is a RESSTRING. If successful (00100), a formatted list of handled domains follows, terminated by a line containing a single dot (<CR><LF>.<CR><LF>). The format of the listing is:
"loc-domain"[TAB]"loc-username"[TAB]"extrn-domain"[TAB]"extrn-username"=> [TAB]"extrn-password"[TAB]"authtype"[TAB]"on-off"<CR><LF>
[admin protocol] [top]
"poplnkenable"[TAB]"enable"[TAB]"loc-domain"[TAB]"loc-username"=> [TAB]"extrn-domain"[TAB]"extrn-username"<CR><LF>
or
"poplnkenable"[TAB]"enable"[TAB]"loc-domain"[TAB]"loc-username"<CR><LF>
where:
1 for enabling - 0 for disabling.
local domain name.
local username which receives mails.
external domain.
external username.
In the second format all users, links are affected by the enable operation.
The result is a RESSTRING.
[admin protocol] [top]
"filelist"[TAB]"relative-dir-path"[TAB]"match-string"<CR><LF>
where:
path relative to MAIL_ROOT path.
wild card match string for file list selection.
The result is a RESSTRING. If successful (00100), the directory is listed line by line, terminated by a line containing a single dot (<CR><LF>.<CR><LF>). The listing format is:
"filename"[TAB]"filesize"<CR><LF>
[admin protocol] [top]
"cfgfileget"[TAB]"relative-file-path"<CR><LF>
where:
path relative to MAIL_ROOT path.
Example:
"cfgfileget"[TAB]"ctrlaccounts.tab"<CR><LF>
The result is a RESSTRING. If successful (00100), the file is listed line by line, terminated by a line containing a single dot (<CR><LF>.<CR><LF>). You CANNOT use this command with indexed files !
[admin protocol] [top]
"cfgfileset"[TAB]"relative-file-path"<CR><LF>
where:
path relative to MAIL_ROOT path.
Example:
"cfgfileset"[TAB]"ctrlaccounts.tab"<CR><LF>
The result is a RESSTRING. IF successful (00101), the client must list the configuration file line by line, ending with a line containing a single dot (<CR><LF>.<CR><LF>). If a line of the file begins with a dot, another dot must be added at the beginning of the line. If the file has zero length the configuration file is deleted. The client then gets another RESSTRING indicating the final command result. Remember that configuration files have a strict syntax and that pushing a incorrect one can make XMail not work properly. You CANNOT use this command with indexed files!
[admin protocol] [top]
"frozlist"<CR><LF>
The result is a RESSTRING. If successful (00100), a formatted list of frozen messages follows, terminated by a line containing a single dot (<CR><LF>.<CR><LF>). The format of the listing is:
"msgfile"[tab]"lev0"[TAB]"lev1"[TAB]"from"[TAB]"to"[TAB]"time"[TAB]"size"<CR><LF>
Where:
message name or id.
queue fs level 0 (first level directory index).
queue fs level 1 (second level directory index).
message sender.
message destination.
message time ("YYYY-MM-DD HH:MM:SS").
message size in bytes.
[admin protocol] [top]
"frozsubmit"[TAB]"lev0"[TAB]"lev1"[TAB]"msgfile"<CR><LF>
where:
message name or id.
queue fs level 0 (first level directory index).
queue fs level 1 (second level directory index).
You can get this information from the frozlist command. After a message has been successfully rescheduled it is deleted from the frozen fs path. The result is a RESSTRING.
[admin protocol] [top]
"frozdel"[TAB]"lev0"[TAB]"lev1"[TAB]"msgfile"<CR><LF>
where:
message name or id.
queue fs level 0 (first level directory index).
queue fs level 1 (second level directory index).
You can get this information from the frozlist command. The result is a RESSTRING.
[admin protocol] [top]
"frozgetlog"[TAB]"lev0"[TAB]"lev1"[TAB]"msgfile"<CR><LF>
where:
message name or id.
queue fs level 0 (first level directory index).
queue fs level 1 (second level directory index).
You can get this information from the frozlist command. The result is a RESSTRING. If successful (00100), the frozen message log file follows, terminated by a line containing a single dot (<CR><LF>.<CR><LF>).
[admin protocol] [top]
"frozgetmsg"[TAB]"lev0"[TAB]"lev1"[TAB]"msgfile"<CR><LF>
where:
message name or id.
queue fs level 0 (first level directory index).
queue fs level 1 (second level directory index).
You can get this information from the frozlist command. The result is a RESSTRING. If successful (00100), the frozen message file follows, terminated by a line containing a single dot (<CR><LF>.<CR><LF>).
[admin protocol] [top]
"etrn"[TAB]"email-match0"...<CR><LF>
where:
wild card email matching for destination address.
Example:
"etrn" "*@*.mydomain.com" "your-domain.org"
starts queueing all messages with a matching destination address.
[admin protocol] [top]
"noop"<CR><LF>
The result is a RESSTRING.
[admin protocol] [top]
"quit"<CR><LF>
The result is a RESSTRING.
[admin protocol] [top]
Do you want to build GUI configuration tools using common scripting languages (Java, TCL/Tk, etc) and XMail controller protocol? Do you want to build Web configuration tools? Please let me know <[email protected]>.
[admin protocol] [top]
XMail has the ability to deliver locally prepared mail files that if finds in the 'spool/local' directory. The format of these files is strict:
mail from:<...>[CR][LF] rcpt to:<...>[CR][LF] ... [CR][LF] message text in RFC822 format with [CR][LF] line termination
All lines must be [CR][LF] terminated, with one mail-from statement, one or more rcpt-to statements, an empty line and the message text. Mail files must not be created directly inside the '/spool/local' directory but instead inside '/spool/temp' directory. When the file is prepared it has to be moved into '/spool/local'. The file name format is:
stime-seqnr.pid.hostname
where:
system time in sec from 01/01/1970.
sequence number for the current file.
process or thread id.
creator process host name.
Example:
97456928-001.7892.home.bogus
XMail has a number of LMAIL threads that periodically scan the '/spool/local' directory watching for locally generated mail files. You can tune this number of threads with the '-Ln nthreads' command line option. The suggested number ranges from three to seven.
[top]
You can use CtrlClnt to send administration commands to XMail. These commands are defined in the previous section (XMAIL ADMIN PROTOCOL). The syntax of CtrlClnt is:
CtrlClnt [-snuptfSLcKCXHD] ...
where:
set server address.
set server port [6017].
set username.
set password.
set timeout [60].
set dump filename [stdout].
enable SSL link negotiation (talks to a CTRL port)
use native SSL link (talks to a CTRLS port)
set the SSL private key file (the environment variable "CTRL_KEY_FILE" also sets it)
set the SSL certificate file (the environment variable "CTRL_CERT_FILE" also sets it)
set the SSL certificate-list file (the environment variable "CTRL_CA_FILE" also sets it). See [SSL CONFIGURATION] for more information
set the SSL certificate-store directory (the environment variable "CTRL_CA_PATH" also sets it). See [SSL CONFIGURATION] for more information
enable debug output
With the command and parameters that follow adhering to the command syntax, i.e.:
CtrlClnt -s mail.foo.org -u davide.libenzi -p ciao=> useradd home.bogus foouser foopasswd U
executes the command useradd with parameters 'home.bogus foouser foopasswd U'.
CtrlClnt returns 0 if the command is successful and != 0 if not. If the command is a query, then the result is printed to stdout.
[top]
Under Linux, XMail creates a file named XMail.pid in '/var/run' that contains the PID of the main XMail thread. By issuing a:
kill -INT `cat /var/run/XMail.pid`
a system administrator can initiate the shutdown process (this can take several seconds). You can use the supplied 'xmail' startup script to start / stop / restart XMail:
xmail start / stop / restart
Under NT console service (XMail --debug ...) you can hit Ctrl-C to initiate the shutdown process.
Using [Control Panel]->[Services] you can start and stop XMail as you wish.
XMail detects a shutdown condition by checking the presence of a file named '.shutdown' in its main directory (MAIL_ROOT). You can initiate XMail shutdown process by creating (or copying) a file with that name into MAIL_ROOT.
[top]
This command line utility enables you to create the user accounts structure by giving it a formatted list of users parameters (or a formatted text file). The syntax of the list (or file) is:
domain;username;password;real-name;homepage[NEWLINE]
where a line whose first character is '#' is treated as a comment. This utility can also be used to create a random number users (useful for me to test server performance).
These are MkUsers command line parameters:
number of users to create in auto-mode.
domain name in auto-mode.
input file name {stdin}.
radix user name in auto-mode.
mail root path {./}.
mailbox maximum size {10000}.
base user id {1};
create Maildir boxes.
show this message.
MkUsers creates, under the specified root directory, the given structure:
rootdir <dir>
mailusers.tab <file>
domains <dir>
domainXXX <dir>
userXXX <dir>
user.tab <file>
mailbox <dir>
...
...
for the mailbox structure, while:
rootdir <dir>
mailusers.tab <file>
domains <dir>
domainXXX <dir>
userXXX <dir>
user.tab <file>
Maildir <dir>
tmp <dir>
new <dir>
cur <dir>
...
...
for the Maildir structure.
If the file 'mailusers.tab' already exist in the mail root path, MkUsers exits without overwriting the existing copy. This protect you from accidentally overwriting your file when playing inside the real MAIL_ROOT directory. If you want to setup the root directory (-r ...) as MAIL_ROOT, you must delete by hand the existing file (you must know what you're doing). If you setup the root directory (-r ...) as MAIL_ROOT you MUST have XMail stopped before running MkUsers. Existing files and directories are not overwritten by MkUsers so you can keep your users db in the formatted text file (or generate it by a database dump for example) and run MkUsers to create the structure. Remember that you have to add new domains in the 'domains.tab' file by hand. MkUsers is intended as a bulk-mode utility, not to create single user; for this CtrlClnt (or other GUI/Web configuration utilities) is better suited.
[top]
When building XMail, an executable called 'sendmail' is created. This is a replacement of the sendmail program used mostly on Unix systems; it uses the local mail delivery of XMail to send email generated onto the server machine. These sendmail options are supported (other options are simply ignored):
Set the sender of the email.
Set the extended sender of the email.
Extract recipients from the 'To:'/'Cc:'/'Bcc:' header tags.
Read the input until the End Of Stream, instead of stopping at the "\n.\n" sequence.
The syntax is:
sendmail [-t] [-f...] [-F...] [--input-file fname] [--xinput-file fname]=> [--rcpt-file fname] [--] recipient ...
The message content is read from the standard input and must be RFC compliant.
The following parameters are XMail extensions meant to be used with mailing lists managers (using sendmail as a mail list exploder):
take the message from the specified file instead from stdin (RFC format).
take the message from the specified file instead from stdin (XMail format).
add recipients listed inside the specified file (list exploder).
To be RFC compliant means that the message MUST have the format:
[Headers] NewLine Body
Suppose you have your message in the file 'msg.txt', you're 'xmailuser@smartdomain', and you want to send the message to 'user1@dom1' and 'user2@dom2'. The syntax is:
sendmail -fxmailuser@smartdomain user1@dom1 user2@dom2 < msg.txt
or
sendmail -fxmailuser@smartdomain --input-file msg.txt user1@dom1 user2@dom2
[top]
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'. XMail 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:
[email protected] ==> [email protected]
and not:
[email protected] ==> foo
This enables XMail to handle multiple domains in cases where more nic-names are mapped over a single IP address.
To run finger queries you must specify:
[email protected]@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.
Important!
'REMEMBER TO REMOVE THE EXAMPLE ACCOUNT FROM CTRLACCOUNTS.TAB FILE!'
Use ctrl.ipmap.tab to restrict CTRL server access.
Use a long password (mixed upper/lower case with digits) for ctrlaccounts.tab.
The main cause of bugs with XMail 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>.
If you get a bind error in Linux,you must comment pop3, smtp and finger entries in your /etc/inetd.conf.
Remember to compile the file CTRL.IPMAP.TAB to restrict the access to the IPs you use to remote administer XMail server.
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'.
If you have enabled logging, remember to setup the '-Mr hours' option depending on the traffic you get in your server. This avoids XMail having to work with very large log files and can improve server performance.
If you are unable to start XMail (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 XMail errors and errors in this document. If you successfully build and run XMail please let me know at [email protected], I don't want money ;)
[top]
My mother Adelisa, for giving me the light.
My cat Grace, for her patience waiting for food while I'm coding.
All of the free source community, for giving me code and knowledge.
[top]