Scope of sendersBefore CodeTwo Exchange Rules PRO processes the message and performs any actions, it checks the defined conditions. If the message meets the defined conditions, then it is processed. If not, the rule will not apply and no action will be taken. Apart from the condition it is possible to define exceptions. If the defined exception is met then the rule will not be applied. One of the available exceptions checks the scope of senders. To define the Scope of senders on the Exceptions tab click Add and choose Scope of senders (Fig.1.).
|Fig.1. Choosing Scope of senders in the Exceptions tab.|
The Scope of senders will be added to the list of exceptions in the middle pane, while the right pane will show the exception properties (Fig.2.). Click Add in the properties pane to define the senders. The following options are available to define the scope of senders: e-mail address, Active Directory group and users, organizational unit, internal and external users to the organization, unknown address and disabled users in Active Directory (Fig.3.).
|Fig.2. Scope of senders on the list of exceptions.||Fig.3. List of available elements options to define Scope of senders.|
By default the program will skip the message and will not apply the rule if any of the exceptions are met (there is a logical OR relationship between the exceptions). In the example below the rule will not be applied if the user is the Administrator (Fig.4.) or the message type is: new mail message or reply/forward (Fig.5.) i.e. the message must meet Exception #1 or Exception #2 for the rule to be skipped and not be applied.
|Fig.4. Exception #1: the user can be the Administrator.||Fig.5. Exception #2: message type can be: new, reply or forward.|
You can change the logic of exceptions to check when you click on the word ANY. The word ANY will be replaced by ALL, which means that the rule will not be applied only if all of the exceptions are met (there is a logical AND relationship between the exceptions). In the example below the rule will not be applied only when the user is the Administrator (Fig.6.) and the message type is: new mail message or reply/forward message (Fig.7.) i.e. the message must meet both Exception #1 and Exception #2 for the rule to be skipped and not be applied.
|Fig.6. Exception #1: the user is the Administrator.||Fig.7. Exception #2: message type is: new, reply or forward.|
Below you can learn about all available options to define the Scope of senders:
If you want to define senders' addresses for the program to check in order to exclude any messages, you need to choose Add, and then select E-mail (Fig.8.). In the new window (Fig.9.) you can a single email address or if you want to define multiple addresses type in the e-mail addresses separated by semi-colon, or domain address with an asterisks (*) to include multiple addresses from the same domain.
|Fig.8. Choosing e-mail address for the scope of senders.||Fig.9. Defining the sender's e-mail address.|
Active Directory Group
If you want to define a group of senders from the Active Directory you need to choose Add (Fig.10.), and then Active Directory Group. In the new window (Fig.11.), you can search for the desired group of senders (in this example it is the group of Administrators).
|Fig.10. Choosing group in Active Directory.||Fig.11. Searching and defining group in Active Directory.|
Active Directory Properties Filter
Another useful option is the properties filter in Active Directory. If you want to use this option choose Add, and then Active Directory Properties Filter (Fig.12.). In the new window you can define various fields. In this example below the exception is: if the AD field Country equals USA then the rule will not be applied (Fig.13.). Additionally you may check whether one of the exceptions above is met or all exceptions are met from the properties' filter list.
|Fig.12. Choosing properties filter in w Active Directory.||Fig.13. Properties filter window in Active Directory.|
Active Directory User
You can also search for a specific user in Active Directory. In order to do it, you need to choose Add, and then select Active Directory User (Fig.14 & 15.).
|Fig.14. Choosing an option to search for a user in Active Directory.||Fig.15. Searching specified user in Active Directory.|
If you want to define an Organizational Unit for the scope of senders you need to choose Add, and then select Organizational Unit (Fig.16 & 17.).
|Fig.16. Choosing option to search for Organizational Unit.||Fig.17. Window to search for Organizational Unit.|
It is also possible to use all internal users as the scope of senders for the exception. To use this option you need to choose Add, and then select Internal User (Fig.18 & 19.). This element doesn't have any additional options, it is only displayed on the exceptions' list (Fig.19.).
|Fig.18. Choosing the option for internal users.||Fig.19. The rule will not be applied for internal users.|
Similarly, you can define the external users. To set it up, choose Add, and then select External User (Fig.20.).
|Fig.20. Choosing the option for external users.||Fig.21. The rule will not be applied for external users.|
Another option is an exception for users with unknown address. You can activate it when you choose Add, and then select Unknown address (Fig.22 & 23.).
|Fig.22. Choosing the exception for the unknown address.||Fig.23. The rule will not be applied for the unknown address.|
Disabled in AD
The last element for the scope of senders exception is for the disabled users in Active Directory. If you want to use it, you need to choose Add, and then select Disabled in AD (Fig.24 & 25.).
|Fig.24. Choosing the exception for the disabled user in Active Directory.||Fig.25. The rule will not be applied for the disabled user in Active Directory.|