The action
The action executes and alters Internet Services processing, once an RFC-2822 header has matched a rule and the tests have been done. There are three actions a rule can do:
• alter the message that arrives
• reject the message altogether
• change the behavior of the rules system.
Actions that alter the delivered message
There are four actions that can alter the delivered message:
• SPAM
This action marks the message as Junk and sets the bit indicating it was a machine generated message.
• DISCARDHEADER
This action discards the current header. The header will not appear if you choose View > Show Internet Headers.
• INJECT
This action injects an RFC-2822 header into the message as delivered in FirstClass. The header will appear if you choose View > Show Internet Headers.
• REPLACE
This action replaces an RFC-2822 header in the message as delivered in FirstClass. The header will appear if you choose View > Show Internet Headers.
Actions that reject the message
There are two actions that can reject the message:
• DISCARDMESSAGE
This action generates the NDN message 552 Delivery Failed.
To silently absorb a message without delivering it to the recipients use SET$lsSpammer = 1. This will not generate an NDN.
• NDN
This action generates an SMTP error causing the sending server to NDN the message.
Actions that affect rules processing
There are two actions that affect rules processing:
• SET
This action sets variables for processing by later rules.
• DONE
This action stops any further processing of rules for this message.
Let's take a look at some examples of actions in mail rules:
Example
# set the icon of a message in the low spam range
# admin settable variables are defined here
: IF ($LowSpamMin <= $spamlevel && $spamlevel <= $LowSpamMax) INJECT "X-FC-Icon-ID: 23050"
This rule states, after all headers have been processed, if the $spamlevel variable is in the LOW range then add an X-FC-Icon-ID header, which sets the icon in FirstClass.
Note
There are many X-FC headers that affect message attributes, such as formID, IconID, and forms data. These can be seen when Internet Services renders a message sent out through SMTP mail.
Example
^: IF (1) SET $CrosspostLimit=$Form.Config.2606.Number AND $CrosspostIncr=5 AND $XpostSpamLevel=20 AND $XpostSpamIncrVal=5
This rule states, before any headers are processed, ^ sets a variety of variables that affect later processing. You can change the values to make this rule behave differently.
Example:
Subject:IF (@inblocklist($subject)) DISCARDMESSAGE
If you treat the subject block list as bad words, this rule would discard inappropriate content without sending NDNs. This rule states, when the Subject header arrives check if any of the text is in the subject block list and, if so, quietly discard the message.
| 
