Local Signatures were introduced in Crossware Mail Signature Version 3.0.
Local signatures allows the creation and distribution of locally deployed signatures to the Lotus Notes client, Lotus iNotes client and Blackberry devices. Local signatures are not supported on android devices.
Crossware Mail Signature can distribute signatures to Pre-8.5 Lotus Notes clients, via an HTML signature File for Notes clients, and a Plain Text signature for Lotus iNotes / Domino Web Access.
For Post-8.5 Lotus Notes clients, the application can automatically append a Rich Text Signature to the users Calendar Profile and apply an HTML Signature for Lotus iNotes.
For Blackberry users, the application can apply a Plain Text Signature at the Blackberry Enterprise Server.
Steps to setting up Local Signatures
Create a Signature Configuration Document
Create a Signature Configuration - these are the same configuration documents used in server based signatures.
Ensure that the Name of the signature does not match an existing group otherwise the signature will be used as a server base signature as well.
Create a User Configuration Document
A User Configuration document controls the setting applied to all users who are associated with this configuration document.
Create either a User Log document OR execute a console command
One option is to create a New User Log document.
Otherwise execute the console command to automatically generate the User Log documents from a Group.
The User Configuration documents have a field called "User Group". This field is used by the esig task to monitor and maintain signatures for groups of user. See Esig Client Commands for further information.
The below PDF shows possible installations when using Local Signatures. NB. If you are using Local Signatures alongside server based signatures you will still need to install Crossware Mail Signature on your Mail Servers or SMTP servers.