Email rules in CodeTwo Exchange Rules Pro are based on conditions. Conditions are user-specified criteria that your message needs to meet in order for the software to trigger a rule (and apply a corresponding action). If a message does not meet any conditions, no actions are applied and the message reaches the recipient unaltered. Conditions are configured and processed by the program independently for each rule. In this article you can learn more about:

Conditions vs. exceptions

Conditions allow you to decide when a specific rule should be applied. In a similar way, exceptions let you specify when a rule should not be applied. The principles of defining conditions and exceptions are the same. In fact, each type of condition can also be defined as an exception to an email rule. See this article to learn more about exceptions.

How to define conditions

Conditions are specified on the Conditions tab of a rule (Fig. 1.). You can configure one or more conditions by adding them via the Add (+) button. Use the Remove (Exchange Rules Pro remove button 11px) button to remove them at any point.


By default, if you leave the list of conditions empty, the rule applies to all messages processed by the server. The program will remind you about this fact and ask you to confirm when you save your rule via the Submit changes (ESIG for O365 rule save) button.

The Conditions tab with all available conditions.
Fig. 1. The Conditions tab with all available conditions.

Conditions are based on four components:

  • And/Or – in this column, you can define the logical relationships between individual conditions.
  • Field – this is where you choose the type of condition.
  • Operator – this field depends on the condition type you selected and defines how the condition is executed. The execution method can only be set to true.
  • Value – this field also depends on the condition type and is used to specify the actual or expected value of the condition. This value triggers (activates) the associated email rule.

If you created multiple conditions for a rule (Fig. 2.), you need to bind them by using appropriate logical relationships in the And/Or field. This allows you to decide how the software should process these conditions:

  • if you want your rule to be applied only to messages that meet all of the specified conditions at the same time, use the And logical operator to connect these conditions;
  • if you want the rule to apply to messages that meet at least one of the specified conditions, use the Or operator to create connections between these conditions.

Conditions bound with And/Or relationships.
Fig. 2. Conditions bound with And/Or relationships.

You can mix the And and Or operators to connect your conditions. Note that a particular logical operator always applies to the condition defined in the line above. To help you understand how multiple conditions will be executed, the logical relationship between them is shown at the bottom of the RULE PROPERTIES pane (see Fig. 2.). To create more complex arrangements, you can group and nest conditions via the Group(ER Pro 2.x - conditions grouping button) button. Visit this article to learn more about the logical operators and grouping of multiple conditions, and see examples.

The available conditions

Click the links below or use the navigation menu to learn more about the conditions (and exceptions) available in CodeTwo Exchange Rules Pro.

See next

How to group conditions - this article describes how connect conditions together and create logical And/Or relationships between groups or individual conditions within groups.

See also

Exceptions - this article describes the configuration of exceptions, which exclude messages from being processed by the program.
Actions - this article provides information on the actions that can be performed by the program on messages.

In this article

Was this information useful?