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

Senders' scope for whom the rule will apply.
Fig.1. Senders' scope for whom the rule will apply.

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

The scope of senders can be defined using several criteria (Fig.2). The same criteria can be used in the excpetions field.
Criteria for adding senders.
Fig.2. Criteria for adding senders.


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

While configuring the program, you can decide whether the rule will apply only for the main SMTP address, or also for the remaining ones, the so-called proxy or alias addresses.

Example:
You want the "Test" rule to apply to all senders whose domain is support.company.com. A user has the main SMTP address tester@company.com, and an additional address tester@support.company.com. If While matching the rule, use only the main SMTP address of the user in Active Directory option is checked, the "Test" rule will not apply to messages sent by this user since the main address tester@company.com does not match the senders' scope defined for this rule, i.e. support.company.com. If, however, the above option is unchecked, the rule will apply for this user since one of the additional addresses tester@support.company.com matches the senders' scope defined for the rule.

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


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

Specifying organizational units in senders' scope.
Fig.4. Specifying organizational units in senders' scope.


Active Directory User
You can add senders by specifying particular Active Directory objects (Fig.5). You can also add a user to the exceptions list in the bottom field of the Senders' Scope if you do not want to apply the rule to this user.

Specifying Active Directory users in the senders' scope.
Fig.5. Specifying Active Directory users in the senders' scope.


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

Specifying Active Directory Group the sender must belong to.
Fig.6. Specifying Active Directory Group the sender must belong to.


Active Directory Filter
You specify the properties necessary for Active Directory User Object representing the message sender (Fig.7). For instance, you can set the rule to apply if the City variable of the sender 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 senders for whom the City variable equals New York or includes NY. The condition will be met for senders whose City value is for example: New York NY, Manhattan, NY Brooklyn, but it will not be met for example for senders from Los Angeles.

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


In a similar way we can define which attributes an Active Directory user object that represents the sender 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 Senders' scope.

General principles

You can specify multiple addresses in the fields of individual criteria, separating them with semicolons.

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 with the @ (at) sign: *@company.com.

Example:
We have created a rule with the following scope of senders:
  • domain: *company.com
  • addresses: info@codetwo.com and it_*@codetwo.com
  • organizational unit: Computers

    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 from addresses belonging to company.com domain and all its subdomains excluding support.company.com and it@company.com
  • sent from users belonging to Computers Organizational Unit
  • sent from info@codetwo.com
  • sent from users of codetwo.com domain, whose address starts with it_, excluding it_john@codetwo.com.


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

    Each criterium specified above has its equivalent in the exceptions list - the lower field of the senders' scope.

    If a user sends a message from a mail client and connects to the Exchange Server using SMTP protocol, this user is identified by the SMTP address specified in the properties of the given account in the mail client, and not by the account s/he uses to log in to SMTP server.

    See also:
    How to create different signatures/disclaimers for users from various Active Directory groups