Emails from oureasygame.com landing in Outlook/Hotmail junk folder despite perfect authentication

For Microsoft consumer services (Outlook.com/Hotmail), “perfect” SPF/DKIM/DMARC only prevents outright rejection; it does not guarantee inbox delivery. Once messages are accepted, Microsoft’s spam filters still score them based on:

• Overall sender reputation (domain + IP)
• Complaint rate and user engagement
• Bulk/marketing classification (Bulk Complaint Level – BCL)
• Content patterns and historical behavior

The behavior described—messages accepted by Microsoft, then consistently placed in Junk for all recipients—matches a reputation/content-based spam classification rather than an authentication problem.

From the documented causes of false positives:

• Legitimate email can be flagged as spam when email authentication passes but sender reputation or content triggers spam filters.
• Bulk or marketing-style email can be classified as bulk (gray mail) and routed to Junk based on BCL and user feedback, even with valid SPF/DKIM/DMARC.

Because this is a consumer (Outlook.com/Hotmail) scenario and the domain is hosted on a third‑party platform, the specific internal reputation score and exact rule that is causing Junk classification are not exposed. However, the supported remediation paths are:

1. Ensure authentication is consistently correct for all traffic
   The domain already passes SPF, DKIM, and DMARC, which aligns with Microsoft guidance that authenticated mail is less likely to be junked, but this must be true for every sending IP and sub-service used.
2. Improve sender reputation and reduce false positive signals
   • Keep lists clean (no sending to invalid or inactive addresses).
   • Avoid patterns associated with spam (excessive links, URL shorteners, image‑only messages, embedded scripts, etc.).
   • Maintain low complaint rates; recipients should mark wanted messages as “Not junk” in Outlook.com/Hotmail, which feeds Microsoft’s reputation systems.
3. Use allow/safe sender mechanisms on the recipient side
   For affected Outlook.com/Hotmail users:
   • Add the domain or specific addresses to Safe senders and domains in Outlook.com:
     Settings → Mail → Junk email → Safe senders and domains → Add safe sender → Save.
   • This prevents messages from that domain from going to Junk for those mailboxes.
4. Handle spam false positives via Microsoft’s processes
   For Microsoft 365/Defender for Office 365 tenants (business recipients), the documented approach is to:
   • Submit misclassified messages as “not junk” to Microsoft for analysis.
   • Create allow entries for the sender domain or address in the Tenant Allow/Block List when appropriate.
     While this specific case is Outlook.com/Hotmail, the same principle applies: repeated “Not junk” actions and any available feedback channels help Microsoft adjust classification.
5. Allow time for reputation to adjust
   Even with correct configuration, new or low‑volume domains/IPs can experience delivery issues until they build a positive reputation. Microsoft notes that sending reputation, list accuracy, and complaint rates are principal factors in filtering decisions.

In summary, the cause is Microsoft’s spam/reputation engine classifying the domain’s mail as spam/bulk after acceptance, not an authentication failure. Resolution requires a combination of: maintaining correct SPF/DKIM/DMARC for all sending infrastructure, improving sender reputation and list hygiene, having recipients mark messages as “Not junk” and/or add the domain to Safe senders, and allowing time for reputation changes to take effect.

References:

• Filter junk email and spam in Outlook
• Frequently asked questions - Anti-spam protection
• Resolve false positives for legitimate blocked emails in Microsoft Defender for Office 365
• External senders - Troubleshoot email sent to Microsoft 365
• Email authentication in cloud organizations