Please choose a topic below to get started.
- Configuration - Frequently Asked Questions
- Features - Frequently Asked Questions
- Manage Subscription - Frequently Asked Questions
- Purchase/Billing Exclaimer Cloud subscription - Frequently Asked Questions
- Security and Compliance - Frequently Asked Questions
- Signature Designer - Frequently Asked Questions
- Signature Rules - Frequently Asked Questions
- Support - Frequently Asked Questions
Configuration - Frequently Asked Questions
Apply to email from all devices including mobiles: This is also referred to as server-side signatures. In this mode, signatures are applied to all email messages via Exclaimer's Cloud service, irrespective of which browser/device/email client is used.
See before you send (Client-side): This is also referred to as client-side signatures. In this mode, signatures are synchronized to the users' computers for use in Microsoft Outlook.
- Exchange On-Premises: In this mode, server-side signatures are applied to emails sent from on-premises Exchange mailboxes.
After the initial setup, you can:
Configure server-side signatures to your subscription.
Configure client-side signatures to your subscription.
You don't need to make any changes in Exclaimer Cloud. But please ensure that:
- Data synchronization has been completed (this occurs automatically once a day but can be forced if required).
- The new or modified domain has been added to the same Microsoft 365 tenancy that was used when signing up for Exclaimer Cloud.
- Messages are routed through the Exclaimer send connector in Microsoft 365 (this is a standard setup, so unless you have actively changed this setting, it will be correct).
Currently, the Sent Items Update will not update any mailboxes hosted within your On-Premises environment.
If required, please raise a feature request via a Support ticket.
- If you have configured the client-side feature, you don't need to update the Sender Policy Framework (SPF) record.
Depending on the configuration, you can set up Send on behalf to apply either the sender's personal signature or the shared mailbox's signature.
- If the Send on behalf feature is disabled, the sender's personal signature will apply, and an additional license is not required.
- If the Send on behalf feature is enabled or the email is sent using Send-as permissions, then the shared mailbox's signature will apply, and an additional license is required.
If you are interested in integrating Exclaimer Cloud with SendGrid, please raise a ticket with our Support team, who can submit a feature request on your behalf.
Learn more about managing Google Chrome cookies.
To prevent duplicate signatures from being applied to a message when using client-side rules, the system carries out a 'text match' check. This check determines if a message has a client-side signature from Exclaimer Cloud Signature Update Agent.
If a client-side signature has been applied, the signature processing stops, and the message is routed back to Microsoft 365 for delivery.
You can 'lock' access to the signature options in Microsoft Outlook and/or archive (remove) all existing Microsoft Outlook signatures for each user.
On the other hand, you cannot restrict a user's ability to edit signatures in Apple Mail.
- For multiple groups, separate them by spaces, commas or semi-colons.
- Email addresses will not work.
You can specify the following group types when restricting the Exclaimer Exchange Transport Agent to members of a specific group:
- Security Group
- Distribution groups
The following group types and group configurations will not work with the Exclaimer Exchange Transport Agent:
- Dynamic Distribution Groups
- Nested groups
For more information, please see the differences between Exclaimer Cloud Outlook Add-in and Exclaimer Cloud Signature Update Agent?
Yes, Exclaimer Cloud is known to work where Microsoft 365 is purchased from GoDaddy.
Please ensure that you have an account with Global Admin permissions and access to Exchange Online for use during the setup of Exclaimer Cloud.