Skip to content

Job template · Website and landing pages

Job template: fix a contact form that stopped sending emails

By The Microployed teamUpdated 2 min read

The short answer

Post this when your contact form says the message went through but nothing reaches your inbox. A pro finds where the email stops, routes form mail through a proper sending service with a From address on your own domain, and proves the fix with test submissions that land in your inbox instead of spam.

Ready-to-post scope

Find out why our contact form stopped sending emails and fix it

Typical time for a pro: 45 minutes to 2 hours

Our website contact form shows a success message, but the notification emails stopped arriving in our inbox. Find where the messages are failing, set up reliable sending through an SMTP service or our email provider with a From address on our domain, and confirm that form submissions reach our inbox and not spam.

Check first

  • Submit the form yourself, note the time, and check your inbox, spam folder and any filters or forwarding rules
  • Note which form plugin or form tool the site uses and anything that changed recently, such as a new host, plugin update or email provider
  • Find out where your domain's DNS is managed and which service sends your business email
  • Check whether your form plugin stores entries, so you know if any messages were lost

Access to give

  • An administrator user account on your WordPress site created just for this job, or a collaborator invite on your site builder
  • A user invite or delegated access on your DNS provider, if records need to change
  • A team member invite to your email sending service, if one is already in use

Done when

  • Three test submissions arrive in the notification inbox within a few minutes and not in spam
  • A test message's headers show SPF or DKIM passing for the sending domain
  • The form sends from an address on your own domain, with the visitor's email set as Reply-To
  • A short note explains what was wrong and lists every setting, plugin or DNS record that changed

When you need this job

You need this job when your contact form still shows a success message but the notification emails no longer reach you, or they've started landing in spam. On WordPress, that success message only means the site handed the email off for sending. The WordPress developer docs say a successful return from wp_mail() "does not automatically mean that the user received the email", and WordPress doesn't include mail-sending software of its own, so it depends on whatever your server or host provides. Forms on other platforms fail in much the same way after a change to the domain, the email provider or the DNS records.

What the pro will do

The pro starts by finding where the message stops: whether the form submits at all, whether the site tries to send, and whether the receiving inbox rejects the message or files it as spam. The usual fix routes form email through an SMTP service or your email provider instead of the web server, sets the From address to one on your own domain, and puts the visitor's address in Reply-To so you can still answer them directly. If your domain's SPF or DKIM records don't cover the sending service, they'll add or correct them, since Gmail requires SPF or DKIM from every sender.

How to review the work

Submit the form yourself from a personal address two or three times, and check that each message arrives in your inbox within a few minutes rather than in spam. In Gmail, you can open a message's menu, choose Show original, and look for SPF and DKIM marked as PASS. Ask for the short note on what changed, including any new plugin, service or DNS record, so whoever touches the site next knows where form email is configured.

Common gotchas

  • WordPress sends from wordpress@ plus your domain by default, and that address often has no mailbox and no authentication behind it, so receiving servers filter it.
  • Using the visitor's own email as the From address looks like spoofing to Gmail and other providers, and those messages are often rejected outright.
  • A domain can only have one SPF record, so adding a second one for the new sending service breaks SPF for everything. If your domain needs a full pass, the SPF, DKIM and DMARC job template covers it.
  • A move to a new host or email provider is the most common trigger, so mention any recent change when you post the job.
  • Many form plugins keep a copy of each entry on the site, so check there before assuming the messages you missed are gone.

The next level up

Send every form lead to your CRM so none of them depend on one inbox

Once form email arrives reliably, the next step is making sure a single missed message can never cost you a customer. Sending each submission into your CRM or a shared sheet, with an automatic reply to the person who wrote in, gives you a record of every lead and tells them right away that you got their message.

Post the form-to-CRM job

Questions people ask

Why does my contact form say it was sent when I get no email?

The form's success message usually means the website handed the email to its sending method, not that it was delivered. The message can still fail at the server or be rejected or filtered by the receiving inbox.

Do I need an SMTP plugin for my WordPress contact form?

Often, yes. WordPress relies on the server to send mail, and its own docs recommend relaying through a third-party sending service on self-managed sites, with an SMTP plugin as a common option for low volumes. On managed hosting, ask your host whether it offers an SMTP relay first.

Will fixing the form recover the messages I already missed?

Only if they were stored somewhere. Many form plugins save each entry on the site, so check the plugin's entries list before you assume those leads are lost.

Sources

Checked against these pages on .