trustyourinbox

Forward us the bounce. We'll tell you why.

Every workspace has a private address. Forward a bounce, or a message that landed in spam, and we name the cause in plain English, with the evidence behind it and the fix.

Included: Lite and up. Compare plans

Product example. Illustration, not interactive.

Explore live demo

Your Paw Pantry order #10482 is confirmed

pawpantry.exampleForwarded by ops@pawpantry.exampleNov 1, 2:47 PM UTCReply emailed

What we found

Authentication5.7.26High confidenceAffects Gmail

Gmail refused this message at the door.

Microsoft 365 sent it without authenticating as pawpantry.example. Your own DMARC reports show the same pattern from this source over the last 14 days, affecting 158 messages. Before Oct 20, the same source passed DMARC.

Authorize Microsoft 365 for meShow me the change

Adds Microsoft 365 to your SPF record. It waits 5 minutes before applying. Cancel it from the domain page, or undo it once it has applied.

Also worth doing

  • Turn on custom DKIM signing in Microsoft 365Aligned DKIM survives forwarding. The DKIM page has the steps and the exact records to publish.Show me

pawpantry.example: p=reject, enforced. SPF found · no DKIM selectors found · MTA-STS not found. 2 open recommendations.View the domain

Evidence · 6 sources

  • Bounce decodeRejected by Gmail: unauthenticated mail. Gmail requires mail to pass SPF or DKIM (and, for bulk senders, both plus DMARC). This message arrived without passing authentication, so Gmail refused it. The server said: "550-5.7.26 Unauthenticated email from pawpantry.example is not accepted due to domain's DMARC policy. Please contact the administrator of pawpantry.example domain if this was a legitimate mail. To…".Rejected
  • Header chainThe message did not authenticate as pawpantry.example. DKIM signed as pawpantry.onmicrosoft.com.Fails
  • Your DMARC dataYour DMARC reports show 186 messages from this source in the last 14 days, 85% failing; the failing pattern started Oct 20 after previously passing.Degrading
  • Google Postmaster ToolsGmail measures spam rate 0.04% and authentication success 95%.Healthy
  • BlocklistsNo listings were found in 3 answered blocklist checks.No listings
  • SenderThe message left Microsoft 365, a sender already seen for your domain.Known sender

Ruled out

  • ReputationThe source was listed on 0 of 3 answered blocklists, and Gmail's measured spam rate is under its threshold.

How it works. Forward it as an attachment.

A plain Forward drops the headers we need. In Gmail, use a computer: the phone app cannot forward as an attachment.

  1. Copy your addressIt is on the Diagnose page and belongs to your workspace. Rotate it any time.
  2. Forward the messageThe bounce, or the message that landed in spam, as an attachment.
  3. Read the caseAbout a minute later: the cause, the evidence, what was ruled out, and the fix.

What it will not do. Evidence, not guesses.

  • Diagnose mail from a domain you have not added. Only the domains verified in your workspace.
  • Guess when the headers are missing. The case says what is missing and how to forward it again.
  • Keep the whole message. It is deleted once diagnosed, or within 7 days if it cannot be. The headers and the diagnosis stay for 90 days.

At a glance

Included
Lite and up
Cases a month
10 on Lite, 50 on Pro, unlimited on MSP. Only diagnosed cases count.
Causes
Authentication, reputation, forwarding, connection or routing, a recipient issue, receiver policy, or unclear
Evidence
The bounce code, the header chain, the receiver's verdict, your DMARC data, Google Postmaster Tools, TLS reports, blocklists, and the sender
Replies
Emailed to the person who forwarded it, if they are on your team or use one of your domains

Start with one domain. See it with your own data.

Free for one domain, no card. Add one DNS record and the first reports usually arrive within a day.

  1. Monitoring
  2. Quarantine
  3. Reject