Relevant Product: Signature Manager Exchange Edition
WARNING! The following products were discontinued on 30 September 2022:
- Exclaimer Signature Manager Outlook Edition
- Exclaimer Signature Manager Exchange Edition
The end of Support for these products is 30th September 2024.
For more information, please see the Discontinued Questions and Answers page.
You are adding or updating a signature template in Exclaimer Signature Manager Exchange Edition or Signature Manager Outlook Edition. When you try to save changes, the following error is displayed:
You are not able to save the template until the Plain Text element is updated, however, you only wish to create an HTML version.
For example, you want to create a template that contains a campaign promotion/banner for emails- the kind of content that is of little or no use in anything other than HTML format.
If you create a new signature template in Exclaimer Signature Manager Exchange Edition or Signature Manager Outlook Edition, it must be created in three formats:
- Rich Text
- Plain Text
In most cases, Outlook composes and sends new email messages in HTML format. However, if Outlook receives an email in Plain Text Format, then by default, it will reply in Plain Text Format. In this case, unless the sender manually changes the email to HTML before sending it, a Plain Text version of the signature will be applied.
For this reason, it is mandatory to create all three formats of a signature template - when adding or editing templates, you cannot save changes until all three formats are set.
If you attempt to save a template without updating the Plain Text format, an error message is displayed.
If you are sure that a Plain Text version of your template will never be needed, a quick solution to clear the warning message and allow you to save changes - is to add an empty composite field to the Plain Text version, as displayed below:
A Composite Field can be thought of as a container for other fields - so if you just add a composite field without defining what it is comprised of, it will never be populated in signatures.