Userguide
Table of Contents
Go to the Program Website
Specifying Recipients’ Scope
While creating or editing a rule, you can specify the recipients' scope for whom this rule will apply when messages are sent (Fig.1). You also can add exceptions to the recipients’ scope for whom the rule will never apply.

The scope of recipients for whom the rule will apply.
Fig.1. The scope of recipients for whom the rule will apply.

In the upper field, add scope(s) of recipients for whom the footers will be attached. The bottom field includes exceptions to the scope of recipients, for whom the footer will not work.

Criteria for recipients.
Fig.2. Criteria for recipients.


E-mail address
The recipients can be specified by adding full or partial e-mail addresses (Fig.2). While adding senders’ addresses you can use one or several asterisk signs (*), which substitute any string of characters. For instance, by adding support*@*co.uk you decide to apply the rule for all addresses starting with support, from domains ending in co.uk. In the bottom field of Recipients’ scope dialog box, you can define exceptions to the list of e-mail addresses.

Specifying addresses or parts of addresses of senders.
Fig.3. Specifying addresses or parts of addresses of senders.


If you want the rule to apply to messages sent from the main domain and not from its subdomains, include this domain in the list using the @(at) sign: *@company.com.

The possible application of the above-mentioned criteria can be exemplified by the following rule:
The scope of recipients include:
  • domain: *company.com
  • addresses: info@codetwo.com and it_*@codetwo.com

    The exceptions include:
  • subdomain: *support.company.com
  • addresses: it@company.com and it_john@codetwo.com

    With such settings in action the rule will apply to all messages:
  • sent to company.com domain and all its subdomains excluding support.company.com and it@company.com
  • sent to info@codetwo.com
  • sent to users of codetwo.com domain, whose addresses start with it_, excluding it_john@codetwo.com.

  • To apply the rule to all messages, regardless of the address they are sent to, in the upper field of the recipients’ scope dialog box enter the asterisk (*) only or leave it empty.

    Organizational Unit
    You specify one or more organizational units of Active Directory (i.e. containers) the recipients must belong to (Fig.4). Organizational units can also be added the exceptions in the lower field of the recipients' scope dialog box.

    Specifying organizational units in recipients’ scope.
    Fig.4. Specifying organizational units in recipients’ scope.


    Active Directory User
    You can add recipients by specifying particular Active Directory objects (Fig.5). You can also add an addressee to the exceptions list in the bottom field of the Recipients’ Scope if you do not want to apply the rule to this addressee.

    Specifying Active Directory users in the recipients’ scope.
    Fig.5. Specifying Active Directory users in the senders’ scope.


    Active Directory Group
    You specify one or several Active Directory groups in the recipients’ scope (Fig.6). The rule will no apply if the recipient belongs to the Active Directory group entered in the exceptions list.

    Specifying Active Directory Group the recipient must belong to.
    Fig.6. Specifying Active Directory Group the recipients must belong to.


    Active Directory Filter
    You specify the properties necessary for Active Directory User Object representing the message recipient (Fig.7). For instance, you can set the rule to apply if the City variable of the recipient meets certain value or contains selected text. The filter can work according to one of the two principles: "one of the conditions is met" or "all conditions are met".

    In the example from Figure 7 the rule will apply to all recipients for whom the City variable equals New York or includes NY. The condition will be met for recipients whose City value is for example: New York, NY – Manhattan, NY – Brooklyn, but it will not be met for example for recipients from Los Angeles.

    Specifying Active Directory properties that the recipients must meet.
    Fig.7. Specifying Active Directory properties that the recipients must meet.


    In a similar way we can define which attributes an Active Directory user object that represents the recipient of the message must have for the rule not to be applied. You specify the appropriate Active Directory field filter in the lower field of the Recipients' scope.

    External recipients
    This is used to add to the scope of recipients all external users (Fig. 8). Adding this condition will make the rule apply to messages sent to external recipients.

    Specifying the external recipient of the message.
    Fig.8. Specifying the external recipient of the message.

    If this condition is used in the lower (exceptions) field of the recipients' scope, the rule will not apply for messages sent to external recipients.

    Internal recipients
    This is used to add to the scope of recipients all internal users (Fig.9). Adding this condition will make the rule apply to messages sent to internal recipients.

    Specifying the internal recipient of the message.
    Fig.9. Specifying the internal recipient of the message.

    If this condition is used in the lower (exceptions) field of the recipients' scope, the rule will not apply for messages sent to internal recipients.

    General principles

    If you want the rule to apply to internal messages only, add to the list of conditions Internal recipients or add to the exceptions field External recipients.

    If a message has more than one recipient, the rule will not apply if at least one of the recipients is included in the list of exceptions for this rule. If none of the recipients is on the list of exceptions, the rule will apply if at least one of them is in the list of accepted recipients. This process is due to the fact that the program checks the list exceptions first, and next goes on to check the list of accepted recipients.