Author: Anthony Mitchell

  • How to Set Up SPF, DKIM and DMARC for Any Email Platform

    How to Set Up SPF, DKIM and DMARC for Any Email Platform

    Every email platform has its own screens and its own names for things, but the job underneath is always the same. You’re proving to Gmail, Outlook and Yahoo that the email really comes from you, using three DNS records: SPF, DKIM and DMARC.

    This guide walks through that job step by step. It works whether you send from Mailchimp, Brevo, HubSpot, Klaviyo, Google Workspace, Microsoft 365 or something else entirely. Where a platform does things differently, I’ll point it out.

    Before you start: list everything that sends as you

    This is the step most people skip, and it’s why so many setups fail later. Make a list of every service that sends email from your domain, not just your marketing platform. Typically that’s:

    • Your mailbox provider (Google Workspace or Microsoft 365)
    • Your marketing platform
    • Your CRM or sales tools
    • Your help desk or support system
    • Invoicing, booking or ecommerce systems
    • Your website’s contact forms

    Every one of these needs to pass authentication. Miss one, and when you turn DMARC up later, its emails will start going to spam or bouncing.

    You’ll also need access to your DNS. That’s usually wherever you bought your domain, or Cloudflare if you use it.

    Step 1: Authenticate your domain in each platform

    Every decent email platform has a setting for this, though the name varies: domain authentication, sending domain, branded domain or verified domain. Find it, add your domain, and the platform will give you a set of DNS records to publish. Usually these are CNAME or TXT records.

    Do this for every platform on your list. It’s what lets the platform sign your email with your own domain instead of its own.

    Step 2: Publish the DKIM records

    Most of the records your platform gives you are for DKIM. Copy them into your DNS exactly as shown. A few things to watch:

    • Some DNS panels add your domain to the end of the name automatically, so you end up with selector._domainkey.yourdomain.co.uk.yourdomain.co.uk. Check what your panel expects.
    • Long DKIM keys sometimes get split or cut off when pasted. If your platform offers a 2048-bit key, use it, and check the whole value went in.
    • Some platforms, like Microsoft 365, need you to switch DKIM on after the records are published. Publishing them isn’t enough.

    Then go back to the platform and click verify. DNS changes can take a few minutes to a few hours to show up.

    Step 3: Sort out SPF, but only where it’s needed

    This is where most people go wrong. Not every platform needs adding to your SPF record. SPF checks the bounce (Return-Path) domain, and many marketing platforms use their own bounce domain unless you set up a custom one. If yours does, adding it to your SPF record does nothing.

    Add a platform to SPF when it tells you to, or when you’ve set up a custom bounce domain on your own domain. Your mailbox provider (Google Workspace or Microsoft 365) always needs to be in there.

    Two rules matter more than anything else:

    Step 4: Check alignment

    DMARC doesn’t just want SPF or DKIM to pass. It wants them to pass for the same domain your subscribers see in the From address. That’s called alignment.

    In practice, DKIM alignment is the one that matters most. If step 2 is done properly, DKIM will be signed with your domain and will align. SPF only aligns if the platform uses a custom bounce domain on your domain. If you’re seeing SPF pass but DMARC fail, DMARC alignment explained covers why.

    Step 5: Add a DMARC record

    Once your senders are authenticating, publish a DMARC record. Start in monitoring mode:

    v=DMARC1; p=none; rua=mailto:[email protected]

    It goes in a TXT record at _dmarc.yourdomain.co.uk. The p=none part means nothing gets blocked yet. The rua part asks mailbox providers to send you daily reports showing every service sending as your domain and whether it passed. Those reports are how you find the senders you missed. Here’s how to read a DMARC aggregate report.

    Step 6: Test it

    Send a test email from each platform and check it passes. The quickest way is our free email spam test, which checks SPF, DKIM and DMARC along with your spam score. You can also open the email in Gmail, choose “Show original” and look for SPF, DKIM and DMARC all showing PASS.

    Step 7: Move to enforcement

    p=none is a starting point, not a finish line. Once your reports show all your real email passing, move to p=quarantine and then p=reject. That’s what actually stops someone sending email pretending to be you, and it’s needed for BIMI. A few weeks is typical to get there. DMARC p=none: what it means and how to move to enforcement safely walks through it.

    Notes for the most common platforms

    • Google Workspace: DKIM is generated in the Admin console and has to be switched on after you publish it. Full walkthrough: DMARC for Google Workspace.
    • Microsoft 365: your own domain isn’t DKIM-signed until you switch it on. Full walkthrough: How to set up DKIM in Microsoft 365.
    • Mailchimp, Brevo, HubSpot and Klaviyo: each has a domain authentication setting that gives you the records to publish. Step-by-step guides: Mailchimp, Brevo, HubSpot and Klaviyo.
    • Anything else: look for “domain authentication” or “sending domain” in the settings. If you can’t find it, or the platform can’t sign with your domain at all, that’s worth knowing before you move DMARC to enforcement.

    Common mistakes

    • Adding a second SPF record instead of merging into the first
    • Publishing DKIM records but never clicking verify or switching DKIM on
    • Forgetting the services outside marketing, like invoicing or your help desk
    • Adding a DMARC record with no rua address, so you never get the reports
    • Staying on p=none forever, which leaves your domain open to spoofing

    Want it done for you?

    I’ve set up SPF, DKIM and DMARC on most email platforms over 16 years, and it can often be done within an hour. See SPF, DKIM & DMARC setup, or run the free email spam test first to see where you stand.

  • Microsoft 365 Outage: What Happened to Outlook and Email, and How Big Is It?

    Microsoft 365 Outage: What Happened to Outlook and Email, and How Big Is It?

    If Outlook or Teams has been playing up since Thursday, it was not just you. Microsoft dealt with a large outage affecting Exchange Online, the service behind email for businesses on Microsoft 365, and a lot of email was delayed. Here is what we know now, who was affected, and what it means for your email.

    Updated Monday 16 November. Microsoft has marked the incident as resolved and promised a full Post-Incident Report, so check the Microsoft links further down for the latest.

    What happened

    Microsoft opened an incident called EX1550543 at 16:17 UTC (the same as UK and Irish time at this time of year) on Thursday 12 November, covering people unable to connect to their mailboxes in Exchange Online. The first message only mentioned the Americas, but Microsoft later confirmed that users in any region could be affected.

    Microsoft’s explanation changed as the incident went on. It first pointed to servers that had become unexpectedly unavailable after failing automated health checks, which pushed extra load onto the remaining servers. It has since given a preliminary root cause: an issue during an earlier network capacity upgrade, which surfaced following a recent network change. Microsoft has confirmed it was a technical issue, not a cyberattack and not related to AI or agents. A full Post-Incident Report is due to confirm the details.

    Who is affected

    The affected ways of getting to a mailbox included Outlook on the web, desktop Outlook, phones and API based integrations. So if you tried rebuilding your Outlook profile, that was not going to help, the problem was on Microsoft’s side.

    Other services that depend on Exchange were hit too, with reports covering Teams, SharePoint, Copilot and Defender XDR. Teams chats and calls could carry on working while calendar and scheduling features failed, as those rely on Exchange. If you use AI or automation tools that read your Microsoft mailbox or calendar, those will have been struggling as well. Businesses running a hybrid setup with an on-premises mail server could also see mail flow affected.

    It reached well beyond small businesses. In Ireland, the HSE warned of delayed emails and intermittent problems with video conferencing, and Cork City and County Councils reported disruption. In the UK, GPs, pharmacies, councils and schools were hit, and several police forces asked people to report crimes by phone instead of online. There was also a separate Teams incident earlier on Thursday, and Microsoft has not said if the two are related.

    What it means for your email

    The main thing is that delayed mail is not the same as lost mail. Microsoft extended its email timeout window to 48 hours so delayed messages do not expire while it catches up. Nothing so far suggests messages were lost, so expect late delivery rather than missing mail.

    If you are on the sending side, our advice is to leave your DNS and MX records alone. Changing them will not fix a capacity problem at Microsoft and can add work later. A few things are worth doing instead:

    • Check your bounce and deferral logs over the next few days, in case anything to Microsoft recipients got stuck.
    • If you have a campaign due to go out, consider holding it until the delays clear.
    • Once things settle, run an inbox placement test to confirm your email is landing where it should.

    If mail to Outlook, Hotmail or Live addresses keeps going to junk after the outage is over, that is a separate problem. Our guide to emails going to junk in Outlook or Hotmail covers what to check.

    Where things stand now

    Microsoft has marked the incident as resolved, with service restored. Recovery was not smooth. At one point a fix it was rolling out did not work as expected, and servers it had brought back could become unresponsive again once traffic returned. Some customers and regions took longer than others to recover, so if you are still seeing delayed email, check your own service health in the admin centre.

    Microsoft has promised a preliminary Post-Incident Report within two business days of the incident being resolved and a final one within five business days. For the latest, including the Post-Incident Report once it is published, go to Microsoft directly:

    How big is this?

    It is a big one. Nearly 130,000 reports came in on Downdetector at the peak on Thursday, across 74 countries. For comparison, the Outlook outage in March 2025 had around 37,000 reports. Reuters described Thursday’s disruption as lasting roughly 10 hours, but it carried on into Friday, and Irish coverage had it stretching beyond 18 hours at one point. An Exchange Online outage in September 2025 was described as mostly restored about 14 hours after Microsoft’s first post.

    Microsoft said in January it had more than 450 million paid Microsoft 365 commercial subscriptions. That is the size of the user base, not the number affected, but it shows how many businesses rely on one provider for email.

    Have a plan B for email

    A cloud provider going down is out of your hands, but a plan B is not. Even something as simple as a phone number or a second way to reach your key customers makes a difference when email is out.

    Need a hand with your email?

    If you would like us to look at how your email is set up, or you need help with anything in email or AI & automation, give us a shout. You can also send a test email to The Inbox Wizard Test to see whether SPF, DKIM and DMARC pass.

    ★★★★★ 5.0 from 12 Google reviews

  • DMARC for Google Workspace: A Small-Business Setup Guide

    DMARC for Google Workspace: A Small-Business Setup Guide

    If your business email runs on Google Workspace, setting up DMARC properly takes three records: SPF, DKIM and DMARC itself, in that order. Get the first two right and DMARC is straightforward to add. This guide is written for small and medium-sized UK and Irish businesses doing it themselves.

    Why bother?

    Gmail, Yahoo and Microsoft all now expect SPF, DKIM and DMARC from anyone sending at volume, and since late 2025 Gmail has been rejecting more mail that doesn’t comply. DMARC also stops criminals sending fake invoices that look like they came from your domain.

    Step 1: SPF

    Your domain should have one TXT record starting v=spf1 that includes Google:

    v=spf1 include:_spf.google.com ~all

    If other services send email as your domain (a newsletter platform, CRM or website form), their entries go into the same record. Never add a second SPF record. Our guide to merging SPF records explains why. And keep an eye on the 10-lookup limit.

    Step 2: DKIM in the Google Admin console

    Google Workspace doesn’t sign mail with your own domain until you set it up:

    1. In the Google Admin console, go to Apps → Google Workspace → Gmail → Authenticate email.
    2. Choose your domain and click Generate new record.
    3. Choose a 2048-bit key (use 1024 only if your DNS host can’t handle long records) and keep the default selector, google.
    4. Copy the host name (google._domainkey) and the TXT value, and add them as a TXT record at your DNS host.
    5. Back in the Admin console, click Start authentication.

    It can take up to 48 hours to start working, and the console may show a warning about DNS during that time. If you’ve added the record correctly, you can ignore it.

    Step 3: check both are working

    Send an email from your Workspace account to a Gmail address other than your own (you can’t test by emailing yourself). Open it, choose Show original, and check SPF and DKIM both say PASS, with DKIM showing your domain.

    Step 4: add your DMARC record

    Add a TXT record at _dmarc.yourdomain.co.uk:

    v=DMARC1; p=none; rua=mailto:[email protected]
    • p=none starts in monitoring mode, so nothing is blocked while you check everything is set up.
    • rua= is where daily reports are sent. Use a dedicated mailbox or a DMARC reporting service, because the volume adds up.

    Step 5: read the reports for a few weeks

    Your DMARC reports will show every service sending as your domain. Google Workspace should pass straight away. Anything else that fails needs SPF and DKIM set up in that service, signed with your domain so it aligns.

    Step 6: move to enforcement

    Once your reports show all your legitimate email passing, move to p=quarantine and then p=reject. That’s when DMARC actually protects your domain from spoofing, and it’s also a requirement for showing your logo with BIMI. Our guide to moving from p=none covers it step by step.

    Check your Google Workspace setup

    Send a test email from Google Workspace to The Inbox Wizard Test and it shows whether SPF, DKIM and DMARC pass, in seconds. When you’re ready to move to enforcement, our DMARC service handles the reports and gets you to p=reject safely.

    5.0 from 12 Google reviews

  • How to Set Up DKIM in Microsoft 365 (Step by Step)

    How to Set Up DKIM in Microsoft 365 (Step by Step)

    If your business email runs on Microsoft 365, there’s a good chance DKIM isn’t set up for your own domain. Microsoft signs mail from your yourcompany.onmicrosoft.com domain automatically, but not mail sent from your custom domain until you switch it on. Without it, DKIM can’t help your emails pass DMARC, which matters more every year as Gmail and Microsoft tighten their rules.

    Here’s how to set it up, step by step, in about 15 minutes plus waiting for DNS.

    Before you start

    • You need a Microsoft 365 admin account with access to the Microsoft Defender portal.
    • You need access to your domain’s DNS settings (your registrar or DNS host).
    • Your domain must already be added and verified in Microsoft 365.

    Step 1: open the DKIM settings

    In the Microsoft Defender portal, go to Email & collaboration → Policies & rules → Threat policies → Email authentication settings, then open the DKIM tab. You’ll see a list of your domains with their DKIM status.

    Step 2: get your two CNAME records

    Select your domain. If DKIM has never been set up, switch the toggle to Enabled. Microsoft will show an error explaining that the CNAME records are missing. That’s expected. The domain’s details panel then shows two records under Publish CNAMEs, which look like this:

    Host name:  selector1._domainkey
    Points to:  selector1-yourdomain-co-uk._domainkey.yourcompany.n-v1.dkim.mail.microsoft
    
    Host name:  selector2._domainkey
    Points to:  selector2-yourdomain-co-uk._domainkey.yourcompany.n-v1.dkim.mail.microsoft

    Copy the exact values from the portal rather than typing them yourself. Domains added before May 2025 use an older format ending in onmicrosoft.com, and the letter before -v1 varies between tenants.

    Step 3: add both CNAMEs to your DNS

    At your DNS host, create two CNAME records with those host names and values. You need both, even though only one is used at a time: Microsoft switches between them when it rotates keys.

    A common mistake: some DNS panels add your domain to the host name automatically, so enter just selector1._domainkey rather than the full domain if your panel works that way.

    Step 4: switch on signing

    Once DNS has updated (minutes to a few hours), go back to the domain in the DKIM tab and turn on Sign messages for this domain with DKIM signatures. The status should change to Signing DKIM signatures for this domain. If it still says CnameMissing, give DNS a little longer and check the records for typos.

    Step 5: move to a 2048-bit key

    Microsoft has historically created 1024-bit keys by default. Google recommends 2048-bit keys, and they’re stronger. In the domain’s details, choose Rotate DKIM keys and pick 2048 bits if offered (or use PowerShell: Rotate-DkimSigningConfig -Identity yourdomain.co.uk -KeySize 2048). A rotation takes around four days to take effect, and you need to rotate twice to move both selectors to 2048.

    Step 6: check it’s working

    Send an email from your Microsoft 365 mailbox to a Gmail or Outlook.com address and view the full headers. You’re looking for:

    DKIM-Signature: ... d=yourdomain.co.uk; s=selector1 ...
    Authentication-Results: ... dkim=pass header.d=yourdomain.co.uk

    If the signature shows d=yourcompany.onmicrosoft.com instead, signing isn’t on yet for your custom domain. Our guide to why DKIM fails covers the other common errors.

    Don’t stop at Microsoft 365

    DKIM in Microsoft 365 only covers mail sent from your Microsoft 365 mailboxes. Your newsletter platform, CRM, helpdesk and invoicing system each need their own DKIM set up for your domain. Your DMARC reports will show you which ones are still unsigned. And once everything aligns, you can move your DMARC policy to enforcement.

    Need a hand with Microsoft 365?

    Send a test email from Microsoft 365 to The Inbox Wizard Test to see whether SPF, DKIM and DMARC pass, or talk to us about setting up DKIM for Microsoft 365 and every other platform that sends as your domain.

    5.0 from 12 Google reviews

  • BIMI in the UK: VMC vs CMC, Trademarks and What You Need

    BIMI in the UK: VMC vs CMC, Trademarks and What You Need

    BIMI puts your logo next to your emails in the inbox, so they’re instantly recognisable and harder to fake. But the rules on what you need are confusing: certificates, trademarks, logo formats and DMARC policies. Here’s what a UK or Irish business needs in practice, and how to choose between the two certificate types, VMC and CMC.

    What is BIMI and how does it work?

    BIMI stands for Brand Indicators for Message Identification. It’s a DNS record that tells mailbox providers where to find your logo, so they can show it next to your emails in the inbox.

    When your email arrives, the receiving server checks that it passes DMARC. If it does, it looks up your BIMI record, fetches your logo and, at most providers, checks the certificate that proves the logo is yours. Only then does the logo appear.

    That’s why BIMI is more than branding. It only works for domains that have locked down their authentication, so the logo is a visible sign to your subscribers that the email really came from you. It also helps your emails stand out in a busy inbox.

    Gmail, Yahoo and Apple Mail all support BIMI, and more providers are adding it. Here’s what you need to get it working.

    Step 1: DMARC at enforcement

    This is the requirement that stops most businesses. Your DMARC policy must be p=quarantine or p=reject, applied to all of your mail. A p=none policy doesn’t qualify, and neither does a pct value below 100. Gmail also expects your subdomain policy (sp=) not to be set to none.

    If you’re still on p=none, start with our guide to moving to enforcement safely. Most of the work in a BIMI project is here, not in the logo.

    Step 2: your logo in SVG Tiny PS format

    BIMI needs your logo as a square SVG file in a specific profile called SVG Tiny Portable/Secure (SVG Tiny PS). A normal SVG exported from a design tool usually won’t pass validation, so expect to convert it. Keep the logo simple and centred, with a solid background, because inboxes show it small and often cropped to a circle.

    Step 3: choose a certificate, VMC or CMC

    Gmail and Apple Mail only show your logo if it’s backed by a mark certificate, which proves you have the right to use it.

    VMC (Verified Mark Certificate)CMC (Common Mark Certificate)
    Needs a registered trademark?YesNo
    Other requirementTrademark registered with an accepted office (UK IPO and EUIPO are accepted)Logo in continuous public use on your domain for at least 12 months
    GmailLogo plus blue verified tickLogo only, no tick
    Apple MailSupportedNot supported

    Which should you choose?

    • Already have a registered trademark for your logo? Choose a VMC. You get the tick in Gmail and support in Apple Mail.
    • No trademark, but you’ve used the logo for at least a year? A CMC gets your logo into Gmail without the time and cost of registering a trademark.
    • Neither? Get your DMARC to enforcement now, and revisit BIMI once your logo qualifies. Yahoo can show BIMI logos without a certificate for some senders, but don’t rely on that alone.

    Certificates are issued by a small number of approved certificate authorities and renewed every year. Expect a cost in the hundreds of pounds a year, and allow a few weeks for verification.

    Step 4: publish your BIMI record

    Once you have your SVG and certificate hosted on your website, add a TXT record at default._bimi.yourdomain.co.uk:

    v=BIMI1; l=https://yourdomain.co.uk/bimi/logo.svg; a=https://yourdomain.co.uk/bimi/certificate.pem

    The l= tag points to your logo and a= to your certificate.

    Step 5: be patient

    Mailbox providers decide when to show your logo, and they also look at your sending reputation. It can take days or weeks to appear, and good authentication and engagement remain a prerequisite.

    A note for Outlook users

    Microsoft’s Outlook doesn’t currently display BIMI logos, so recipients on Outlook and Microsoft 365 won’t see the logo even when everything is set up correctly.

    Is your domain BIMI-ready?

    BIMI starts with authentication. Send a test email to The Inbox Wizard Test to see whether SPF, DKIM and DMARC pass before you spend money on a certificate. We can also take you from p=none to a working BIMI logo.

    5.0 from 12 Google reviews

  • SPF Passes but DMARC Fails? DMARC Alignment Explained

    SPF Passes but DMARC Fails? DMARC Alignment Explained

    Your email headers show spf=pass. Maybe dkim=pass as well. And yet dmarc=fail. It looks contradictory, but it’s one of the most common results we see, and it comes down to one idea: alignment.

    Passing isn’t the same as aligning

    SPF and DKIM each check a domain, but not necessarily the domain your recipient sees.

    • SPF checks the Return-Path (also called the envelope sender or bounce address), a hidden address used for bounces.
    • DKIM checks the domain in the signature’s d= tag, which is whoever signed the email.
    • DMARC cares about the From address, the one people actually see.

    DMARC passes only when SPF or DKIM passes and the domain it passed for matches the From domain. That match is alignment.

    A typical example

    You send a newsletter from [email protected] using an email marketing platform. The headers show:

    Return-Path: [email protected]
    DKIM-Signature: d=platform-example.com; s=k1
    From: [email protected]
    
    spf=pass (mail.platform-example.com)
    dkim=pass (platform-example.com)
    dmarc=fail (yourdomain.co.uk)

    Both checks passed, but for the platform’s domains, not yours. Neither aligns with yourdomain.co.uk, so DMARC fails. In your DMARC reports this shows up as SPF and DKIM passing under auth_results but failing under policy_evaluated.

    Relaxed vs strict alignment

    Your DMARC record controls how closely the domains must match, with aspf for SPF and adkim for DKIM:

    • Relaxed (r, the default): subdomains count. DKIM signed by mail.yourdomain.co.uk aligns with a From address at yourdomain.co.uk.
    • Strict (s): the domains must match exactly.

    Most businesses should stay on relaxed. Strict alignment breaks easily and adds little protection for most senders.

    How to fix it

    Fix DKIM first

    Set up custom DKIM in every platform that sends as your domain: it’s usually called “domain authentication” or “branded sending domain”. Once the signature reads d=yourdomain.co.uk, DKIM aligns. This is the most reliable fix, because DKIM survives forwarding and SPF doesn’t. See why DKIM fails if it doesn’t verify.

    Add a custom Return-Path if you can

    Many platforms let you set a custom bounce domain, such as bounce.yourdomain.co.uk. With relaxed alignment, SPF then aligns too, which gives you a second route to DMARC passing.

    Watch for forwarding

    When email is forwarded, SPF usually fails because the forwarding server isn’t in your SPF record. Aligned DKIM is what keeps forwarded mail passing DMARC.

    A note on the 2026 DMARC update

    The updated DMARC standard published in 2026 (RFC 9989) changes how receivers work out your organisational domain, replacing a published list of domain suffixes with a lookup of DMARC records up your domain tree. For a typical business with a DMARC record at _dmarc.yourdomain.co.uk, alignment works exactly as before. Keep a DMARC record on your main domain and you’re covered.

    Why it matters

    Until every legitimate sender aligns, you can’t safely move your DMARC policy beyond p=none. Once you do, Gmail and Microsoft will start rejecting or junking the senders that don’t.

    Get every sender aligned

    Send a test email to The Inbox Wizard Test to see whether SPF, DKIM and DMARC pass for your domain, or let our DMARC service find every platform sending as your domain and get each one aligned before you move to enforcement.

    5.0 from 12 Google reviews

  • Gmail “550 5.7.26” Unauthenticated Email Error: How to Fix It

    Gmail “550 5.7.26” Unauthenticated Email Error: How to Fix It

    If emails to Gmail addresses are bouncing back with a 550 5.7.26 error, Google has rejected them before they reached the inbox or the spam folder. Since November 2025, Google has been permanently rejecting more non-compliant bulk mail rather than just slowing it down, so this error has become far more common.

    The good news: 5.7.26 is almost always an authentication problem, and authentication problems are fixable.

    What the error says

    The bounce usually contains one of two messages:

    550 5.7.26 This mail has been blocked because the sender is unauthenticated.
    Gmail requires all senders to authenticate with either SPF or DKIM.

    This means neither SPF nor DKIM passed for your email.

    550 5.7.26 Unauthenticated email from yourdomain.co.uk is not accepted due to domain's DMARC policy.

    This means your domain has a DMARC policy of quarantine or reject, and this email failed DMARC, so Gmail is enforcing your own policy.

    Why it’s happening now

    Google introduced its sender requirements in February 2024. All senders need SPF or DKIM, and bulk senders (around 5,000 or more emails a day to Gmail) need SPF, DKIM, DMARC, alignment, one-click unsubscribe and a spam complaint rate below 0.3%. Enforcement started gently with temporary errors, then tightened. From November 2025, Google moved to permanently rejecting more mail that doesn’t comply.

    How to fix it

    1. Find out which email is failing

    Look at the bounce: which address sent it, and from which system? It’s often not your main mailbox but something else sending as your domain: a CRM, an invoicing tool, a website contact form or an old marketing platform.

    2. Check SPF for that sender

    Make sure the service is covered by your SPF record, that you have only one SPF record, and that it stays within the 10-lookup limit. A broken SPF record fails for everything.

    3. Set up DKIM signed with your domain

    In the sending platform’s settings, find “domain authentication” or “DKIM”, add the records it gives you to your DNS, then verify. The signature should read d=yourdomain.co.uk. Our guide to why DKIM fails covers the usual problems.

    4. Check DMARC alignment

    For the DMARC version of the error, SPF or DKIM must not only pass but align: the domain they pass for must match the domain in your From address. A platform that passes SPF for its own bounce domain and signs DKIM with its own domain will fail DMARC even though both checks “pass”.

    5. Don’t fix it by weakening DMARC

    Dropping your DMARC policy back to p=none makes the bounces stop, but it also removes your protection against spoofing. Fix the sender instead. If you need breathing room while you do, read our guide to DMARC policies before changing anything.

    Other things that can trigger 5.7.x rejections

    If authentication is passing and you’re still being rejected, check that you send over TLS, that your sending IP has valid forward and reverse DNS, that marketing email has one-click unsubscribe, and that your spam rate in Google Postmaster Tools is below 0.3%.

    Confirm the fix

    Send a new test to a Gmail address, open it, choose Show original, and check that SPF, DKIM and DMARC all show PASS. Then keep an eye on your DMARC reports for any other service failing in the same way.

    Stop the Gmail bounces

    Send a test email to The Inbox Wizard Test and it shows whether SPF, DKIM and DMARC pass, with a score out of 100. If the bounces are coming from a platform you can’t pin down, we’ll find it and fix it.

    5.0 from 12 Google reviews

  • Emails Going to Junk in Outlook or Hotmail? A Guide for UK & Irish Senders

    Emails Going to Junk in Outlook or Hotmail? A Guide for UK & Irish Senders

    Your emails reach Gmail inboxes without trouble, but anyone on Outlook, Hotmail or Live says they found you in junk. It’s one of the most common problems we see from businesses in the UK and Ireland, and Microsoft’s filtering works differently enough from Gmail’s that the usual fixes don’t always carry across.

    Here’s the checklist we work through when a client’s mail is going to junk at Microsoft, in the order that usually finds the problem fastest.

    Why Microsoft matters so much in the UK and Ireland

    A big share of UK and Irish personal email addresses sit with Microsoft: hotmail.co.uk, live.co.uk, live.ie, outlook.com, msn.com and the rest. Plenty of people set up a Hotmail address years ago and never moved. If you sell to consumers, the Microsoft domains are often one of the biggest groups on your list after Gmail.

    It matters for B2B too. Lots of UK and Irish businesses, charities and public bodies run their email on Microsoft 365. Their mail goes through Microsoft’s filtering as well, and their IT team can add stricter rules on top. So when a quote, an invoice or a sales email “never arrived”, Microsoft is often where it went missing.

    Quick check: sort your list by domain and add up the Microsoft ones. That tells you how much of your email (and your revenue) depends on getting this right.

    First: junk or rejected?

    These are two different problems. If your email bounces with an error like 550 5.7.515 Access denied, Microsoft is refusing it outright because authentication failed. Our guide to fixing 550 5.7.515 covers that. If the email arrives but lands in the Junk Email folder, Microsoft accepted it but didn’t trust it enough for the inbox. That’s what this checklist is for.

    1. Authentication: SPF, DKIM and DMARC all passing and aligned

    Since May 2025 Microsoft has required SPF, DKIM and DMARC from high-volume senders to Outlook.com, Hotmail and Live addresses. Even below that volume, mail that fails authentication is far more likely to be junked.

    • Send a test to an Outlook.com address you own and check the headers for spf=pass, dkim=pass and dmarc=pass.
    • Make sure DKIM is signed with your domain, not your email platform’s. Why DKIM fails covers the usual causes.
    • Check you have exactly one SPF record, within the 10-lookup limit.

    2. Sending IP and domain reputation

    Microsoft weighs the reputation of the IP address your mail comes from heavily. If you send from a dedicated IP, register it with Microsoft’s Smart Network Data Services (SNDS), which shows how Outlook.com sees that IP, including complaint rates and spam-trap hits. If you’re on a shared IP through an email platform, your platform manages this, but a sudden drop in placement across all your mail can point to a shared-IP problem worth raising with them.

    Alongside SNDS, sign up to Microsoft’s Junk Mail Reporting Program (JMRP). It sends you a report each time an Outlook.com, Hotmail or Live user marks one of your emails as junk, so you can take them off your list before the complaints pile up. JMRP feeds are now linked to your SNDS account, and since early 2026 the reports no longer include the email body, so add a campaign reference to your headers if you want to know which send caused the complaint. On a shared IP, your email platform usually handles this for you.

    Also check your domain and IPs against the main blocklists. A listing doesn’t always cause junking at Microsoft, but it’s a strong warning sign.

    3. Complaints: people clicking “Report junk”

    Every time an Outlook user marks your email as junk, it counts against you. Common causes:

    • Emailing people who didn’t clearly sign up, or who signed up a long time ago and have forgotten you.
    • An unsubscribe link that’s hard to find, so people report you as junk instead.
    • Sending far more often than people expected when they signed up.

    Microsoft expects a working unsubscribe link in marketing email (and one-click unsubscribe from bulk senders), so make it easy to find.

    4. List hygiene

    Repeatedly sending to addresses that don’t exist tells Microsoft you aren’t maintaining your list. Remove hard bounces straight away, stop mailing people who haven’t opened or clicked in six to twelve months (or send them a short re-engagement campaign first), and never buy or rent lists. Old Hotmail addresses that have been closed are a common source of both bounces and spam traps.

    5. Consistent volume

    Microsoft is suspicious of sudden spikes. If you normally send 2,000 emails a week and suddenly send 40,000 to your whole database, expect a lot of it to land in junk. Build volume up gradually, especially from a new domain or IP. This is called warming.

    6. From and Reply-To addresses

    Use a real, recognisable From name and an address on your own domain that can receive replies. A noreply@ address on a domain that doesn’t match your website looks less trustworthy to filters and to people.

    7. Content and links

    Content matters less than reputation, but it still counts:

    • Avoid link shorteners and links to domains with poor reputation.
    • Keep a sensible balance of text and images. A single large image with little text is a classic spam pattern.
    • Make sure the domains in your links match the brand sending the email.

    8. Engagement

    Microsoft, like Gmail, notices whether people open, reply to and move your emails out of junk. Ask new subscribers to add you to their contacts, and focus regular sends on people who engage. Sending less to unengaged contacts often improves placement for everyone else.

    Test before you guess

    The quickest way to see where you stand is an inbox placement test: you send your campaign to a set of test mailboxes across Outlook, Hotmail, Gmail, Yahoo and corporate Microsoft 365, and see exactly where it lands. It turns “I think we’re going to junk” into a clear answer, and shows whether the problem is Microsoft-specific.

    Find out why you’re landing in junk

    Our deliverability audit runs inbox placement tests across Outlook, Hotmail, Gmail and Microsoft 365, checks your authentication and reputation, and gives you a prioritised list of fixes. Or start by sending a test email to The Inbox Wizard Test, which shows whether SPF, DKIM and DMARC pass.

    5.0 from 12 Google reviews

  • Why DKIM Fails: 6 Common Causes and How to Fix Them

    Why DKIM Fails: 6 Common Causes and How to Fix Them

    DKIM is the part of email authentication that does the heavy lifting. It survives forwarding, it’s what most marketing platforms rely on to pass DMARC, and Google, Yahoo and Microsoft all expect it from bulk senders. So when your headers or DMARC reports show dkim=fail, it’s worth fixing quickly.

    Here are the six causes we see most often, how to spot each one and how to fix it.

    First, a 30-second refresher

    When you send an email, your platform adds a DKIM signature: a header with an encrypted fingerprint of the message, the signing domain (d=) and a selector (s=). The receiving server looks up the public key at selector._domainkey.yourdomain.co.uk and checks the fingerprint still matches. If the key can’t be found, or the message has changed since it was signed, DKIM fails.

    To find which cause you’re dealing with, open the full headers of a failing email and look at the Authentication-Results line. The wording after dkim=fail (or dkim=permerror) usually points straight at the problem.

    Why do you need DKIM as well as SPF? Because they protect different things. SPF checks which server sent the email, and it usually breaks when an email is forwarded. DKIM signs the email itself, so the signature travels with the message and survives forwarding. It also proves the content wasn’t changed on the way. Together with DMARC, they make it very hard for anyone else to send email as you.

    1. The DKIM record is missing or published in the wrong place

    What you’ll see: “no key for signature”, “key not found” or dkim=permerror.

    The receiving server went to look up your public key and found nothing. Usually one of these has happened:

    • The record was never added, or was added to the wrong domain.
    • The DNS panel added your domain to the name automatically, creating s1._domainkey.yourdomain.co.uk.yourdomain.co.uk.
    • The selector in the record doesn’t match the one in the signature (for example, s1 published but s2 used).

    Fix: Compare the s= and d= values in the email’s DKIM signature with the record in your DNS, and look the record up with a DKIM checker to confirm it resolves.

    2. DKIM was set up in DNS but never switched on

    What you’ll see: the email is signed by your platform’s domain instead of yours, or not signed at all.

    Most platforms make you add the DNS records and then click “verify” or “enable” in their settings. Microsoft 365 is the classic example: you publish two CNAME records (selector1._domainkey and selector2._domainkey) and then enable DKIM signing for the domain in the Defender portal. Skip that last step and Microsoft keeps signing with its own default domain.

    Fix: Go back into each platform’s domain authentication settings and confirm DKIM signing shows as active for your domain.

    3. The key has been broken by your DNS panel

    What you’ll see: “invalid public key”, “key syntax error” or dkim=permerror.

    DKIM keys are long. A 2048-bit key is over 400 characters, and a single DNS text string can only hold 255. Some DNS panels split long values automatically and some don’t. Copy-and-paste can also add stray spaces, line breaks or extra quotation marks, or cut off the end of the key.

    Fix: Republish the record exactly as your platform provides it. If your DNS panel struggles with long values, use the CNAME option many platforms offer instead. The platform then hosts the key and keeps it up to date.

    4. The email was changed after it was signed

    What you’ll see: “body hash did not verify” or “signature did not verify”.

    DKIM’s fingerprint covers the message body and key headers. If anything changes them on the way, the fingerprint no longer matches. Common culprits:

    • Email security gateways that rewrite links or add “external sender” banners
    • Mailing lists and Google Groups that add footers or change the subject line
    • Signature or disclaimer tools that add text after sending
    • Forwarding services that alter the message

    Fix: Make sure any tool that modifies outgoing mail does so before DKIM signing, not after. For mailing lists you don’t control, there’s little you can do. That’s normal, and it’s one reason DMARC passes if either SPF or DKIM passes and aligns.

    5. The key was rotated or removed

    What you’ll see: DKIM was passing and suddenly fails across all mail from one service.

    Platforms periodically switch to new keys, and people tidying DNS sometimes delete an “unrecognised” _domainkey record that was still in use. If a key is replaced before the platform stops using it, signatures fail until things catch up.

    Fix: Never delete a _domainkey record without checking your DMARC reports to see whether anything still signs with that selector. Where possible, use CNAME-based DKIM so the platform handles rotation for you. And check you’re on 2048-bit keys: Google recommends them, and some older setups still use weaker 1024-bit keys.

    6. DKIM passes, but not for your domain

    What you’ll see: dkim=pass in the headers, but DKIM shown as failing in DMARC reports.

    This one catches out a lot of people. DKIM can pass perfectly well for the platform’s own domain (for example d=platform-example.com). DMARC, though, only counts DKIM when the signing domain matches your From domain. That’s called alignment. Without it, DKIM is technically working but does nothing for your DMARC result or your sender reputation.

    Fix: Set up custom DKIM (often called “domain authentication” or “branded sending domain”) in every platform that sends as your domain, so the signature reads d=yourdomain.co.uk. This matters even more as you move your DMARC policy from p=none to enforcement.

    A quick DKIM health check

    • Every service that sends as your domain signs with d=yourdomain.co.uk.
    • Every selector in use has a working record in your DNS.
    • Keys are 2048-bit where the platform supports it.
    • Your DMARC reports show DKIM passing and aligned for all legitimate sources.

    Get your DKIM sorted

    DKIM problems are fiddly to track down across several platforms, and they quietly hold back your inbox placement until they’re fixed. Start by sending a test email to The Inbox Wizard Test, or let us find every service sending as your domain and set up aligned, 2048-bit DKIM for each one.

    5.0 from 12 Google reviews

  • Two SPF Records? Why It Breaks Your Email and How to Merge Them

    Two SPF Records? Why It Breaks Your Email and How to Merge Them

    Here’s a mistake that breaks email for thousands of businesses, and it usually starts with good intentions. You sign up for a new email platform, it tells you to “add this SPF record to your DNS”, and you add it. The problem is that you already had one.

    A domain can only have one SPF record. With two, SPF doesn’t check both and pick the best result. It fails completely.

    What is SPF, and what does a record look like?

    SPF, or Sender Policy Framework, is a list of the servers allowed to send email for your domain. You publish it as a TXT record in your DNS. When an email arrives claiming to be from you, the receiving server checks whether it came from one of the servers on that list.

    A typical SPF record looks like this:

    v=spf1 include:_spf.google.com include:sendgrid.net ~all

    It always starts with v=spf1. Each include: adds a service that sends for you, such as Google Workspace or your email platform. It ends with an all rule, which says what to do with everything else: ~all (soft fail) is the usual choice, and -all (hard fail) is stricter.

    SPF on its own doesn’t stop spoofing, because it checks a hidden “envelope” address rather than the From address your subscribers see. That’s why it works alongside DKIM and DMARC. But it’s the first thing mailbox providers check, and the easiest one to break by accident, which is what the rest of this guide is about.

    Why two SPF records break SPF

    The SPF standard (RFC 7208) is explicit: a domain must not publish more than one SPF record. When a receiving server looks up your domain and finds two TXT records that start with v=spf1, it returns a PermError (“permanent error”) and stops. Neither record is used.

    In practice that means:

    • Every email from your domain fails SPF, including your normal day-to-day email from Microsoft 365 or Google Workspace.
    • DMARC can only pass through DKIM. Any service that isn’t signing with DKIM for your domain will fail DMARC.
    • Emails to Outlook and Hotmail can be refused with 550 5.7.515 errors, and once your DMARC policy is quarantine or reject, failing emails go to spam or bounce.

    How to check if you have two SPF records

    Look at the TXT records on your root domain (the one shown as @ or left blank in most DNS panels). Count how many start with v=spf1. More than one means you have the problem.

    Common giveaways:

    • One record from your mailbox provider and a second added later by a marketing, CRM or helpdesk platform.
    • An old record left behind after moving from one email host to another.
    • A record added by your web host or domain registrar automatically, alongside the one you created.
    • A v=spf2.0 record (an old Microsoft “Sender ID” format). It isn’t a second SPF record in the same sense, but it’s obsolete and worth removing while you’re there.

    Send a test email to The Inbox Wizard Test and it shows whether SPF passes or fails for your domain. The link is at the end of this post.

    How to merge them into one

    Say you have these two records:

    v=spf1 include:spf.protection.outlook.com -all
    v=spf1 include:_spf.your-email-platform.com ~all

    Merging them takes four steps.

    1. Keep one v=spf1 at the start

    Every SPF record starts with v=spf1, exactly once.

    2. Combine all the mechanisms in the middle

    Take every include:, ip4:, ip6:, a and mx from both records and list them once each, separated by spaces. Remove duplicates.

    3. Keep one all at the end

    Choose a single ending. ~all (soft fail) is the common choice while you’re setting things up, and -all (hard fail) is stricter. Don’t include both, and make sure all is the last thing in the record. Anything after it is ignored.

    4. Delete the old records and publish the merged one

    v=spf1 include:spf.protection.outlook.com include:_spf.your-email-platform.com ~all

    Publish this as the only SPF TXT record on your root domain, then delete the others.

    Before you merge: two things to check

    Do you still need every entry?

    Merging is a good moment to remove services you no longer use. It’s also worth checking whether a platform needs to be in your SPF at all. Many marketing platforms use their own bounce domain, so your SPF isn’t what they’re checked against. They pass DMARC through DKIM signed with your domain instead.

    Will the merged record go over 10 lookups?

    Combining two records often pushes you over SPF’s 10-lookup limit, which causes a different PermError. If that happens, our guide to fixing “too many DNS lookups” covers how to trim it back.

    What about subdomains?

    The one-record rule applies per domain name. yourdomain.co.uk and news.yourdomain.co.uk can each have their own SPF record. That’s a useful way to give a marketing platform its own SPF without touching the record your main email depends on.

    After you’ve fixed it

    • Wait for DNS to update (usually minutes, occasionally a few hours).
    • Re-check that exactly one v=spf1 record exists.
    • Send a test email from each service and check the headers show spf=pass.
    • Keep an eye on your DMARC reports for a week to confirm everything is passing.

    Test your SPF in seconds

    Not sure whether your SPF is working? Send a test email to The Inbox Wizard Test and it shows whether SPF passes for your domain. If you’d rather someone just sorted it, we’ll merge your records, trim anything you no longer need and confirm every service still passes.

    5.0 from 12 Google reviews