Troubleshooting
Start with the Mail authentication section on your organisation's page in the portal: every sending domain must show OK. Then run the script. It checks connectors, the rule, SPF, DMARC and DKIM in one go:
.\Test-InnovarroSignatures.ps1 -TestRecipient you@gmail.com
Then look at the Recent messages list on your organisation's page in the portal. Every message the relay handled is listed with its type (new, reply or forward), result and, where the message tells, the app it was sent from.
| Result | Meaning |
|---|---|
| applied | The relay added the signature. |
| skipped – signed by Outlook add-in (or … (marker)) | The add-in had already added it. Nothing to do. |
| skipped – relay signing off; not signed by add-in | Relay signing is switched off for your organisation (portal → Settings → Relay adds signatures), for example during an add-in-only pilot, and the add-in had not signed this message. It was delivered without a signature. |
| skipped – licence limit reached | All licensed senders for this month are used. The message was delivered without a signature. Contact Innovarro to add licences. |
| skipped – no matching signature | No enabled signature matches the sender (or the mail was internal and the signature is external only). |
| skipped – already processed | The message passed the relay before. |
| skipped – signed/encrypted/report, auto-submitted, calendar item, null sender (bounce) | Left untouched on purpose: changing these would break them. |
| skipped – no editable body part | The message has no text or HTML body the signature could be added to. |
| rejected – tenant mismatch | The message came from a different Microsoft 365 organisation than the sender's domain belongs to. It is refused and the sender gets a bounce. Contact support. |
| failed | The relay could not hand the message back. It asks Exchange Online to try again later, so the message is delayed, not lost. |
With the optional Sent Items update, signed messages also show a Sent Items result; that guide explains each one.
A result in this list only means the relay handed the message back. If Exchange Online then refuses it (see Mail bounces with 550 5.7.509 below), the sender gets a bounce and the message trace in Exchange Online shows why.
Common problems
The signature does not appear at all and the portal shows nothing The message never reached the relay. Check that the transport rule is enabled and includes the sender (in Exchange admin center → Mail flow → Rules), and that no earlier rule with Stop processing more rules matches the message. Message trace (Exchange admin center → Mail flow → Message trace) shows whether the message went through the Innovarro Signatures connector.
The portal shows skipped – no matching signature Check that a signature is enabled, that its Applies to includes the sender, and whether the message was internal while Also add to internal mail is off. For a department rule, the department must be spelled exactly as in Entra ID.
Wrong or missing name, title or phone number The details come from Entra ID. Correct them there and press Sync from Entra ID in the portal, or set an override under Users. A person who was just created appears after the next sync (hourly).
Two signatures The person also has their own signature in the mail app. Outlook with the add-in turns it off automatically; in other apps (Apple Mail, phone mail apps) the user has to remove it.
The add-in does not show up in Outlook Deployment can take up to 72 hours. Restart Outlook. Check in the Microsoft 365 admin center → Integrated apps that the user is in the assigned group. Older volume-licensed Outlook (2016–2021) does not support the add-in; the relay signs that mail instead.
Images do not show Images are embedded in every message, so they normally show straight away. If one is missing, check that it was uploaded as PNG, JPEG or GIF (not SVG), and in HTML mode that the image tag points to https://signatures.innovarro.cloud/assets/….
Connector validation fails
Check that the smart host is exactly relay.signatures.innovarro.cloud and TLS is set to trusted CA with that name. Contact support if
it still fails; the relay may not have your organisation activated yet. A validation that fails only on the test
step, while the connection succeeded, usually means the test recipient has no mailbox. Note that a successful
validation does not test SPF or DMARC: Microsoft's test message has no sender address.
Mail bounces with 550 5.7.509 Access denied, sending domain … does not pass DMARC verification
The relay handed the message back, but Exchange Online refused it: the domain's SPF record does not include the
relay and its DMARC policy is p=reject. Turn off the Innovarro Signatures transport rule (or run
Disable-InnovarroSignatures.ps1) so mail flows directly again, add ip4:102.213.7.195 to the SPF record
(Update SPF and turn on DKIM), wait until the portal's Mail authentication section shows OK,
then turn the rule back on. With p=quarantine the same problem sends mail to Junk instead.
Mail ends up in spam, or DMARC fails Check that the relay is in your SPF record and that DKIM is on for your domain (Update SPF and turn on DKIM), then look at the headers of a received message as described below.
A service's mail goes to Junk or bounces after a DMARC step A sender you use (newsletter tool, CRM, invoicing) does not pass DMARC for your domain. If the domain is hosted by Email & Domain Protection, the portal moves it back one step automatically within about 6 hours of the reports showing it. Fix the sender's DKIM or SPF as described in A sender fails DMARC, then tell Innovarro.
The Protection page shows no reports
Receivers send one report a day, so allow 24 hours after adding the records. Check that _dmarc returns a record
with rua=mailto:dmarc@innovarro.cloud (Resolve-DnsName _dmarc.contoso.com -Type TXT). If the domain shows
Waiting for CNAME under Policy rollout, the CNAME records are not visible yet, or the old TXT record is still
there.
Mail loops or gets the signature twice from the relay
The transport rule is missing the exception for the header X-Innovarro-Signature. Run
Install-InnovarroSignatures.ps1 again; it puts the exception back.
Reading message headers
Open a message received at an external mailbox and show its headers (Outlook: File → Properties → Internet headers; Outlook on the web: ⋯ → View → View message details; Gmail: ⋮ → Show original).
| Header | What to look for |
|---|---|
X-Innovarro-Signature |
applied; sig=… = signed by the relay. skipped; … with a reason = passed through. Missing = never reached the relay. |
X-Innovarro-Signature-Client |
applied = signed by the Outlook add-in. |
Authentication-Results (at the recipient) |
spf=pass, dkim=pass and dmarc=pass. |
X-MS-Exchange-Authentication-Results |
The check Exchange Online made when the message came back from the relay. spf=pass here means the relay is in your SPF record. |
When the relay adds a signature it removes the original DKIM signature (the body has changed), and Exchange Online signs the message again before it leaves. Recipients therefore see one DKIM result, from that last signature.
Microsoft's Message Header Analyzer shows headers in a readable form.
Emergency: stop everything
.\Disable-InnovarroSignatures.ps1
Mail flows directly again within a minute or two. See Pilot, roll out and roll back.
Contact
Contact Innovarro support with the sender, the recipient, the time of the message and, if you can, its full headers.