Exchange Online holds mail arriving over IPv6 to stricter rules: the sending address must have reverse DNS, and the message must pass SPF or DKIM. This one failed one of them.
550 5.7.25 Access denied, the sending IPv6 address [2001:db8::25] must have a reverse DNS record
1 other wording of the same rejection
Temporary, IPv6 without SPF or DKIM:
451 4.7.26 Access denied, a message sent over IPv6 [2001:db8::25] must pass either SPF or DKIM validation, this message is not signed
| Code | 550 5.7.25 |
| Sent by | Microsoft 365 and Outlook.com |
| Type | Permanent — not retried |
| Cause | Reverse DNS |
See what receivers see
Send one email to our test address and get back the sending server’s reverse DNS, TLS, authentication and blocklist results — the things this bounce is about.
What it means
Servers often start using IPv6 on their own once their host enables it, while their reverse DNS and SPF were only ever set up for IPv4.
Why it happens
- No PTR record for the server’s IPv6 address.
- The IPv6 address is not in SPF and the message is not DKIM-signed.
How to fix it
- Set reverse DNS for the IPv6 address with your provider.
- Add the address to SPF (ip6:) and sign with DKIM.
- Or send over IPv4 only until both are in place.
Sources
Message text and meaning checked on 25 September 2026 against these official sources:
- Email nondelivery reports (NDRs) and SMTP errors in Exchange Online — learn.microsoft.com