XMail 1.14 Pre 01 is out!, Download and test it ...

[hschneider]

QUOTE

************************************************************     *   WARNING                                                                                               *  If you're upgrading an existing version of XMail it's                     *  strongly suggested that you read all the ChangeLog.txt                     *  notes that range from existing version to the new one.                             ************************************************************ This is a pre01 version of 1.14 with the new filter architecture ( among other things ) : http://www.xmailserver.org/xmail-1.14-pre01.tar.gz http://www.xmailserver.org/xmail-1.14-pre0...01.win32bin.zip Please refer to the included documentation for more info, and report me feedback about it. It's running pretty fine on my server. - Davide No biggie, but in the Win32 binary, filters.out.tab was inadvertently named "Copy of filters.out.tab". - Rolf Woops, damn cut&paste Such file MUST be renamed in "filters.in.tab". Without the new two ( even empty ) files : filters.in.tab filters.out.tab Otherwise XMail won't work. - Davide

[hschneider]

QUOTE

CHANGE LOG  January 25, 2003 v 1.14    *   'ATTENTION': The filter architecture has been completely changed. To        correctly update to this version you have to create two empty files        "filters.in.tab" and "filters.out.tab" inside the $MAIL_ROOT        directory. Please refer to the documentation for more informations        about the new filter architecture. If you are not currently using        filters, the simple creation of the two files listed above will be        sufficent.    *   'ATTENTION': The internal spool file format is changed with the new        line added ( the 1st one ) that contain various message        informations. Filters that rely on the internal spool file format        must be changed to match the new structure.    *   Fixed a bug that made XMail to not correctly report zero sized files        inside the mailbox.    *   Added file size to CTRL's "filelist" command.    *   Fixed a connect-error reporting bug on Windows platform.

[hschneider]

QUOTE

MESSAGE FILTERS    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 '97, 98 or 99' the message is rejected and is    stopped in its travel. If the filter modifies the message it must return    '100'.    Filter selection is driven by two files 'FILTERS.IN.TAB' and    'FILTERS.OUT.TAB' 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"     "*" "clean@purified.net" "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]    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. Each argument can    be a macro also:    @@FROM        the sender of the message    @@RFROM        the sender of the message resolved to the real account, when        possible (alias resolution)    @@RCPT        the target of the message    @@RRCPT        the target of the message resolved to the real account, when        possible (alias resolution)    @@REMOTEADDR        remote IP address and port of the sender    @@LOCALADDR        local IP address and port where the message has been accepted    @@FILE        the message file path (the external command may modify the file if        it returns '100' as command exit value.)    @@MSGID        with the (XMail unique) message id    @@MSGREF        the reference SMTP message id    Here 'command' is the name of an external program that processes the    message and returns its processing result. If it returns '99' the    message is rejected and a notification message is sent to the sender. By    returning '98' the message is rejected without notification. While    returning '97' the message is rejected without notification and without    being frozen (a '98' response could lead to a frozen message if the the    section on "SERVER.TAB" configuration enables this). If all filters    return values different from '99, 98 and 97' the message continues its    trip. The filter command may also modify the file (AV scanning, content    filter, message rewriting, etc) by returning '100'. The filter 'MUST'    return '100' 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 .    The spool files has this structure:     Info Data           [ 1th line ]     SmtpDomain          [ 2nd line ]     SmtpMessageID       [ 3rd line ]     MAIL FROM:<...>     [ 4th line ]     RCPT TO:<...>       [ 5th line ]     <>       [ 6th line ]     ...    After the '<>' tag (5th line) the message follows. The    message is composed of a headers section and, after the first empty    line, the message body. '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.

[hschneider]

And finally you might need this one:

http://www.ralphb.net/IPSubnet/cidr.html

... which explains that special "192.168.1.0/24" notation (=CLIDR notation)

When dealing with IP addressing in filters, Xmail Queue Manager is very helpful. It displays the new INFO DATA in the spoolfile header, that tells you from which IP the message came and where it goes to. E.g.

CODE

192.168.0.1:4699;192.168.0.1:25;Sat, 15 Feb 2003 08:57:19 +0100 tbird S31CFA Mail from: <maildiag@marketmix.com> RCPT TO:<test@marketmix.co> <<MAIL-DATA>>

This one was sent from an application at port 4699 of 192.168.0.1.
Xmail tried to send it through port 25 (=SMTP) if interface 192.168.0.1
So this is an outgoing message.

XQM is still compatible to the new spoolfile format.