|Each e-mail address (or macro) configured under your account is associated
with a list of
instructions, determining the way incoming e-mail is processed.
Instructions can have associated
conditionals. For example, you can instruct messages that have been determined to be spam,
to be discarded or delivered to a specific mailbox folder.
Note that if using multiple instructions with conditionals, and more than
one conditional evaluates to true, only the first instruction in the list
will be executed, without any further processing.
The table below summarizes the different types of mail delivery instructions
that are supported by our mail system:
|mailbox-name||E-mail is delivered to the named mailbox account (as configured previously
mail mbox add, see
MAILBOXES section for details).
|firstname.lastname@example.org||E-mail is forwarded to the given e-mail address, which may be either
locally-hosted or external to the server.
To prevent blacklisting due to spam, if the target address is hosted with
a provider that enforces site-wide spam filtering, it is recommended that
you pre-filter the mail for spam, by using at least a "spam<=5.0" conditional.
|./path/to/file||Messages are written to the given file, in standard "flat-mailbox" format.
|./path/to/directory/||Messages are written to the given
maildir directory structure.
|¯o-name||Messages are further processed by the specified "mail macro".
Mail macros are treated just like ordinary e-mail addresses, with their own
list of delivery instructions (use
mail rule add to create a new macro).
||program args||The given program is executed on the server and contents of the incoming
e-mails is piped to its standard input.
Do not use this feature unless you are familiar with
Ux .The standard
maildrop filters are available on the server, for users who are familiar with them.
Note that our mail system will always insert a
X-Csoft-Pipe header in mail delivered this way, so that loops may be detected.
When using the more advanced
mail rule add command over
mail alias add, conditionals may be specified.
The table below summarizes the different conditionals supported by our
|any||Always evaluate to true.
|spam||Always evaluate to true, but check for spam and insert SpamAssassin headers
into the message.
|spam<=>n||Spam threshold is less than (spam<=n), or greater than (spam>=n) the specified
score (note that behavior if score is exactly n is not important: if using
multiple rules and score is exactly n, only the first rule will be processed).
When using the default SpamAssassin configuration, a score around 5.0
is possibly spam and 7.0 is very likely spam.
|size<=>n||The message body is less than or greater than the given size in bytes.
The "K" and "M" suffixes are recognized.
|email@example.com||Sender envelope address matches this value.
|client_address=18.104.22.168||Numerical IP address of the sender matches this value.