Articles sorted alphabetically
|
An improvement was added to V3.09 that allowed the path of the extracted HTML file to be configurable. One of the improvements allowed the path to be constructed using LotusScript. If the path generated did not contain a trailing slash, it was treated as a "prefix" to the HTML file. e.g. path ... |
|
Prior to this fix, the application incorrectly determined the MIME Boundaries. This resulted in the wrong signature being merged incorrectly. If the email was then forwarded to a MailMarshal server, it was detected as "Malformed Mime" and does not get delivered to the recipient. This fix was ... |
|
The following actions will help troubleshoot missing signatures: 1. Check that the email has been processed by the signature application
See (Crossware Mail Signature System Fields). If these fields are not present, then the email hasn't been processed by Crossware Mail Signature. The ... |
|
Crossware Mail Signature Email Field lookups allow you to extract data from the email. For example you may wish to mention the subject line within an email disclaimer, or include the senders email address as part of the signature. Configuring custom database lookups allows you to define a ... |
|
Prior to this fix, when creating a subsignature of type "Internal Only" or "External Only" there was no check to ensure that the Meta Data document was set up to define the internal domains. With this fix, a check is now made for the "OtherDomains" Meta Data document and prompts the user to ... |
|
This example demonstrates how to create lookups which will automatically add a new line ONLY if there is information returned from another lookup. For Example, in the configuration below, if the Fax number is not set in the users Person document, a empty line if left in the signature. b ... |
|
This example demonstrates how to create lookups which will automatically add a spacer symbol to the lookup ONLY if the spacer is required. Problem
You create a signature configuration using the (!PhoneAndDescription!), (!FaxAndDescription!) and (!MobileAndDescription!) lookups to add the ' ... |
|
Prior to this release, the installer would show an unhelpful run time error message if the user performing the installation on a Windows server did not have access to run unrestricted agents. This change detects the unauthorised error code and displays a more helpful error message with a link to a ... |
|
Prior to this release, if the senders full user name was required, several lookups needed to be created to extract the data from the address book and extract the first element of the "FullName" field. This improvement add an additional built in lookup (!username!) to extract the information ... |
|
Prior to this fix, there were inconsistencies on the configuration forms. This fix made the forms consistent with Save, Close and Edit buttons. This fix was implemented in Version 3.07 |