If you've ever had an employee forget to add the legal disclaimer, use an outdated logo, or send an email from their phone with no signature at all, you've already run into the core problem this page is about: where your signature lives determines how much control you actually have over it. 

There are two ways ExSign adds signatures to outgoing emails. Understanding the difference will help you see why it matters for your organization. 

Client-side Signatures: Added Directly in Outlook 

This is the traditional approach: a signature is configured to appear inside each person's Outlook client and is inserted automatically when they compose a message.

What This Means for Admins 

• The user can see the signature while composing an email. 
• Supports only Microsoft Outlook on Windows. 
• Better user experience, visibility and control. 
• Users can edit their signatures and disclaimers; therefore, legal compliance isn’t enforceable.  
• Centralized templates, but client agent deployment is required. 
• Agent installation is not required on the Exchange Mailbox Server. It can be installed on any standalone workgroup machine. 
• Higher endpoint maintenance. 
• Best for organizations wanting accurate visible signatures in Outlook only. 

Server-side Signatures: Added on the Server

Here, the signature is applied centrally, by ExSign, as the email leaves your organization, regardless of what device or client the sender used. 

What This Means for Admins 

• The user cannot see the final signature while composing but can see it in their Sent Items folder if configured.
• Works with Outlook, OWA, Mac Mail, mobile devices, and all SMTP clients. 
• The sender doesn't have much control over email signatures. 
• Because the senders can't remove or skip disclaimers, legal compliance is very much enforceable. 
• Fully centralized management. 
• Agent installation is required on each Exchange Mailbox Server, even in a DAG. 
• Lower endpoint maintenance. 
• Best for organizations with mixed devices and mobile users.

Comparison