Using custom reply separators

When Exclaimer Signature Manager Exchange Edition is installed, standard reply separators are included. Under normal circumstances, administrators do not need to change this information unless a custom reply separator is required.

To add a new reply separator, access the signature policy settings tab and click the add button to open the add/edit reply separator window:

When defining custom separators, you can use:

Underscores
Hyphens
HTML tags
HTML style attributes
Spaces
Regular expressions

Underscores

Character	Description	Exclaimer Interpretation.
_	Single underscore	Look for one or more consecutive underscores.
__	Double underscore	Look for two underscores, one after the other, followed by more consecutive underscores.
___	Triple underscore	Look for three underscores, one after the other, followed by more consecutive underscores.

Hyphens

Character	Description	Exclaimer Interpretation.
-	Single hyphen	Look for one or more consecutive hyphens.
--	Double hyphen	Look for two hyphens, one after the other, followed by more consecutive hyphens.
---	Triple hyphen	Look for three hyphens, one after the other, followed by more consecutive hyphens.
	When searching for the specific string '-Original Message-' as a reply separator, Exclaimer Signature Manager Exchange Edition matches one or more hyphens at the start and end of the text 'original message'. It will also accept a trailing line space before the text, 'Original Message'. For example, Exclaimer Signature Manager Exchange Edition will match: - - - - - - -Original Message- - - - - - - - - -Original Message- - - -Original Message-

HTML tags

Exclaimer Signature Manager Exchange Edition can resolve HTML tags as reply separators. It matches first the element, then the attribute (if present in the search string) and finally the attribute value (if present in the search string). This matching process is illustrated below:

First, match the element:

Next, match the attribute for the element:

Finally, match the attribute value:

Example

Suppose that the tag below was specified as a separator:

For this string, Exclaimer Signature Manager Exchange Edition will match any horizontal rule with a tabindex of -1. The horizontal rule can include other attributes and values but it must have the attribute and value of tabIndex=-1. As such, the following elements would be matched:

...or

However, the following element would not be matched (because the attribute value is set to -2 rather than -1):

HTML style attributes

Style attributes are resolved in a similar way to HTML tags, described above.

Example

Suppose that the tag below was specified as a separator:

For this text string, Exclaimer Signature Manager Exchange Edition will match any div tag containing a style attribute of 'border:none\;border-top:solid #B5C4DF 1.0pt\;padding:’.

The div tag can include other attributes but it must include the attribute and values style='border:none\;border-top:solid #B5C4DF 1.0pt\;padding:'. As such, the following style attributes would be matched:

...or

However, the following element would not be matched

Spaces

Exclaimer Signature Manager Exchange Edition will handle spaces when searching for a specific string. A match will be made if a tab occurs within the space and if a space rolls over into a line break. For example, Exclaimer Signature Manager Exchange Edition will match:

-Original Message-

...or

-Original Message-

...or

-Original

Message-

Regular expressions

Many common reply separators are static - i.e. a given string of text and/or characters. However, with the proliferation of email applications on mobile devices, variances between regions, etc, relying on static reply separators may not always be sufficient.

If required, dynamic reply separators can be handled using regular expressions. Regular expressions are used to express how the software should look for a specified pattern in text and then what to do when a pattern match is found.

The composition of regular expressions is an advanced task, which may require some knowledge of programming. If this is a requirement, please contact Exclaimer support.