Your contact form "works", but does the email arrive? (the Microsoft 365 junk trap)

A contact form that shows "thanks, we'll be in touch" and still loses the enquiry is the most expensive bug on a website, because nobody sees it fail. The usual culprit: Microsoft 365 quietly files the form's email into Junk.

The silent failure

Your form submits. The visitor gets a success message. The server even sent the email. And it landed in the business's Junk Email folder in Microsoft 365 (or Google Workspace), where nobody looks. From the outside everything worked. In reality you just lost a lead, and you will lose the next hundred the same way until someone happens to check junk.

Why 365 in particular? Transactional mail, a message generated by a server, often "from" a visitor's address but actually sent by your website's host, trips exactly the signals spam filters are built to catch. Microsoft's filtering is aggressive by default and will not tell you it is quarantining you.

Test it end-to-end, including the junk folder

The only test that counts is a real submission you follow all the way to the inbox:

  1. Fill in the live form as a visitor would and submit it.
  2. Go to the destination mailbox and confirm the email landed in the Inbox, then check the Junk Email folder, and ask your Microsoft 365 admin to check quarantine at security.microsoft.com/quarantine. "It submitted fine" is not a test.
  3. Test from an outside address (not the same domain), because same-domain mail is often auto-trusted and hides the problem.
  4. Retest after any change to the form, the host, or the DNS.

If it is landing in Junk, do not just drag one message out, fix the trust signals below so it stops happening.

Follow an enquiry through every hand-off

  1. Visitor submits

    Validate the request and show an accurate success or failure message.

  2. Server records

    Retain the enquiry safely before attempting delivery, with access and retention controls.

  3. Mail provider sends

    Use a verified business-domain sender. Put the visitor's address in Reply-To.

  4. Inbox receives

    Check provider logs, Microsoft 365 trace and quarantine. A provider acceptance is not proof of inbox delivery.

This describes a reliability pattern, not a claim that every existing site already stores a second copy.

Get the mail trusted: SPF, DKIM, DMARC

Most form mail gets junked because it is not authenticated. Three DNS records tell Microsoft the mail is legitimately from your domain:

Get all three right and the mail arrives trusted. A common trap: the website sends through a different service than your normal email, so it passes your email's SPF but not the form's. Send through an authenticated path and include it in SPF. (Mail authentication is fiddly and provider guidance changes, so confirm SPF, DKIM and DMARC against Microsoft's current documentation.) These live in your DNS, mostly as TXT records: see which DNS record you actually need.

The reliability pattern we build into forms

Getting mail delivered is half the job. The other half is a form that resists spam without silently eating real enquiries:

If you would rather we built the form and the site so this never happens, that is exactly the kind of thing our Sydney web design work is set up to get right.

The short version: Microsoft 365 quietly junks contact-form email, so a form that "submits fine" can still lose every lead. Test end-to-end from an outside address, check the Junk Email folder, and ask your Microsoft 365 admin to check quarantine at security.microsoft.com/quarantine. Fix SPF, DKIM and DMARC so the mail is trusted. And build the form properly: honeypot, per-IP rate limit, a spam check that fails open, branded error pages, and a redirect to a thank-you page.

General guidance: mail authentication and filtering behaviour change over time; confirm SPF, DKIM and DMARC against your mail provider's current documentation.

Where this comes from

The primary sources behind the above, so you can check any of it yourself rather than take our word for it: