Sending, receiving, and organizing email in Outlook.com
The 550 5.7.1 … lacks SPF/DKIM/DMARC Auth Records (AS9031519) response is a server-level rejection before the message reaches your Hotmail mailbox, so adding Gmail addresses to Safe senders cannot override it.
Determine which side must resolve it
- From Gmail on the web, send a new test message to the Hotmail address.
- Select the From field.
- Ensure it is the sender’s actual
@gmail.comaddress—not a custom-domain address, alias, “send mail as” identity, mailing list, or forwarded address. - Keep the complete bounce message if it fails again.
- If the From address is a custom domain or alias, give the complete bounce to that domain’s administrator or email provider. They must check the sending domain’s SPF, DKIM, and DMARC configuration and alignment. Those records belong to the sender’s domain and cannot be repaired from your Hotmail account.^1^
- If the From address is a normal
@gmail.comaddress sent directly through Gmail, neither Gmail users nor Hotmail recipients manage the authentication records forgmail.com. With the sameAS9031519rejection recurring, report it to Outlook.com Support as a potentially incorrect authentication verdict.^2^
Contact Outlook.com Support
While signed in to the affected Hotmail account:
- Select Help on the Outlook.com top menu.
- Search for
AS9031519 Gmail rejected. - If the suggested articles do not resolve it, scroll to Still need help?
- Select Yes and submit the case.^3^
Include:
- The complete error:
550 5.7.1 Message rejected: Message lacks SPF/DKIM/DMARC Auth Records (AS9031519). - The Outlook protection-server hostname and UTC timestamp from the bounce.
- Confirmation that it was sent directly from an actual
@gmail.comaddress using Gmail. - Whether multiple unrelated Gmail accounts receive the same rejection.
- The screenshot, with all personal email addresses obscured.
Safe Senders only prevents successfully delivered messages from being moved to Junk; it does not affect mail rejected during the sending server’s connection.^4^ No further changes to that list are needed.
As a temporary workaround, use another receiving address until Microsoft or the custom-domain sender corrects the authentication rejection.
References