Back

New Exclaimer Signature Manager releases available

We’ve just released new versions of Exclaimer Signature Manager Outlook Edition and Exclaimer Signature Manager Office 365 Edition. The big news is that both products now support Outlook 2016.

If you haven’t received an email with your update details and you have a valid SMA (Software Maintenance Agreement), please contact the Exclaimer Sales department on +44 (0)1252 531422 or email sales@exclaimer.com.

 

Exclaimer Signature Manager Outlook Edition

Version 3.0.3

 

Changes and Enhancements:

  • Outlook 2016 support.

Fixed Issues:

  • ExSync.exe certificate had expired.
  • Event log entries were not logged when the configuration contained 43 or more policies.
  • Temporary files from the Remote deployment operation were not automatically deleted.
  • Remote deployment service had a memory leak.
  • Configuration file was locked in some situations preventing configuration changes from taking effect.
  • Signatures would not be generated until the Outlook connector service was restarted in certain scenarios.

Read the release notes >>

 

Exclaimer Signature Manager Office 365 Edition

Version 1.0.6

 

New Features and Changes:

  • Outlook 2016 support.
  • Ability to enable the signature options in Outlook.
  • New option to include signature on reply and forwards in OWA.

Fixed Issues:

  • Outlook was not detected correctly in some scenarios.
  • Initial subscription request did not maintain affinity which caused signatures to not be uploaded for some users.
  • Memory was leaking when a signature template contained multiple nested smart tables.
  • ‘Property value is not valid’ error occurred when setting an RSS item field to a numeric value.
  • Signature options were disabled when Outlook Signature Update Agent was uninstalled.
  • Field data was not included in signatures when the user’s SMTP address and username did not match, and the policy condition was set to a group.
  • Existing signatures were removed as default for new messages/replies and forwards when a policy did not set the signature as default.

Read the release notes >>