Use this form to create a rule for handling mail when one of the following trigger events occurs:
• the mail is received by this container
• you send mail
This only affects the copies of the sent mail left in your Mailbox (local copies).
• you want to run rules manually on selected messages
• the mail is deleted by a user.
Name
The name of the rule.
Enabled
Makes the rule run each time the trigger event occurs.
When
The trigger event that will cause this rule to run. Item Deleted runs the rule when a user deletes mail. Run Manually runs the rule when you select mail, then choose Message > Run Manual Rules.
If
Choose All if all of your conditions must match before action will be taken. Choose Any if any one of your conditions must match before action will be taken (this can result in the rule running more frequently).
Build your conditions just as you would for a basic receive or send rule. If you want multiple conditions, click + to add another row. Clicking - deletes the selected row.
See our help on the receive and send rule forms for explanations of some conditions. The following are advanced rule terms and conditions that may not be self explanatory:
• current user
Means the user who is activating this rule.
• history contains
Choose any action or a specific action. You can also specify a user or leave the user field blank for any user.
• Internet header
Choose a standard Internet header or an Internet header generated by FirstClass (X-), for which your administrator sets the possible values. X-SPAM-Warning and X-SPAM-Level both indicate the probability of this being spam, the first as an alphanumeric expression, such as LOW, and the second as a number, where the higher the number, the more likely this is to be spam. X-SPAM-Tests are the tests that resulted in this message being marked as spam. X-RBL-Warning means the message was sent by a known spammer as reported by a Realtime Blackhole List (RBL). You must know the possible values for the header you choose.
 TipWe recommend you use a receive rule, choosing the spam level condition, instead of the advanced rule's X-SPAM-Warning condition. FirstClass can process the spam level condition more efficiently.
• leaf
Means any object that isn't a container.
• system notice
Means a FirstClass-generated object, such as an NDN.
• when the odds are.
This condition is considered to be met based on the probability you specify. For example, if the odds are 1 in 2, there is a 50% chance that this condition will be considered to be met. If this is the only condition, it means there is a 50% chance that this rule's actions will run.
Then
Build your actions just as you would for a basic receive or send rule. If you want multiple actions, click + to add another row. Clicking - deletes the selected row.
See our help on the receive and send rule forms for explanations of some actions. The following are advanced rule actions that may not be self explanatory:
• Generate reply with attachment name
The reply message will be based on the object attached to this rule.
• Generate reply with fixed text
Type the reply message in the next field.
• Generate reply with preferences autoreply text
The reply message will use the autoreply text from your preferences.
• Make a rule log entry
Adds an entry to your Rules Log, using the text you specify in the next field.
• Send a notification
The specified user must have notification activated, or be running the FirstClass Notifier component that shipped with earlier versions of FirstClass.
• Send a pager message
Your paging preferences will be used to create a forwarded or redirected message.
• Stop rule processing
Put this action at the end of the rule's actions if you have other rules below this one in the container's rules list, and you don't want those rules to process objects that meet this rule's conditions.
• Suppress FC notifier
Turns off FirstClass notification for this mail.
• Turn approval.
Turning approval on means that the object requires approval.
For the Item Deleted trigger, the actions are performed before the actual delete, so that you can cancel the delete, move the object to a folder, and so on, instead of deleting it. If you don't want to delete the object, add the action Cancel deletion after any other actions this rule will perform.
 ExceptionIf you move an object to a subcontainer, FirstClass automatically cancels the deletion.
Attachment
An attachment can be used as the basis for certain actions. For example, a reply with attachment uses the text, formatting, embedded pictures, and so on, of the attached object (typically a message or document). If you want to include an uploaded file, first attach it to the object, then attach the object to the rule.
|