ShowTable of Contents
A problem may occur when a user has a local signature set up, and two signatures get appended.
When a user has set up a local signature, it will be appended when an email is created from within their own mail file. When the email is sent, it hits the server and if he is a member of a group that should have a signature, Crossware Mail Signature will append the configured signature. This means that the email will have two signatures - the local signature defined by the user, and the server based signature applied by Crossware Mail Signature.
There are a couple of options to resolve this issue:
1. Let the server control all signatures so that local signatures are not required
This will ensure that signatures are consistent across the organisation, and follow the company standards for signatures. It will also ensure that the user gets the same signature regardless of the device being used, eg iNotes, Blackberry or any other device controlled by Lotus Traveler.
Using server-applied signatures rather than local signatures also means that logos or image files aren't added at the local workstation, taking up network capacity and disc storage. Any signature that is currently being used by individuals is able to be created in Crossware Mail Signature.
See Disabling users existing email signatures
for instructions on how to disable local signatures.
2. Use the local signature and prevent the server signature from being applied
If a local user-defined signature is being used, the standard mail template can be modified to prevent Crossware Mail Signature from appending a second signature.
Only a small change is required, simply set the following field on the email being sent:
When the email reaches the server, the program will recognise this field and simply pass it on without adding a signature.
Note: when an upgrade to Domino occurs, this change will need to be re-applied to your template.
For more information on the CwEsigProcessed field see Crossware Mail Signature System Fields