A signature is not applied to signed or encrypted messages – Exclaimer Cloud

Scenario

You are using Exclaimer Cloud, and you notice that when a signed or encrypted message is processed, no signature is appended.

Reason

This is expected behaviour when using the server-side signature rules - it ensures that security on the message is preserved and un-tampered when the message is delivered to the intended recipient.

NOTE:

There are two options when defining signature rules:

Server-side: Signatures are applied once the message has been routed to Exclaimer Cloud. As the signature is applied once the message has been sent, you will not be able to see the signature whilst composing your email. Signatures will be applied to messages sent from any device.
Client-side: Signatures are synchronized to Microsoft 365 (Outlook and Apple Mail) or Google Workspace (Gmail), where they are visible whilst composing your email.

Resolution

It is possible to apply a signature to encrypted messages using client-side signature rules.
This is because the signature is present when the message is composed, so the message is not processed by our servers.

Alternatively, if using server-side signatures, the signature will need to be applied before the message is encrypted. If you use a transport rule to encrypt messages, provided the Exclaimer transport rule has a higher priority and is processed before the encryption transport rule, the message will have a signature applied.