The Rules Evaluation tab in Log Details displays details for each signature, such as whether the signature was successfully applied to the given email address, whether it was sent internally or externally, and so on.
This process involves each signature to go through a series of rules and is displayed in the Rules Evaluation tab. You will notice that the information for each log type is slightly different, as displayed in the Rules Evaluation tab.
This article contains the following sections:
For a better understanding of the different rules, for example purposes, we will go through the different rules applied to a server-side subscription:
1. The processed signatures are displayed in order of processing (from top left to bottom right in the ‘Signatures’ screen including folders).
2. By default, only signatures that will be applied are expanded, and the screen is scrolled down to the first signature that will be applied.
3. If all signatures have the 'Process Next Signature' enabled, then all available signatures will be evaluated, and the details of the rules for each signature will be displayed. Alternatively, if the last applied signature has the option 'Process Next Signature' set to OFF, then the processing will stop at that point, and the rules following it will not be displayed.
The following screenshot displays the different rules applied:
- Any sender rule: Implies the rules to set users/groups to the signature. For more information, see how you can apply a signature to users and/or groups in Exclaimer Cloud.
- All message rules: Implies the rules to deploy the signature to the users. You can either deploy it via server-side or client-side.
This also contains the subject rules; for more information, see how you can use the subject line trigger rules to apply a signature.
Server-side signatures imply that the signatures are applied after the message has been sent. For more information, see How to apply a server-side signature.
Client-side signatures imply that the user can see the signature whilst composing messages in Microsoft 365 (Outlook and Apple Mail) or Google Workspace (Gmail). For more information, see How to apply a client-side signature.
- All recipient rules: Implies the rules set to apply signature only when emailing specific recipients. For more information, see What are recipient rules?
Processing order of rules
The following screenshot displays the processing order of the rules applied:
The rules are processed in the following order:
|Product Type||This rule checks what is configured: server-side or client-side. In this example, 'server-side' is configured.|
|Recipient is||This rule checks if the recipient is 'internal' or 'external'.|
|Sender is||This rule checks all the senders specified in the email. The list of senders can be a combination of rules, such as individual users, groups, advanced queries, and so on.|
This rule checks all the recipient rules defined.
Inclusion rules implies 'Any recipient is'. This can be a combination of individual recipients and domain rules.
Exclusion rules implies 'Except where any recipient is'. This can be a combination of individual recipients and domain rules. During the evaluation process, if any query matches the exclusion rule, then the signature will fail.
This rule checks the date-time settings for the required signature. For more information, see how you can apply a signature for a specified time period.
This rule checks if there are any messages set to exclude signatures in certain scenarios. The rules set in the body are always last to be evaluated.
For more information, see how you can exclude a signature from being applied based on message body text.
When you go through the log you can, at a glance, see the status of the different rules applied, whether they have been successful or not.
The following is a compiled list of all possible states that are displayed at the signature level:
|Pass||This means that the rule has passed (or cleared) and if all rules pass whether the signature has been applied or not.|
|Fail||This means that the signature has not been applied or the rule has failed.|
|Disabled||This means that the rule was not checked because it was not enabled.|
|N/A (Not evaluated)||This is when a condition does not need to be evaluated because the state of the rule can already be determined.|