Can You Manage Email Signatures Without Exclaimer? Pros and Cons

TL;DR

Yes, you can run email signatures without Exclaimer. If you’re still at the “do we even need this?” stage, start here. It explains why the problem exists at any size. If you’re past that and want the alternatives, you have three DIY routes: Outlook signatures, an Exchange transport rule, and Google Workspace canned responses or per-user GW settings. Each one trades licence cost for a different flavour of pain. Here’s what each one costs you in tickets and brand drift, and when DIY actually holds up.

Option 1: Outlook signatures, set per user

The cheapest route. The user opens Outlook, pastes some HTML into File → Options → Mail → Signatures, sets it as the default for new mail and replies, and you’re done.

Free. No licence, no connector, nothing to break in mail flow.

It doesn’t scale. Outlook stores the signature on the device, per profile. So:

• It does not render in Outlook on the Web. OWA has its own signature setting, in a different place, with a different rendering engine. Set both, hope they match.
• It does not render on the iPhone Mail app, the Outlook for iOS app, or the Gmail app pointed at the M365 mailbox. Each one has its own signature field. Each one is set per user.
• It is gone the moment the user gets a new laptop, rebuilds Outlook, or moves to a new tenant. We have rebuilt Outlook profiles after a corruption and watched a year of carefully-pasted signatures disappear in seconds.
• Replies and forwards stack the signature awkwardly because there is no central rule stripping prior blocks.
• You have no central control. The MD has whatever Outlook gave him in 2019. Sales has the new logo. Reception has a smiley face.

Workable for a five-person shop. Anything bigger and the IT support hours cost you more per year than the licence would have.

Option 2: Exchange transport rule with HTML

Server-side, no client involvement. You write a transport rule in Exchange admin: “if the sender is in this group, append this HTML to the body of outgoing mail.” The HTML is your signature.

Works regardless of device. Everything that goes out gets a signature, no per-user setup, and it ships with M365 at no extra cost.

It is awful to live with.

• No design tools. You are hand-editing HTML in a tiny text box in the Exchange admin centre. Tabular layouts, fallback fonts, image embedding via base64 or hosted URLs: all manual.
• The signature appends as plain HTML at the bottom of the message body. It does not handle replies. Five-message thread, five copies of the signature stacked.
• Banner campaigns are a nightmare. Want a Black Friday banner with start and end dates? You are scheduling rule activation manually, hoping nobody forgets in mid-January.
• Updating it for a hundred users means editing one rule, but updating it for fifty users in the sales team and a different version for the support team means duplicating and maintaining multiple rules.
• No analytics. No A/B testing. No idea whether anyone clicks anything in the signature.
• No equivalent on Google Workspace. If you are mixed-platform, the rule lives only on the M365 side and you are still on the hook for the GW half.

A transport rule is fine for a single compliance footer (“This email and any attachments are confidential…”). It is not fine for a marketing-active signature.

Option 3: Google Workspace canned responses or per-user GW signatures

GW’s options are slimmer.

Per-user signature in Gmail settings: same problem as Outlook. The user sets it themselves. It does render across web and mobile, because Gmail is consistent that way, which is one point in GW’s favour. But there is no central control, no template push, no banner.

Append-footer admin setting: at the OU level, you can add an organisational footer to all outbound mail. This is the closest thing GW has to a transport rule. Same limitations: plain HTML, no design tools, no banner scheduling, stacks awkwardly on replies.

Canned responses: a per-user templating feature. Useful for sales sequences, useless for centralised brand.

The OU-scoped append-footer is your best free option in GW. It works for a compliance disclaimer. It does not work for marketing.

When DIY is fine, and when it isn’t

DIY is fine when:

• You are under 10 mailboxes.
• You have one brand, one domain, no aliases.
• You don’t run banner campaigns from the signature.
• You don’t have a regulated compliance disclaimer that needs to be guaranteed to ship on every outbound mail.
• Staff are technically disciplined and do as they’re told the first time. (you know they won’t)

DIY breaks down when:

• Marketing wants to schedule a campaign banner.
• Compliance wants the FAIS / POPIA / HIPAA disclaimer to be unbypassable.
• You have multiple domains, multiple brands, or send-as aliases.
• You are mixed M365 / GW.
• You want analytics on signature CTAs.
• You have ever fielded the support ticket “my signature disappeared”.

By month three, most growing organisations regret the DIY call. By month six, someone is quietly pricing Exclaimer.

So can you do signatures without Exclaimer?

Yes. The DIY routes work, in narrow conditions. The trade-off doesn’t change: licence cost goes down, support and brand-drift cost goes up. If you’re small, single-brand, single-domain, and the staff actually do what IT asks, run the GW append-footer or an Exchange transport rule and move on.

If you have a marketing function, a compliance officer, or more than one domain, buy the licence. The maths works out inside a quarter.

Want to know what your current setup is actually costing you in tickets and brand consistency? 20-minute signature audit, no commitment.