Step 3: Route mail through the relay
Three objects in Exchange Online send your users' mail to the relay once and accept it back:
| Object | Name | Purpose |
|---|---|---|
| Outbound connector | Innovarro Signatures | Delivers to relay.signatures.innovarro.cloud over TLS, used only by the rule below |
| Inbound connector | Innovarro Signatures - return | Accepts signed mail back, recognised by the relay's TLS certificate |
| Transport rule | Innovarro Signatures | Sends mail from your users to the outbound connector, unless it has already been signed |
Before you start, make sure that:
- your tenant is connected and activated, and at least one signature is enabled in the portal;
- every domain you send from allows the relay in its SPF record (Update SPF and turn on DKIM), and the Mail authentication section on your organisation's page in the portal shows OK for each domain.
Do not skip the SPF step. Exchange Online checks SPF and DMARC on the mail the relay hands back. If a domain with DMARC
p=rejectdoes not allow the relay, mail from the routed users bounces with 550 5.7.509; withp=quarantineit goes to Junk. Microsoft's connector validation does not catch this.
With the script (recommended)
Download Install-InnovarroSignatures.ps1.
Open PowerShell in the download folder. On Windows, allow the downloaded script to run:
Unblock-File .\Install-InnovarroSignatures.ps1Start with one or two pilot users and an external mailbox you can read (for example a personal Gmail address):
.\Install-InnovarroSignatures.ps1 -PilotUsers alex@contoso.com -TestRecipient you@gmail.comSign in as an Exchange Administrator when asked. The script creates both connectors and the transport rule, limits the rule to the pilot users, puts it after your existing rules and validates the outbound connector.
To see what the script would do without changing anything, add -WhatIf.
Options
| Parameter | Effect |
|---|---|
-PilotUsers a@x.com,b@x.com |
Only these senders go through the relay |
-PilotGroup "Signature pilot" |
Only members of this distribution or mail-enabled security group |
-AllUsers |
Everyone in the organisation |
-ExcludeSenders scanner@x.com |
Never route these senders (scanners, no-reply, payment mailboxes) |
-ExternalOnly |
Route only mail to external recipients; internal mail stays direct |
-TestRecipient you@gmail.com |
Validate the outbound connector with a test message |
| (no scope) | Connectors are created, the rule is created disabled |
Run the script again with different options to change the scope. It updates the existing objects.
By hand in the Exchange admin center
Use this if you cannot run PowerShell. Open admin.exchange.microsoft.com → Mail flow → Connectors.
Outbound connector
- Add a connector: from Office 365 to Partner organization. Name:
Innovarro Signatures. - Use of connector: Only when I have a transport rule set up that redirects messages to this connector.
- Routing: Route email through these smart hosts →
relay.signatures.innovarro.cloud. - Security: Always use TLS → Issued by a trusted certificate authority (CA) → And the subject name or
subject alternative name matches this domain name:
relay.signatures.innovarro.cloud. - Validation: enter an external address. Validation sends a test message through the relay and should succeed. It proves the connection and TLS only: its test message has no sender address, so SPF and DMARC are not tested.
- Create the connector.
Inbound connector
- Add a connector: from Your organization's email server to Office 365. Name:
Innovarro Signatures - return. - Authentication: By verifying that the subject name on the certificate that the sending server uses to
authenticate with Office 365 matches this domain name →
relay.signatures.innovarro.cloud. - Leave Retain internal Exchange email headers on.
- Create the connector.
Transport rule: Mail flow → Rules → Add a rule → Create a new rule
| Setting | Value |
|---|---|
| Name | Innovarro Signatures |
| Apply this rule if | The sender is → your pilot users (later: The sender is located → Inside the organization) |
| Do the following | Redirect the message to → the following connector → Innovarro Signatures |
| Except if | A message header matches these text patterns: header X-Innovarro-Signature, pattern . |
| Except if | The message type is → Calendaring |
| Rule mode | Enforce |
| Stop processing more rules | Off |
Save the rule, then move it to the bottom of the list so your existing rules run first.
The exception for
X-Innovarro-Signatureis essential. The relay adds this header to every message it has handled. Without the exception, the signed message would be sent to the relay again.
Check
.\Test-InnovarroSignatures.ps1 -TestRecipient you@gmail.com
Then send a real message from a pilot user to an external mailbox, check that it arrives with the signature and that the portal lists it under Recent messages, and continue with Pilot, roll out and roll back.