Contact-form emails not arriving? Check the whole delivery path

1. Make one traceable test

Submit a harmless test through the public form. Use a distinctive message such as “Website test Tuesday 10:15” and record the exact time, time zone, page address and intended recipient. Use an email address you control and avoid customer data.

Note what the screen actually says. A validation error, a saved entry and a sent notification are different outcomes. Repeated tests without a timestamp or identifier are harder to follow through the logs.

2. Check whether the website captured it

Look in the form provider’s submissions area or the website’s own saved enquiries. Check its spam or filtered-submissions view too. Confirm that the test contains the fields you entered.

If it was saved, review the notification rule: is it enabled, does it apply to this form, and is the destination address correct? A provider may store an enquiry without sending a notification.

If the entry is missing, start with the form’s validation, spam handling, submission response and provider logs. Some forms do not store entries at all; in that case, use the submission and sending logs rather than treating an empty list as proof of failure.

3. Find the service that sends the email

The website host, form provider and business mailbox may be three different services. Identify which service creates the notification and check its event log for the test. Record the recipient, message ID, status and any rejection or error text.

Queued means there is more work to do. A rejection needs its specific explanation. A sending service’s “delivered” event may mean that the receiving mail server accepted the message; it does not show where a person will find it in their mailbox.

For applications sending through Microsoft 365, the supported method depends on the application and account configuration. Use its current provider instructions rather than enabling an older sign-in method or changing account protection to make a test pass.

Provider guidance: Microsoft: email options for applications.

4. Check who the notification claims to be from

A useful pattern is a From address on a domain your sending service is authorized to use, with the visitor’s address in Reply-To. Putting an arbitrary visitor’s Gmail or business address in From can make your service appear to be sending on behalf of a domain it does not control.

Check the actual sender setup and a message’s authentication results. SPF, DKIM and DMARC relate to the sending system and domain identity; adding a record without identifying that system can leave the real problem in place.

Use the sending provider’s current requirements and preserve other legitimate senders. Avoid replacing existing records, weakening the domain’s policy, or disabling spam protection as a first response to a missing notification.

Provider guidance: Google: contact-form delivery and authentication.

5. Follow the message at the receiving side

Search the recipient’s junk, spam and other folders, then review inbox rules and forwarding. An administrator can check quarantine and mail-flow rules where those features are available.

In Microsoft 365, message trace can show whether the service received, rejected, deferred or delivered the message. Google Workspace administrators can use Email Log Search to investigate the route and delivery status. Search with the test time, actual sender, recipient and message ID; allow for reporting delay.

If you find the message, inspect its detailed events rather than stopping at a summary label. If you cannot find it, confirm the search criteria and return to the sending service for evidence of where it was handed off.

Provider guidance: Microsoft: trace an email message.

6. Retest the complete enquiry journey

After a supported correction, submit the public form again. Confirm the saved entry where storage exists, the notification arriving in the intended mailbox, and a reply reaching the test sender. Check the real form rather than relying only on a mail plug-in’s test button.

Keep a direct contact email visible while you investigate. If the form stores submissions, review them so a missing notification does not leave an enquiry unattended.

For an investigation, collect the form and mail providers, the test time, destination, event statuses and redacted error text. Share access only when needed; passwords and private customer messages do not belong in the initial enquiry.

• The form captures the intended submission.
• The correct notification is created for the correct recipient.
• The message is found in the intended mailbox.
• A reply reaches the test sender and the result is recorded.

Provider guidance: Google: find messages with Email Log Search.