Can I have my subscription set up for both Microsoft 365 and Google Workspace?
No. Exclaimer subscriptions can only be configured for one type of platform. There is no way to have a 'dual setup'. If you want to use Exclaimer for both Microsoft 365 and Google, you must have a separate subscription for each platform.
What is the difference between the different configuration options?
-
Server-Side: In this mode, signatures are applied to all email messages via Exclaimer's Cloud service, irrespective of which browser/device/email client is used.
-
Client-Side: 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.
Can I change my configuration options later?
The Launch button is not available. What do I do?
You must log in as the subscription Owner and ensure you have accepted the terms and conditions. See our
solutions article for this issue.
I have changed domain name, or got a new one. What do I do now?
You do not need to make any changes in Exclaimer, but should ensure that:
- Data synchronization has been completed (this occurs automatically once a day, but can be manually done 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 set up as standard, so unless you have actively changed this setting, it will be correct.
Will the Sent Items Update feature work with my On-Premises mailboxes?
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.
I have configured the server-side/client-side feature. Do I update the SPF record?
- If you have configured
Server-Side deployment, you must update the
Sender Policy Framework (SPF) record. If you do not, there is a risk that messages routed from Exclaimer back to your email service are marked as spam.
- If you have configured Client-Side deployment, you do not need to update the SPF record.
Is a license required for sending email as or on behalf of a shared mailbox?
If send-as permissions are used, an additional license is required.
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.
Does Exclaimer integrate with SendGrid?
Exclaimer does not currently integrate with emails sent directly from SendGrid. If the emails are also passed to your Microsoft 365 or Google tenancies, and the MAILFROM addresses match users' email addresses, then it may still be possible for you to apply signatures sent from SendGrid.
If you are interested in integrating Exclaimer with SendGrid,
raise a ticket with our Support team, who can submit a feature request on your behalf.
Does Exclaimer Outlook Add-in work in Chrome incognito mode?
Yes, however you may need to enable third-party cookies if you are experiencing any display issues.
Learn more about
managing Google Chrome cookies.
How does the Exclaimer Server-Side configuration handle messages when a user has already applied a synchronized signature in Outlook or Apple Mail?
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.
How do you update group members?
To update group members, change their memberships in the Active Directory, then resynchronize to reflect changes.
Which group types can be specified to restrict the use of the Exclaimer Exchange Transport Agent?
You can specify the following group types when restricting the Exclaimer Exchange Transport Agent to members of a specific group:
- Security Group
- Distribution groups
Which group types will not work with the Exclaimer Exchange Transport Agent?
The following group types and group configurations will not work with the Exclaimer Exchange Transport Agent:
- Dynamic Distribution Groups
- Nested groups
Is there any Outlook Add-in that works with Google Workspace Sync for Microsoft Outlook (GWSMO)?
No, there is no Outlook Add-in that works with GWSMO.
Can I use my personal signature when sending as a shared mailbox using the Outlook Add-in?
Can I sync user photos from Entra (formerly Azure AD) or Google Workspace?
Yes, with the
Pro plan, you can synchronize user photos from
Entra ID/
Google Workspace, or you can use the
user photos upload feature.
Does Exclaimer work with Microsoft 365 purchased from GoDaddy?
Yes, Exclaimer is known to work when Microsoft 365 is purchased from GoDaddy. However, this does not work with the Outlook Add-in.
Ensure that you have an account with Global Admin permissions and access to Exchange Online for use during the setup of Exclaimer.
Can I use both custom attributes and additional Azure AD attributes?
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.
What is the difference between Send As and Send on Behalf?
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.
Can a shared mailbox signature include both the mailbox and the sender’s details?
No. Signatures sent from shared mailboxes cannot include multiple users' details. The signature will use information from one source only, either the shared mailbox or the user.
Can I rename a field from Custom Attribute to Pronouns in the User Details Editor?
No, it is not possible to rename existing fields. However, users on the
Pro plan can add a new field named Pronouns by uploading a CSV file that includes a new column with the header Pronouns. Once uploaded, an Admin can enable this field for users to fill in themselves.
For more information, see
how to add pronouns, qualifications, accreditations or other custom info to your template.
Why does Exclaimer say my connector cannot be validated?
The Exclaimer connector validation may appear to fail because the request is sent from the server rather than a user mailbox, and automated messages are not supported.
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.
Do I need to validate the Exclaimer connector for it to work?
No, Exclaimer connectors do not require validation to operate. They will function correctly even if the validation appears to fail.
Can I apply a signature to an RTF message?
Exclaimer does not support applying signatures to RTF messages in Server-Side deployment on any platform. Only users with Classic Outlook may apply a Client-Side signature to an RTF message, but this may cause formatting issues and trigger a warning from the Exclaimer Outlook Add-in.
I don't want to sync all shared mailboxes, only certain ones. Can I only sync some mailboxes and not others?
No, you cannot selectively sync certain mailboxes and not others. This includes disabled mailboxes when you are using the Synchronize Disabled Accounts feature. Exclaimer synchronizes all mailboxes present.
Does Exclaimer use Exchange Online Remote PowerShell (RPS) to set up mail routing connectors?
No. Exclaimer does not use Exchange Online Remote PowerShell (RPS) when setting up mail routing connectors.
Does Exclaimer offer an API or webhooks to sync signature data with third-party systems?
No. Exclaimer does not offer an API or webhooks to sync signature data with third-party systems, such as CRM, HR, or ITSM platforms.
Does Exclaimer publish an API?
Yes. Exclaimer publishes a provisioning API for partners and distributors. However, this API does not sync signature data with third-party systems.
Can I send user data from Exclaimer back to Microsoft 365, Google Workspace, or another system?
No. Exclaimer receives user data from Microsoft 365 or Google Workspace. You cannot send this data back to those platforms.
Can I use exported signature templates in another platform?
No. Exclaimer exports signature templates in its proprietary format. You can only import these templates back into Exclaimer. Other platforms cannot use them.