Signature added twice
This article is obsolete for newer releases of CodeTwo Exchange Rules family software. If you have:
- CodeTwo Exchange Rules PRO version 1.4.5
- CodeTwo Exchange Rules 2013 version 1.2.0
- CodeTwo Exchange Rules 2010 version 2.2.0
- CodeTwo Exchange Rules 2007 version 3.2.0
or newer, please refer to this knowledge base article that explains how to use a built in solution for this type of problems.
This article should be applied for owners of releases older than listed above.
Some organizations may want to use two Exchange Servers on the same site working together for example for the purpose of redundancy or load balancing. Others, usually big companies will have multiple sites, each with their own Exchange Server but all of them working within the same domain. Two copies of Exchange Rules cannot communicate with each other, therefore to avoid situations in which emails passing through two Exchange Servers within the same organization are getting the same signature added twice, the following solutions can be implemented.
Fig. 1. The same signature added twice? This is what this article is about.
Case 1 – Multiple locations with one Exchange Server each.
Fig. 2. Multiple locations with one Exchange Server each and a common Active Directory.
The best idea is to base your rules on scopes of senders and recipients defined as an active directory group of users or their email addresses. You need to deploy identical rules to both Exchange Rules installation but define different scopes depending on which server is going to be always used by which group of users.
Fig. 3. Multiple locations with one Exchange Server each and a common Active Directory. Each site has the same set of rules but scopes defined as AD groups of local users.
This is not going to work for users who travel a lot between those locations and therefore switch between Exchange Servers. For such scenario, following Case 2 is a better option.
Case 2 – A single location with two Exchange Servers or multiple locations with traveling users.
Fig. 4. A single location with two Exchange Servers. Each server must have the same set of rules due to unsure emails routing, how to avoid double signatures in such configuration?
To make sure that every email receives only one signature you can make use of the Suppressing Disclaimers feature.
- When creating your signature add some random string of characters e.g. ""FgHJr$#56" and change the color of this word to the same color as the background of your signature so it is invisible for the recipient but still detectable for the software.
- Set the Suppressing Disclaimers feature on both servers to prevent Exchange Rules from adding the second signature when this phrase is found in the body of the message.
- Also, configure it to remove the suppressing phrase from the message.
Configured this way, the Suppressing Disclaimers will prevent the second hub server from adding an extra signature and remove the suppressing phrase. Of course, if your mail passes Exchange Servers randomly, some of them go through one hub transport server and some of them go through two hub transport servers then there is a chance that some of your emails will leave your organization with the suppressing phrase onboard. There is no way of avoiding this situation if the number of Exchange Servers which process messages is uncertain or not constant. This is why the suppressing phrase should be masked by using the same color as the background. You can also consider using a visible string of characters which in case of staying in the signature will look like an integral part of it.
Fig. 5. A keyword embedded in the signature pretending to be a delimiter.
The downside of this method is that it works only for a chain of two Exchange Servers. If your mail passes through three or more identically configured Exchange Rules agents multiple signatures will be added. See the Fig. 6 below to see the algorithm. The solution to this would be configuring the rules NOT to remove the suppressing phrases from the signatures.
Fig. 6. A visualization of the algorithm.
- Applies to: CodeTwo Exchange Rules 2.x, 3.x CodeTwo Exchange Rules 2007 1.x, 2.x, 3.x CodeTwo Exchange Rules 2010 1.x, 2.x CodeTwo Exchange Rules 2013 1.x CodeTwo Exchange Rules Pro 1.x
- Categories: How-To
- Last modified: 2015-06-23
- Created: 2012-10-16
- ID: 268
- Keywords: DAG, CAS, multiple, Exchange, servers, two, double, signature, added, twice, load, balancing