James is an experienced product specialist with a strong background in the IT and SaaS industry. As Senior Product Marketing Manager at Exclaimer, he plays a key role in showcasing the value of centralized email signature solutions and transforming them into a powerful communication tool for organizations.
What's new in Exclaimer: October 2026
Key takeaway
Default Signature Source: Admins can now choose which email signature shared mailboxes use by default in the Outlook Add-in. Nothing changes unless an admin switches it.
Sign in with email: The sign-in page checks for single sign-on and sends people to the right place.
Accessibility: Screen reader labels in more places, clickable QR codes, and a language setting for screen readers.
Faster Signature Tester thumbnails, clearer client-side setup, and fixes for reply separators and Google Workspace sync.
This edition covers changes released between October 1 and October 31, 2026.
Highlights
Choose the default email signature for shared mailboxes
Available to all customers using the Outlook Add-in (client-side)
When someone sends from a shared mailbox in the Exclaimer Outlook Add-in, the shared mailbox’s email signature is used by default. Admins can now switch that default to the sender's personal email signature, so recipients can see which person replied. The setting is called Default Signature Source, and you’ll find it in Mail Flow.
Who's affected: Admins. What to do: Nothing, unless you want shared mailboxes to use the sender's personal email signature.
The same release also adds a two-column responsive layout for email signatures when the Exclaimer Outlook Add-in taskbar is expanded, plus some updated icons.
Sign in with email, with single sign-on enforced.
Available to all customers
The sign-in page now has a "Sign in with email" button. After you enter your email address, Exclaimer checks whether it's linked to a single sign-on (SSO) configuration. If it is, you're sent to sign in with SSO. If it isn't, a password field appears and sign-in works as before.
This should cut errors for people with SSO who try a password, request a reset email that never arrives, or lock their account after repeated attempts.
Who's affected: Everyone who signs in to the portal. What to do: Nothing.
Accessibility Controls for email signatures
We added more accessibility options to the Signature Designer, Campaigns, and Brand Kits, as part of our work to support WCAG 2.1 AA.
Screen reader labels for hyperlinks and linked images. Hyperlinks in the Signature Designer and Campaigns, and linked images in Brand Kits, can now carry a label so people using a screen reader hear where each link goes.
Screen reader labels for other signature elements. Social icons, social media strips, calendar booking links, and rotating banners can now carry a label, so people using a screen reader know what each one is.
Clickable QR codes. You can turn an email signature QR code into a link for recipients who can’t scan it, such as anyone reading the email on their phone. Existing QR codes don't update automatically, so edit the QR code to apply the change.
A language setting for screen readers. Choose the language a screen reader uses to read an email signature, so it's read aloud in the right language. It applies to the whole email signature canvas, so individual text boxes can’t have their own language.
Improvements
Clearer client-side setup. A new banner in the client-side connection flow explains that email signatures take a little time to reach end users, so admins aren't left wondering why they aren't showing yet. It appears once an admin has started the add-in step.
Faster Signature Tester thumbnails. Thumbnails in the client-side Signature Tester now load much faster, and they load as you scroll, so checking an email signature no longer means a long wait. In testing, load time dropped from 20 to 30 seconds to about three seconds.
User Photos upload. The User Photos component in Sender Management has a refreshed design and faster-loading thumbnails, and successful uploads no longer look like they failed because of a caching issue.
Server-side setup for Microsoft 365. Setup now gives clearer error messages and handles retries and duplicate starts better, so it's easier to see what went wrong and to finish setup after an interruption.
Fixes
Email signature placement
Exclaimer now recognizes more reply separators, so email signatures land in the right place:
Replies from Apple Mail on macOS Tahoe 26.0.1 now receive an email signature.
Forwards from Apple Mail now have the email signature in the right position when the remote domain has Transport Neutral Encapsulation Format (TNEF) turned off.
Emails sent from the Outreach sales system now get the email signature in the right place, instead of at the bottom of the chain and sometimes duplicated.
Email signatures on emails from LEAP now land in the right place, even with the tracking string that LEAP adds to the end of the email body.
An Outlook behavior could leave an element users couldn't delete, which kept the email signature at the top of the email after the reply content was removed. Updated reply separator detection now works around it.
Google Workspace and the User Details Editor
Job titles and departments could be missing from email signatures for Google Workspace customers with no organization record is marked as primary. Exclaimer now uses the first record Google returns, so those details come through.
Fields overridden with a blank value now display correctly in the User Details Editor, so people can see the override they saved.
Questions or feedback? Click here.
