Outlook.com emails consistently delivered to Gmail Spam, all authentication passing

Open an Outlook.com in-app support case with complete Gmail message evidence; Microsoft can investigate its outbound service, but only Google controls Gmail’s Spam/Inbox verdict, and there is no public process for an Outlook.com user to request direct escalation to Google’s postmaster team.

What your results establish

Your SPF, DKIM, and DMARC results already rule out the usual authentication failure. Do not change those records.

Passing authentication does not guarantee Gmail inbox placement. Google also evaluates reputation, spam complaints, message characteristics, and recipient-level signals.^1^ Your cross-account and cross-recipient tests are consistent with broader filtering, but they do not by themselves prove whether the affected reputation belongs to an Outlook.com sending IP, domain, message pattern, or another Gmail classifier.

Microsoft previously documented an Outlook.com-to-Gmail reputation incident, but that entry concerned rejected messages from certain Outlook.com country domains with 550 5.7.1, and it was marked fixed in August 2024.^2^ It does not confirm the current Spam-folder symptom as a known Microsoft incident.

Submit an actionable Microsoft investigation

1. In Outlook.com, select Help on the top menu.
2. Search for the issue, then scroll to Still need help?
3. Select Yes to open an Outlook.com support request.^3^
4. Include:
   • UTC timestamps for several affected messages.
   • Sender and recipient domains, with personal addresses redacted.
   • Full Gmail Show original headers, especially Message-ID, Authentication-Results, Received, and any Google spam-related headers.
   • Confirmation that SPF, DKIM, and DMARC pass.
   • Confirmation that multiple unrelated Outlook.com accounts and multiple Gmail recipients reproduce it.
   • A plain-text control test with no signature, links, or attachments.
   • A request for review of the specific Outlook.com outbound IPs shown in the Received headers and correlation across the supplied message IDs.
5. Phrase the escalation request as:
   “Please investigate possible Outlook.com outbound pool/domain reputation affecting Gmail placement and escalate internally to the deliverability team if the message traces show a shared-service issue.”

Microsoft’s public sender-support submission form is specifically for mail being delivered to Outlook.com-family recipients, so it is not the correct route for Outlook.com-to-Gmail placement.^4^

Gmail-side actions

Ask affected recipients to:

• Open the message in Spam and select Report not spam.
• Add the sender to Google Contacts.
• Avoid creating a Gmail filter that merely hides the symptom until representative samples have been preserved.

For ordinary @outlook.com mail, Google Postmaster Tools is generally not actionable by the individual sender because its reporting is designed around domains the operator can verify.^5^

If the support case finds no Outlook.com-wide fault, Gmail’s classification remains the controlling result. Continue supplying fresh message IDs and headers rather than repeating authentication checks; those identifiers are what allow Microsoft to determine whether the affected messages shared an outbound server or route.

References

1. Email sender guidelines - Gmail Help - Google Help
2. Fixes or workarounds for recent issues on Outlook.com | Microsoft Support
3. How to get support for Outlook.com | Microsoft Support
4. Sender Support in Outlook.com | Microsoft Support
5. Email sender requirements and Postmaster Tools FAQ