Advanced Rule (web version)

Use this form to create a rule for handling mail when it is received, sent, or deleted, or the rule is run manually.

Name	The name you want to give this rule.
When	The trigger event that will cause this rule to run:
	Message Received	Runs the rule when mail is received by this container.
	Message Sent	Runs the rule when you send mail. This only affects the copies of the sent mail left in your Mailbox (local copies).
	Item Deleted	Runs the rule when a user deletes mail.
	Run Manually	Runs the rule when you select mail, then click Run Manual Rules.
Enabled	Makes the rule run each time the trigger event occurs.
Add to toolbar	Adds this rule to the toolbar, so you can run the rule on selected mail. Caution If you add a rule to a toolbar, you can only remove it using the FirstClass client.
Conditions (If)	All	All of your conditions must match before action will be taken.
	Any	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, fill in the new row that is displayed as you build your current condition. To delete a condition, click the Delete icon beside it. 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	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	Indicates the probability of this being spam as an alphanumeric expression, such as LOW. Tip We recommend you use a receive rule, choosing the spam level condition, instead of X-SPAM-Warning. FirstClass can process the spam level condition more efficiently.
		X-SPAM-Level	Indicates the probability of this being spam as a number. The higher the number, the more likely this is to be spam.
		X-SPAM-Tests	The tests that resulted in this message being marked as spam.
		X-RBL-Warning	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.
	leaf	Any object that isn't a container.
	system notice	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.
Actions (Then)	Build your actions just as you would for a basic receive or send rule. If you want multiple actions, fill in the new row that is displayed as you build your current action. To delete an action, click the Delete icon beside it. 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. You will only see an attachment name in this field after you have attached an object.
	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 rule log entry	Adds an entry to your Rules Log, using the text you specify in the next field.
	Send notification	The specified user must have client notification activated, or be running the FirstClass Notifier component that shipped with earlier versions of the FirstClass client.
	Send 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. This isn't required for deletions, because they automatically stop rule processing.
	Suppress FC notifier	Turns off FirstClass client notification for this mail.
	Turn approval	Turning approval on means that the object requires approval.
Attachments	Only applies to Message Received and Run Manually triggers. 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 a message or document, then attach the message or document to the rule. Attach an object just as you would to a message. After you have attached the object, you can choose it at the appropriate field.

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 do not want to delete the object, add the action Cancel deletion after any other actions this rule will perform.

Exception

If you move an object to a subcontainer, FirstClass automatically cancels the deletion.

For more information

Creating rules for automatic mail handling