Important Notices


General Upgrade Notices

The upgrade from Crossware Mail Signature Version 3 to Crossware Mail Signature Version 4 should be seamless, there are no specific steps to be taken before the upgrade.

As always it is recommended that you perform a full backup of the esig.nsf database. The database contains the binaries if needed.

Please review the System Requirements as this has changed.

Upgrading from Version 3.09 and above Notices

There are no specific requirements for upgrading from Version 3.09 or above.

A change was made in Version 3.09 to the method of generating Local Rich Text Signatures. The new method allows support for sub-signatures and will correct an issue which may occur with the paragraphs in the Rich Text fields. For users of the local signature functionality, the above changes will result in an updated signature being issued to all users.

Upgrading from Version 3.08 Notices

IMPORTANT: When upgrading from Version 3.08, extra care must be taken if the (!NewLineFormula!) (see How to add Carriage Returns into a formula) have been used as part of a configuration. In V3.08, support for double quotes was added to allow returned data to contain single quotes.

This fix caused the (!NewLineFormula!) feature used in V3.07 installations to fail. To resolve the issue (!NewLineFormula!), look-ups require modification.

In 3.09 the above fix has been undone and the escaping on lookups has been implemented as an option of the look-up document. Therefore, existing formulas that contain escape characters need to be edited and the new option selected.

If you are unsure if you look-ups require modification, please send a support copy (see Support_Database) of your signature configuration to prior to upgrading, and we will investigate any necessary modifications..

Issues Resolved


  • 468 - Support for Preview switch and notes.ini variable.
  • 512 - User with author access cannot create a draft version of the signature.
  • 516 - Error in creating a new version from the Signature Configuration Document.
  • 517 - Incorrect formatted body fields can cause server to crash.
  • 518 - Empty database caused server crash.
  • 520 - Concise- no logo template has corrupted lookups.
  • 521 - HTML replies not detected correctly on iSeries.
  • 522 - Mime Editor images not viewable on Outlook Web Access.
  • 523 - Add Support for 64bit Linux.
  • 524 - Ldap data with crlf's does not have the separator applied.
  • 525 - Inline images added to the MIME Editor do not add crlf's.
  • 526 - File Import on old HTML Strips out crlf's.
  • 527 - Empty 7bit email results in odd characters
  • 528 - Debug messages is logged to often
Related Products: CMS DOM v4