Server based signatures on emails from Mail-in databases vs local user-defined signatures

What happens when the user creates an email from the mail-in database?


When a user sends an mail from a mail-in database and the email reaches the server, Crossware Mail Signature applies the signature based upon the user who is defined in the owners field of the database (principal fields). If the principal field is not set the signature will be based upon the From field. If there is a local signature defined in the mail-in database it can happen that two signatures are appended first the local signature and then the server based signature based upon the above rule.



1) The first one is to simply let Crossware Mail Signature control all signatures so no user mail-file or mail-in databases needs to have a local signature.

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.

2) The second option is to make a slight change to your standard mail template that will prevent Crossware Mail Signature from appending a second signature.

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:

  • CwesigProcessed=1

When the email reaches the server, the program will recognise this field and simply pass it on without adding a signature.

For more information on the CwEsigProcessed field see Crossware Mail Signature System Fields.

NOTE: When an upgrade to Domino occurs and the email template is upgraded, this change will need to be re-applied to your template.


3) The third option is to make a change to the mail-in database so it creates a unique field that tells Crossware Mail Signature that it should process the email and append a signature but all other emails are passed through without a signature.

Related Products: CMS DOM v4