Server-side vs client-side email signatures: Choosing the right deployment method

Published

Updated

Image Placeholder

TL;DR

  • Server-side email signatures are applied during mail transport, after the sender clicks send. Server-side deployment works on every device and email client, including mobile, with four exceptions.

  • Client-side email signatures are inserted while the sender writes, so the sender sees the finished email signature before sending, except on Outlook mobile, where the default email signature is applied automatically. Client-side deployment works only where the client-side setup is in place. Exclaimer's support article says disabling Exchange Web Services (EWS) can stop a centrally deployed Exclaimer Outlook Add-in from loading, and that classic Outlook builds 19725.20000 and later no longer depend on EWS.

  • Hybrid deployment runs client-side and server-side deployment together, and is the setup to aim for. The client-side email signature gives compose-time visibility, and the server-side email signature is applied to messages that go out without one, apart from the four exceptions below.

Server-side deployment applies an email signature as mail routes through Exclaimer's cloud solution and works on every device and email client, with four exceptions. Client-side deployment inserts the email signature while the sender writes, so the sender sees the email signature before sending, except on Outlook mobile, where the default is applied automatically. It works only where the add-in is installed. Hybrid deployment runs both.

Key takeaway

Both methods are centrally managed in Exclaimer. You control email signature templates, sync employee details, and push updates from one platform. The difference is how those email signatures are experienced by users.

What is a server-side email signature?

server side email signature showcasing the disclaimer

A server-side email signature is applied after the sender clicks send. In Microsoft 365, a server-side email signature is applied through Exchange Online mail flow rules, also called transport rules. In Google Workspace, the equivalent is a compliance or routing rule configured in the admin console. Either way, the message passes through a rule at the server, and the email signature is appended before delivery.

Because the mail server applies the email signature, coverage doesn't depend on which client sent the message. Outlook desktop, Outlook on the web, and the Outlook mobile app all pick up the same email signature in Microsoft 365. Google Workspace works the same way for Gmail, on a browser or the mobile app.

The sender can't see the final email signature while composing, and depending on how the mailbox is configured, the copy in Sent Items may not match what the recipient received.



What is a client-side email signature?

deploying a client side signature in Microsoft 365 or Google Workspace

A client-side email signature is inserted into the message while it's being composed, before the sender clicks send. It becomes part of the message body immediately, so the version in Sent Items is the version the recipient got.

The sender sees the finished email signature before sending, except on Outlook mobile, where the default email signature is applied automatically. A message sent from a device or mail client where the setup isn't in place goes out without a client-side email signature.

What can break a client-side email signature?

The email leaves without a client-side email signature in these cases:

  • The Exclaimer Outlook Add-in isn't deployed to the user, or the device isn't one the add-in supports.

  • The Outlook version isn't one of the versions listed in the table below.

  • The Microsoft 365 plan can't deploy apps through Microsoft AppSource. Office 365 E2 is one example.

  • The user sends from the Gmail mobile app. Exclaimer lists only Gmail in a web browser for client-side email signatures.

  • EWS is disabled for the tenant, which can stop a centrally deployed add-in from loading (see the Microsoft 365 section below).

What do the Outlook Add-in and Gmail add-on require?

Client

Minimum version

Notes

Outlook on Windows, Microsoft 365 subscription

Version 2409 (Build 18025.20000)

Click-to-Run installations only

Outlook on Windows, retail perpetual

Version 2501 (Build 18429.20132)

Click-to-Run installations only

Outlook 2024 on Windows, volume-licensed perpetual

Version 2408 (Build 17932.20222)

Office 2024 LTSC is the only volume-licensed installation supported

Outlook on Mac

Version 16.89 (24090815)

New Outlook interface only

Outlook on Android

Version 4.2314.0

Outlook on iOS

Version 4.2352.0

Gmail

Web browser

The Gmail mobile app isn't supported. Google Workspace allows one client-side email signature per user, applied automatically

The figures come from Exclaimer's system requirements.

The Exclaimer Outlook Add-in works with Exchange Online mailboxes only, and the Microsoft 365 plan has to allow app deployment through Microsoft AppSource.

The Exclaimer Signature Update Agent is deprecated. Exclaimer discontinued the Mac version with immediate effect and recommends the Outlook Add-in, which fully supports Outlook for Mac. Mac Mail is no longer supported for client-side email signatures.

How server-side vs client-side compare

Factor

Server-side

Client-side

Insertion point

During mail transport, after send

During composition, before send

Visible before sending

No

Yes, except on Outlook mobile

Mobile coverage

Yes, on all mail apps and devices, with four exceptions

Only where the add-in is installed

Shared mailbox coverage

Needs the mailbox added to an email signature rule and synced, not automatic

Needs the shared mailbox in the email signature's Senders list, with client-side deployment enabled

Employee can remove or alter it

Not for legal disclaimers applied by rule

Possible before sending

Template switching

Automatic, based on rule conditions such as department, region, or recipient

Manual: the sender selects per message where multiple templates are assigned, except on Outlook mobile and in Google Workspace, which allows one client-side email signature

Reply and forward handling

Advanced rules

Separate options for new emails and for replies and forwards

Recipient-based settings

Not applicable

Outlook Add-in only

Analytics

Yes

Yes, but server-side configuration is also required. Recipient email addresses in feedback analytics need the Outlook Add-in

Headline content

Yes

Server-side configuration is also required

Feature differences come from Exclaimer's knowledge base article on client-side and server-side features.

How deployment works in Microsoft 365 and Google Workspace

What do server-side and client-side deployment require?

Environment

Server-side

Client-side

Microsoft 365

Exchange Online

Outlook Add-in (Exchange Online mailboxes)

Exchange on-premises

Exchange Server 2016 CU18 and above, or Exchange Server 2019 CU1 and above

Signature Update Agent

Google Workspace

Google Workspace

Gmail, in a web browser

Server-side deployment supports any standard mail client. Exclaimer doesn't support Microsoft 365 GCC High, DOD, Personal, Family, or Apps plans, Microsoft 365 tenants hosted by 21Vianet, or Google Workspace's G Suite Basic plan.

Microsoft 365

Server-side deployment in Microsoft 365 runs on Exchange Online mail flow rules. A condition is matched, typically on the sender or the recipient domain, and the email signature is appended as the message passes through.

Client-side deployment runs on the Outlook Add-in, which covers Outlook desktop, the web app, and mobile, though mobile support can be more limited than desktop.

Exchange Web Services retirement and the Outlook Add-in

Microsoft is retiring Exchange Web Services (EWS) in Exchange Online, with phased disablement due to begin on October 1, 2026, and permanent retirement scheduled for April 1, 2027. According to Exclaimer's support article, disabling EWS can stop a centrally deployed Exclaimer Outlook Add-in from loading.

Customers who use Sent Items Update, the optional feature that replaces the sender's copy of a server-side email signature, need to reauthorize it for Microsoft Graph, or it stops updating sent items. Exclaimer's EWS article has details.

Google Workspace

Google Workspace also splits into server-side and client-side layers.

Server-side deployment for Google Workspace is set up in the Google Workspace Admin Console. A content compliance rule routes email to Exclaimer, and an SMTP relay service setting receives the email back from Exclaimer for delivery to recipients, according to Exclaimer's mail flow configuration article.

Client-side deployment synchronizes the email signature to Gmail, so the sender can see it while composing, unlike a pure server-side setup.

Can you use client-side and server-side email signatures together in a hybrid deployment?

server and client side email signature managment

Yes, a hybrid deployment runs client-side and server-side email signatures together. Client-side deployment inserts the email signature while the sender writes, and server-side deployment applies the email signature as mail routes through Exclaimer.

When both are configured in one Exclaimer subscription, the client-side email signature takes priority. If a client-side email signature is applied, a server-side email signature isn't. If a message goes out without a client-side email signature, for example, from a device where the client-side setup isn't in place, Exclaimer applies the server-side email signature instead. Exclaimer's support article "Information on using Client Side and Server Side signatures together in one subscription" describes the priority and fallback behavior.

How to choose which deployment method is best for you

Choose by the kinds of email your organization sends and the devices they're sent from. Server-side deployment applies the email signature to all but four kinds of email. Client-side deployment inserts the email signature only where the client-side setup is in place.

How much does device diversity matter?

If email comes from a narrow set of managed desktops, client-side deployment alone can cover it. If email routinely comes from mobile devices and mail apps where the client-side setup isn't supported, server-side or hybrid deployment covers it.

What are your coverage requirements?

A legal disclaimer, industry-specific footer, or brand element that has to appear on every outgoing email needs a plan for the four kinds of email server-side deployment can't reach.

Why does governance and audit-readiness matter more than initial setup?

Governance matters more than initial setup because each deployment method leaves some email without an email signature, and finding those emails is the work that starts after setup.

"Relying on individual behavior to enforce communication standards is one of the most common ways organizations get this wrong. Policies exist, but there is no mechanism to ensure they are applied in the same way across different teams, systems, or regions."

Ed Bodey portrait
Ed BodeyGeneral Counsel

Jim Turner, Exclaimer's Chief Operating Officer, says one customer needed three separate teams to roll out a single email signature. IT had to write the script, HR provided the content, and legal had to add the disclaimer, and it still rendered incorrectly on mobile. As Turner put it, "That's the definition of inefficient."

In Exclaimer's State of Business Email survey of 4,009 IT professionals in the UK, US, Germany, and Australia (Censuswide, April 2025), 33% reported that employees ignore email signature guidelines, and only 18% use centralized email signature management.

Exclaimer's Diagnostics Logs show, for each send, why an email signature was or wasn't applied and which email signature rules were evaluated. Exclaimer keeps seven days of log information.

Exclaimer Diagnostics Log screenshot

Why use Exclaimer for server-side, client-side, and hybrid deployment?

An email signature editor with a signature preview, configuration, and options for exporting, duplicating, and deleting signatures.

Exclaimer supports server-side, client-side, and hybrid deployment.

Server-side and client-side deployment are enabled for each email signature from the Manage Rules screen. Its Enable tab turns an email signature on for client-side deployment, server-side deployment or both, once each deployment is configured in the subscription, and the same screen holds the signature's Senders and Advanced Rules tabs.

Exclaimer's role-based access control has eight user roles: Owner, Admin, Editor, Analytics, Designer, Auditor, User Manager, and Finance. Finance is available only to Exclaimer's direct customers.

Meritus Gas Partners centralized email signature management across 20+ Microsoft 365 tenants. Allen Jezouit, Vice President of Product Management and Digital Marketing at Meritus, says the company uses Entra as the single source of truth for employee information, and Exclaimer keeps its email signatures up to date across every operating company.

Should you run server-side and client-side deployment together?

Server-side deployment leaves four kinds of email without an email signature, and client-side deployment applies an email signature only where the client-side setup is in place, so ideally you run both.

See how Exclaimer's device deployment works and compare it against what you're running today.

Not sure which deployment model fits? See it before you commit

Server-side, client-side, or hybrid: run a real email signature rule against your own Microsoft 365 or Google Workspace tenant and see how it behaves, no rebuild required if you change your mind later.

Book a demo

Not sure which deployment model fits? See it before you commit.

Server-side, client-side, or hybrid: run a real signature rule against your own Microsoft 365 or Google Workspace tenant and see how it behaves, no rebuild required if you change your mind later.

Hero Image

Frequently asked questions about server-side and client-side email signatures

Does changing from client-side to server-side deployment require changing MX records?

No. According to Exclaimer's guide to integrating with your existing setup, Exclaimer's server-side deployment for Microsoft 365 and Google Workspace needs no MX record changes. After processing, Exclaimer routes the email back to Microsoft 365 through the domain set in Mail Routing Domain, and Exclaimer recommends the tenant's .onmicrosoft.com domain for that setting. The MX record for that domain should specify a single Exchange Online server, because a multi-host MX record can cause non-delivery reports.

Not by default. The email signature appears in the sender's Sent Items folder only when an admin turns on Exclaimer's Sent Items feature. In Microsoft 365 that feature is Sent Items Update, which isn't guaranteed and doesn't work for Exchange on-premises mailboxes. In Google Workspace it is Sent Items, which adds a message to the sender's Sent Items folder and can increase mailbox size. In classic Outlook with Cached Exchange Mode enabled, the update can fail because the sent item may not have synced yet. If every sent item has to show the email signature, Exclaimer recommends client-side deployment.

The employee's outgoing email stops carrying an email signature until the add-in is reinstalled, unless a server-side layer is also in place to cover the gap. This is the core argument for hybrid deployment in any organization that can't guarantee every device stays correctly configured.

It does, but not in a way that breaks authentication for the recipient. Exclaimer's documentation on this behavior confirms that applying a server-side email signature modifies the message body, which invalidates any DKIM (DomainKeys Identified Mail) signature already on it. Exclaimer doesn't re-sign or apply DKIM itself. Instead, once Exclaimer has finished processing, the message is returned to Microsoft 365 or Google Workspace, which applies a fresh DKIM signature before the message leaves for external delivery.

In practice, this means DKIM signing happens after the email signature is added, not before, so external messages are DKIM signed by Microsoft 365 or Google Workspace. Internal messages may not always display DKIM headers.

Server-side deployment applies legal disclaimers by rule, and employees can't edit or remove them. Client-side deployment applies the email signature only where the client-side setup is in place. Exclaimer's disclaimers support legally compliant emails but don't constitute legal advice or guarantee compliance.

The Exclaimer Outlook Add-in can stop loading when Exchange Web Services (EWS), which Microsoft is retiring from Exchange Online, is disabled for the organization's tenant. Microsoft's phased disablement of EWS was due to begin on October 1, 2026, with permanent retirement scheduled for April 1, 2027, according to Exclaimer's support article on the add-in missing from the Outlook ribbon. The article says the add-in doesn't rely on EWS to insert email signatures, but Microsoft's Centralized Deployment, which delivers and loads centrally deployed add-ins, currently requires EWS to stay enabled. A tenant administrator can re-enable EWS. If the deployment method is set to Optional or Available, changing the deployment method to Default also resolves the problem of the add-in not loading. The article also says classic Outlook builds 19725.20000 and later no longer depend on EWS for add-in functionality, and the article recommends updating all users to that build or later.

Users can edit or delete a client-side email signature before the email is sent, even where some client restrictions are in place, but server-side deployment prevents users from changing the email signature, according to Exclaimer's support article on the differences between client-side and server-side features. Client-side deployment inserts the email signature in the mail client while the sender writes, and server-side deployment applies the email signature as mail routes through Exclaimer. Legal disclaimers that Exclaimer applies server-side by rule can't be edited or removed by employees.

Exclaimer recommends the Outlook Add-in for client-side email signatures in the new Outlook for Windows. The new Outlook for Windows uses Microsoft roaming signatures as the preferred way to synchronize email signatures between mail clients.