We have just released new versions of the following Exclaimer products to our website:
- Exclaimer Signature Manager Exchange Edition
- Exclaimer Signature Manager Outlook Edition
- Exclaimer Template Editor
- Exclaimer Auto Responder
Please see below for fixed issues, changes and enhancements:
Signature Manager Exchange Edition version v2.2.0
Download English version >>
Download German version >>
Fixed Issues
- When a {Conditional Field} or a {Composite Field} was used inside a {List of Fields} the Separator was missing.
- Row in Smart Table was not displayed when ‘suppress field’ was not present in template.
- Certain non-US ASCII characters in RTF files used in ‘Content From File’ were not displayed correctly in HTML preview and HTML messages.
- Unicode characters were displayed as questions marks when pasted from Notepad.
- Certain Exclaimer event log entries were incorrectly appearing in the application log.
- An exception was thrown when importing a template that had a {Custom Image} containing a {Field}.
- In certain scenarios the reply/forward message and signature content were applied at the end of an email conversation.
- A semi colon was added to the end of the line of HTML content when the content included an ampersand.
Changes and Enhancements
- Improved error handling when NETWORK SERVICE account does not have access to the Template Library folder.
- Improved compatibility with Anti-virus applications.
- {Original Message} fields now added to templates when imported from Exclaimer Signature Manager Outlook Edition.
Signature Manager Outlook Edition v3.0.2
Download English version >>
Download German version >>
Fixed Issues
- Excessive memory usage in the Exclaimer Outlook Settings service.
- Group enumeration not correctly detecting members of a group when the group and members are in different domains.
- Signatures not generated when a non-signature ZIP file was present in the deployment share.
- In certain scenarios the Policy Tester would contain incorrect warnings that an OWA signature template contains local images when using internet images.
- Local copy of images were incorrectly used when a template with internet images was imported.
- When changing ‘Deploy signature to’ from ‘Outlook’ to ‘OWA’ the image options were not updated correctly.
- Policy Tester was unable to determine membership of the Domain Users group.
- Unicode characters were displaying as questions marks when pasted from Notepad.
- An exception was thrown when importing a template that had a {Custom Image} containing a {Field}.
- ExSync did not disregard backslashes used as encoding characters.
- ExSync was not able to create a signature file when the user’s display name contained speech marks.
- All template files were saved when saving changes in the console.
Changes and Enhancements
- Improved compatibility with Anti-virus applications.
- Save operation now has a retry strategy to cope with locked files.
Template Editor v2.02
Fixed Issues
- Unicode characters were displayed as questions marks when pasted from Notepad.
- An exception was thrown when copying a template that had a {Custom Image} containing a {Field} between Exclaimer products.
- Console was unresponsive when attempting to display the preview image for an RSS feed when there is no internet connection.
- Certain non-US ASCII characters in RTF files used in ‘Content From File’ were not displayed correctly in HTML preview.
Auto Responder v2.1.0
Fixed Issues
- Excessive memory usage of EdgeTransport.
- Group enumeration not correctly detecting members of a group when the group and members are in different domains.
- Console validation was preventing save operation when the ‘Auto response is from’ field had a manually entered display name.
- Policy was not applied when the ‘Auto response is from’ field contained a display name from a {field} and a manually entered email address.
- Recipient fields were not displayed when inserted into the ‘Replace subject’ field.
- Unicode characters displaying as questions marks when pasted from Notepad.
- An exception was thrown when importing a template that had a {Custom Image} containing a {Field}.
