-
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 for your subscription.
Configure Client-Side signatures for your subscription.
You don't need to make any changes in Exclaimer. 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.
- 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 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 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.
- 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
Yes, Exclaimer is known to work where Microsoft 365 is purchased from GoDaddy.
Ensure that you have an account with Global Admin permissions and access to Exchange Online for use during the setup of Exclaimer.
It is not possible to enable both the Custom Attributes and the Additional Azure AD Attributes features.
However, you can include custom attributes, also known as extension attributes, within the list of directory extensions in Azure AD Connect when selecting up to 100 attributes for use with the Additional Azure AD Attributes feature.
Send As is a permissions setting in Microsoft 365/Outlook that allows you to send an email from a different email address that appears to the recipient as though that email address has sent it. When you draft an email, you can enter another user or group's email address in the From field - the email recipient sees an email from that user, with that user's signature applied.
For example, User 2 has granted permission for Users 2 and 3 to Send As on their account. User 2 sends an email and chooses User 1's email address to send it. Recipients see an email from User 1, with User 1's details, even though User 2 composed and sent the email. This is 'sending as' User 1.
Send on Behalf is a permissions setting in Microsoft 365/Outlook that allows you to send an email from a different email address that shows the recipient you are sending on behalf of another user. When you draft an email, you can enter another user or group's email address in the From field - the recipient sees an email that states it has been sent by you on behalf of the other user or group.
For example, Users 1, 2, and 3 have access to the shared mailbox of Department 1. User 1 sends an email from the Department 1 account. Recipients see an email from 'User 1 on behalf of Department 1'. This is 'sending on behalf' of Department 1.
In Exclaimer, Send on Behalf is only available for Server-Side deployment. You need to use our Send on Behalf settings as well as your Microsoft settings to enable Send on Behalf, so that Exclaimer can evaluate your signatures. When Send on Behalf is enabled, emails use the signature for the email address in the From field.
For more information, see how to add pronouns, qualifications, accreditations or other custom info to your template.
However, you do not need to validate the Exclaimer connectors to operate (see the following FAQ).
If you still require further help with connector validation, raise a Support ticket and describe why you are trying to validate the connector.