Setting
|
Description
|
Require users to be mailbox enabled to receive signatures
|
Specifies that users must have an Exchange Server mailbox in order to receive signatures.
|
Include nested groups when determining user group membership
|
Specifies that nested sub-groups should be included when determining user group membership during deployment of signatures.
|
Remove trailing spaces from field values when generating signatures
|
Specifies that trailing spaces should be removed from field values when generating signatures; field values containing only spaces will be trimmed to empty values. For further information, see the chapter on working with fields.
|
Use ASCII format for all Outlook signature files
|
Specifies that sign.exe should write all Outlook signature files in ASCII format, rather than Unicode, when appropriate (this will affect how HTML and plain-text signature files are written). It should not normally be necessary to use this option. If it is enabled, it is important to note that any non-ASCII characters present in the signature will be converted to question marks in the signature file.
|
Record status information about signature generation and injection (SQL Server databases only)
|
Specifies that additional information is recorded to the Deployment Status log when signatures are generated (for use by the Transport Agent) or injected into emails (by the Transport Agent). It is recommended that this option is not enabled unless specific logging information about the Transport Agent is required.
|
Store deployment status information in files (Access databases only)
|
Specifies that deployment status information should be stored in files (located in a sub-folder of the folder containing the database), rather than being stored in the database itself.
|