Information checked on 12 November 2026.
Have an invoice, quotation or important message to an Outlook.com, Hotmail, Live or MSN address bounced back? A recent hosting advisory highlights rejections involving email authentication. JM Restart can investigate the bounce, check the sending domain and help correct the configuration under an agreed scope.
What is happening
Our hosting provider reports that, since 5 November 2026, Microsoft has been rejecting some messages to its consumer email services with an error containing:
550 5.7.1 Message lacks SPF/DKIM/DMARC Auth Records
The advisory describes reports across different email providers. It identifies missing DMARC records in many cases, while also noting rejections where authentication is already configured. That makes the full bounce message important: the same next step will not resolve every delivery problem.
This concerns delivery to the recipient’s email service. The person receiving your message could be using Outlook, a web browser or another email app. Domain authentication is managed through the sender’s email service and DNS settings.
What to do if an important email bounces
- Keep the full delivery-failure message, including the error code and time. A screenshot of the subject alone may miss the useful diagnostic information.
- Tell your email administrator or support provider which address you sent from and which service sent it, such as your mailbox, website or invoicing system.
- Have the domain’s current SPF, DKIM and DMARC configuration checked before changing records.
- After any agreed correction has been verified, send a controlled test and check the result before resending the affected business messages.
For a time-sensitive invoice or appointment, contact the customer through another agreed method so they know you are investigating. Share bounce details privately with support; they can contain email addresses and message information.
What SPF, DKIM and DMARC do
Your domain is the part after the @ in an address such as [email protected]. The Domain Name System (DNS) publishes records that other services look up, including records used to check email authenticity.
| Check | What it does |
|---|---|
| Sender Policy Framework (SPF) | Lists the servers or services authorised to send for a domain. It checks the sending source against the envelope-sender domain, which can differ from the address a customer sees. |
| DomainKeys Identified Mail (DKIM) | Adds a digital signature to outgoing mail. The receiving service checks it using a public key published in DNS. |
| Domain-based Message Authentication, Reporting and Conformance (DMARC) | Connects authentication to the domain in the visible From address and publishes a policy for messages that fail. Reporting can also be configured. |
For DMARC to pass, a message needs a passing SPF or DKIM result that also aligns with the visible From domain. Alignment means the relevant domains match according to the policy’s rules. A provider’s separate sender requirements may require both SPF and DKIM as well. Cloudflare’s authentication overview explains these checks.
Authentication helps receiving systems assess a message. It does not guarantee that every genuine message reaches the inbox or that every authenticated message is safe. Our email threats, phishing and spoofing guide explains how these domain checks fit into wider email protection.

A missing DMARC record may be part of the problem
The hosting advisory recommends a basic DMARC policy where one is missing. Before adding it, have the applicable policy for the actual sending domain checked, including any relevant parent-domain policy if you send from a subdomain.
For a domain without an existing applicable DMARC policy, a basic starting record can look like this:
| DNS field | Example |
|---|---|
| Type | TXT |
| Name or host | _dmarc |
| Value | v=DMARC1; p=none; |
Some DNS panels expect _dmarc.example.com instead. Others append the domain automatically. The final record name needs checking so the domain is not added twice.
If a DMARC record already exists, leave it unchanged until it has been reviewed. Do not replace a working p=quarantine or p=reject policy with p=none simply to follow a generic example: that would weaken the policy you already have.
p=none requests no quarantine or rejection specifically because of the domain’s DMARC policy. It does not repair SPF or DKIM, force Microsoft to accept a message, or provide an enforcing anti-spoofing policy. This minimal example also contains no rua reporting destination, so it does not by itself arrange delivery of aggregate reports to you. A reporting and enforcement rollout needs its own configuration and review. Google’s DMARC guidance explains the policy and reporting options.
Add records where your DNS is actually managed
Your domain registrar, website host and email provider can be different companies. The change needs to reach the authoritative DNS service, meaning the service whose records the internet uses for your domain.
If your hosting service manages that DNS, its cPanel Zone Editor may be the right place. If Cloudflare manages it, use the Cloudflare DNS settings. A domain-provider portal is appropriate only when that provider also manages the domain’s DNS.
Editing a local cPanel zone will not update the internet’s records when another provider is authoritative. The cPanel Email Deliverability documentation explains this distinction. We can identify the correct location before making an agreed change.
Check Microsoft 365, Google Workspace and other senders too
For a custom domain using Microsoft 365, check that its required DKIM records are published and signing is enabled for that domain. Microsoft provides custom-domain DKIM instructions. Our Microsoft 365 setup and migration support covers the wider account, domain and email configuration.
For Google Workspace, publishing the DKIM key and starting authentication in the administrator console are separate steps. Verify that actual outgoing messages are signed. See Google’s DKIM setup guide.
Include every legitimate sender in the review: hosted mailboxes, website contact forms, newsletters, invoicing platforms, customer-management systems and devices that send email. A message from your normal mailbox can authenticate correctly while a website or business application using the same From address fails.
The configuration should support the services you use, with agreed changes that preserve existing mail routing and legitimate senders.
Is this the same as Microsoft’s bulk-sender rules
Microsoft separately documents stricter authentication requirements for high-volume senders and the related 550 5.7.515 rejection. Those requirements include SPF, DKIM and DMARC. Its bounce-message guidance explains that specific error.
The recent advisory quotes 550 5.7.1, so keep the exact wording from your own bounce. Do not assume that a low sending volume makes authentication irrelevant or that every 550 error has the same cause.
Resend failed messages after checking the result
A message that has received a final rejection should not be assumed to arrive later. The hosting advisory says the affected bounced messages will need resending; they will not be retried automatically. A temporary delivery delay is different, so check what the failure notice actually says.
Allow for cached DNS results to update, verify the published records and check a fresh test. Then review the messages that failed and resend those still needed, taking care to avoid duplicate business communications.
If authentication is correct but Microsoft continues rejecting messages, retain the full new bounce and ask the sending provider to investigate. The advisory notes that correctly configured domains can also be affected and suggests trying again later in those cases. Repeatedly changing valid DNS records can make diagnosis harder.
How JM Restart can help
We help businesses investigate email deliverability and configure SPF, DKIM and DMARC. This can include:
- Reading bounce messages and identifying the sending service involved.
- Checking published DNS records and the authentication results on an agreed test message.
- Reviewing Microsoft 365, Google Workspace and cPanel-hosted email settings.
- Checking website forms, invoicing systems and other authorised senders using your domain.
- Making agreed corrections, checking the outcome and helping escalate persistent problems to the relevant provider.
- Planning DMARC reporting and a gradual move towards enforcement where appropriate, under a separately agreed scope.
You do not need to transfer your domain or hosting to JM Restart to ask for help. Our cloud and business email support and web, email and domain services cover the wider setup. Work and ongoing responsibilities are agreed around your environment; no single DNS record guarantees delivery.
If you use a personal @outlook.com or @hotmail.com address, Microsoft manages that domain’s DNS. A sending business or its provider needs to review authentication for its own sending domain. We can help you understand the bounce and establish who should investigate.
Call 01473 527430 or email [email protected]. Tell us which service is sending, when the problem started and the exact error. Keep passwords and authentication codes out of your enquiry.

