WiseStamp for IT › Exchange › Step 5 of 12 — Server-Side Routing
Plan requirement: Platform or Enterprise.
Topology applicability
Topology | Documented method |
Off-prem (Exchange Online) | Automated wizard or manual connectors + transport rules (below) |
Hybrid (outbound via Exchange Online) | Same — configured at the Exchange Online egress |
Pure on-prem (no M365) | Not supported — no plan — see "Pure on-prem routing" below |
How it works
Outbound mail leaves Exchange, routes to the WiseStamp server-side host, gets the signature appended, and is delivered. Applied in transit, so it’s consistent across devices.
Can run alone or in hybrid mode with the Add-In — server-side appends only when no WiseStamp signature is detected, preventing duplicates (Setup Overview).
Prerequisites
Step 1 complete: Entra ID connected (Identity & Employee Sync) — for off-prem/hybrid.
Microsoft 365 Global Administrator; Exchange admin access to Mail flow > Connectors and Rules.
DNS edit access for SPF/DKIM (Prerequisites Checklist).
Allowlist hostnames in place; IP list added if required (see Prerequisites Checklist).
Option A — Automated configuration (off-prem / hybrid)
In WiseStamp, click Integrations.
In Server-side, click Connect and select Microsoft Exchange.
Select I’m the Global Admin and click Connect.
Click Authorize, select the relevant domains, click Connect.
Add SPF records to domains lacking them, then Verify.
Copy the code and click Connect. In the Microsoft pop-up, paste the code, click Next.
Close the tab. The Management page appears.
Then validate (below) and configure signature rules (Signature Rules & Scoping).
Option B — Manual configuration (off-prem / hybrid)
Use when building the mail flow yourself. Contact WiseStamp support to enable manual configuration and obtain your routing code first. Must be done by a Global Administrator in the Exchange admin center.
Phase 1 — Connectors
Outbound connector:
Exchange admin center > Mail flow > Connectors > Add a connector.
From = Office 365; To = Your organization’s email server. Next.
Name: outbound ms.smtp.wisestamp.net. Next.
Use of connector: "Only when I have a transport rule…". Next.
Routing: enter routing code + .ms.smtp.wisestamp.net (e.g. RFw0rAriJyW.ms.smtp.wisestamp.net). +, Next.
Security restrictions: "Add the subject name…" = *.ms.smtp.wisestamp.net. Next.
Validation email: enter address, +, Validate (ignore validation-failure errors). Next.
Create connector, Done.
Inbound connector:
Mail flow > Connectors > Add a connector.
From = Your organization’s email server. Next.
Name: inbound outbound.smtp.wisestamp.net. Next.
Authenticating sent email: first radio button = outbound.smtp.wisestamp.net. Next.
Create connector, Done.
Phase 2 — Transport rules
Rule 1 — exclude out-of-office:
Mail flow > Rules > Add a rule > Create a new rule.
Name: Prevent Out of Office messages being sent to WS SMTP.
If: message type is Automatic reply.
Do: set header X-Wisestamphostedsignatures-Messageprocessed = true.
Next/Next/Finish; priority 0.
Rule 2 — route to WiseStamp:
Rules > Add a rule > Create a new rule.
Name: Identify messages to send to WS SMTP.
If: sender is located inside the organization.
Do: redirect to connector outbound ms.smtp.wisestamp.net; set header X-Wisestamphostedsignatures-Auth = your routing code.
Exceptions (4): message size ≥ 26624; header X-Wisestamphostedsignatures-Messageprocessed contains true; sender address matches <>; sender located outside the organization.
Next/Next/Finish; priority 1.
Enable: toggle both rules on, then in WiseStamp Integrations > Server-side > Manually > Connect.
Phase 3 — Disable RTF
Mail flow > Remote domains > Default > Edit text and character set > Use rich-text format = Never > Save.
Pure on-prem routing — not supported
Resolved: For pure on-prem Exchange Server (no M365), the connector/transport-rule method above (which uses the cloud Exchange admin center) does not apply, and there is no on-prem equivalent (no on-prem Send Connector/smart host, transport rule, or transport agent method). This is because employee sync is not supported for on-prem — no WiseStamp plan supports it, and employee sync is a prerequisite for deployment. Hybrid/Exchange Online routing is the minimum requirement.
Validation (validity check)
In WiseStamp, activate your user.
Send a test email; confirm the signature appears.
Test from a non-Outlook device (mobile) for cross-client coverage.
Confirm SPF and dkim=pass (Prerequisites Checklist, Troubleshooting Reference).
Keep several admins with Exchange admin center access for fast troubleshooting.
Full acceptance: Go-Live Checklist.
Emergency: disable routing
If mail stops, disable the routing rule so mail bypasses WiseStamp, then contact support:
Exchange admin center > Mail flow > Rules.
Open Identify messages to send to WS SMTP and toggle off.
To re-enable later, reconnect from Integrations (Troubleshooting Reference).