Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Troubleshooting · Troubleshooting

How to Fix a Contact Form That Doesn't Send Email in WordPress

Short answer

A contact form that shows a success message can still lose emails, because WordPress only hands each message to the server's mail system. The usual causes are an unauthenticated From address, PHP mail blocked by the host, or missing SPF, DKIM and DMARC records. Fix the From address, send mail through authenticated SMTP, add the three DNS records, then submit a real form entry to confirm delivery.

Key takeaways

  • A form's success message only means WordPress handed the email to the server, not that it reached an inbox.
  • WordPress sends mail through wp_mail(), which by default uses the server's PHP mail function with no login.
  • The From address must be a real address on your own domain, with the visitor's address in Reply-To.
  • Authenticated SMTP on port 587 with TLS replaces PHP mail and is the fix that lasts for most sites.
  • Google has required SPF or DKIM from every sender to personal Gmail accounts since February 1, 2024.
  • Always confirm a fix with a real form submission, not only with a plugin test email.

Why does my contact form say “sent” but no email arrives?

A form that says sent only means WordPress handed the message to the server, not that the message reached an inbox.

WordPress documents this clearly: a true return from wp_mail() only means the method processed the request without errors, not that the user received the email (wp_mail() reference). After that point, the server, the receiving provider, or a spam filter can still drop the message.

That gap is why this problem is so hard to spot. The visitor sees a thank-you message, you see nothing, and no error appears anywhere on the site.

What you seeLikely causeFirst check
Form says sent, nothing arrives anywhereUnauthenticated mail rejected by the receiving providerFrom address and SPF, DKIM, DMARC records
Mail arrives, but in spam or junkMissing or failing SPF, DKIM or DMARCDNS records and the From address
Form shows an error instead of sentWordPress could not hand the mail to the serverTest email tool and the error message
Mail stopped after moving hostsNew host blocks PHP mail or SMTP portsSMTP settings and host mail limits

How does WordPress send contact form emails?

WordPress sends form emails through its wp_mail() function, which passes each message to the server's mail system.

WordPress itself has no mail server. The Advanced Administration Handbook states that WordPress has never provided a mail user agent or a mail transfer agent by default, and only wraps a library that submits messages to one (Mail handbook). By default that library is PHPMailer, and it uses the server's PHP mail() function.

That default route has no login. PHP mail() sends the message from the web server with no username, no password, and no signature that proves your domain approved it.

The default From address is also a weak point. WordPress fills in [email protected] for your domain, and the handbook warns that some mail systems check whether that mailbox exists (Mail handbook).

WordPress 6.9 improved this by setting the sender address by default to wordpress@ plus your site address, and letting plugins change it with the wp_mail_from filter (More-reliable email in WordPress 6.9).

What should I check first when a form stops sending email?

Check the cheapest causes first, in this order, before you change any settings.

  1. Open the spam and junk folders of the address that should receive the mail, and search for the sender name.
  2. Check that the notification address in the form settings is spelled right, with no extra spaces.
  3. Submit the form yourself with a different email address and watch what happens.
  4. Send a test email from your SMTP plugin or from the Check Email plugin under Tools.
  5. Ask a second person on a different mail provider, such as Outlook, whether they got the message.

If the test email arrives but form mail does not, the form itself is the problem, not the mail route. If the test email also fails, the mail route is the problem.

How do I check the From and notification addresses?

Set the From address to a real address on your own domain, and put the visitor's address in Reply-To instead.

Many form plugins let you set the notification From address to the visitor's address so that Reply goes to them. That breaks authentication, because your server cannot send mail as someone else's Gmail or Yahoo address.

Open the form, then open its notification or email settings. Set From to an address you control on your own domain, such as [email protected], and set Reply-To to the visitor's email field.

If your plugin is WPForms, its notification settings follow the same pattern, and the plugin-specific checks are in our guide to fixing WPForms email.

Also check the site admin address under Settings, then General. That address receives WordPress notices, and a wrong one there hides password resets and update alerts too.

How do I test whether WordPress can send email at all?

Send a test email from an SMTP plugin's test tool, then check the inbox, the spam folder, and the plugin's error log.

WP Mail SMTP adds a test tool under WP Mail SMTP, then Tools, then Email Test. Enter an address you can check right now and click Send Email.

A working setup shows the message "Test HTML email was sent successfully! Please check your inbox to make sure it was delivered" (How to test your SMTP connection).

If the test fails, the error message names the problem. An authentication error, code 535, means the username or password is wrong, and Gmail and Yahoo accounts need an app-specific password rather than the normal account password (How to test your SMTP connection).

To test the default route instead, install the free Check Email plugin from WordPress.org. It adds a tool under Tools, then Check Email, that sends one message through the default wp_mail() path.

How do I set up SMTP to fix WordPress email?

SMTP makes WordPress log in to a real mail server, which replaces the unauthenticated PHP mail route.

SiteGround's knowledge base puts it plainly: WordPress uses the PHP mail() function by default, and SMTP uses proper authentication that leads to higher deliverability (How to fix WordPress not sending emails). Follow these steps with WP Mail SMTP, the most widely used SMTP plugin for WordPress.

  1. Go to Plugins, then Add New, search for “WP Mail SMTP”, then click Install Now and Activate.
  2. Open the setup wizard and pick a mailer, such as Other SMTP, Gmail, or a transactional mail service.
  3. Enter the SMTP host, encryption, port, username, and password from your mail provider.
  4. Turn on Force From Email so every message leaves from your verified domain address.
  5. Save the settings, then send a test email from WP Mail SMTP, then Tools, then Email Test.
SettingWhat to enter
SMTP hostYour provider's server address, for example your mailbox host
EncryptionTLS
SMTP port587
AuthenticationOn, with your mailbox username and password
From emailA verified address on your own domain

For most providers, port 587 with TLS is the right combination, according to WP Mail SMTP's own setup documentation (WordPress SMTP settings). If the connection fails, your host may block SMTP ports, and you should ask them to open port 587 or switch to an API mailer.

What are SPF, DKIM and DMARC, and why do they matter?

SPF, DKIM and DMARC are three DNS records that prove your domain approved the mail, and receiving servers check them before delivering.

SPF is a TXT record that lists the servers allowed to send mail for your domain. DKIM adds a digital signature to each message so the receiver can check it came from your domain and was not changed.

DMARC is a TXT record that tells receivers what to do with mail that fails SPF or DKIM.

Google's sender guidelines require SPF or DKIM from every sender to personal Gmail accounts, a rule in force since February 1, 2024 (Email sender guidelines).

Senders who send around 5,000 or more messages a day to personal Gmail accounts must use SPF and DKIM together, plus DMARC, and keep the spam rate reported in Postmaster Tools below 0.3%.

Google also sets a minimum DKIM key length of 1024 bits and recommends 2048 bits. Our step-by-step guide to setting up SPF, DKIM and DMARC for WordPress email walks through each record.

DNS changes can take hours to spread, so wait before you retest after adding a record, as explained in our guide on how long DNS propagation takes.

Why do form emails land in spam?

Form emails land in spam when they arrive without authentication, from a shared server IP, or with a From address that fails checks.

The WordPress handbook warns that a message may be routed to a spam folder or discarded as malicious, and that SPF, DKIM and DMARC are the measures that convince recipient servers the message is legitimate (Mail handbook).

Shared hosting adds a second risk. Your mail leaves from the same IP address as many other sites, so another site's bad behaviour can hurt your delivery even when your own settings are right.

A third cause is content and volume. Short, link-heavy form notifications sent in bursts look like bulk mail, so keep notification text plain and send each form entry as its own message.

How do I confirm the fix worked?

Submit a real form entry to an address you control, then check the inbox, the spam folder, and the mail log.

A passing test email is not enough on its own. It proves the mailer works, but it does not prove the form uses the same recipient, sender, and settings. Fill in the live form exactly as a visitor would, then check whether the notification arrives within a few minutes.

Check the mail log too, if your SMTP plugin keeps one. Look for the form entry by time and recipient, and confirm the log shows it as sent rather than failed or blocked.

Repeat the check with a second provider. A message that reaches Gmail but not Outlook points to a provider-specific filter, not a broken form.

When should I contact my host?

Contact your host when test emails fail with a connection error, when SMTP ports seem blocked, or when PHP mail is disabled on the server.

The WordPress handbook says that on managed hosting, mail questions should go to the host, and the host may offer an SMTP relay through its admin panel (Mail handbook).

Ask them three things: whether PHP mail() is enabled on your plan, whether outbound port 587 is open, and whether they offer a relay or mailbox you can use for WordPress mail.

If the host confirms PHP mail is disabled, no plugin setting can bring it back, and SMTP is the only route. If the host confirms the ports are open and the test still fails, the error message from the test tool is the detail their support team needs.

Before you open the ticket, note your hosting plan and whether the problem started after a move or an update. Our guide to WordPress hosting requirements explains what a host should provide for mail and other core features.

What mistakes should you avoid?

The most common mistakes all come down to one habit: changing the From address, the mail route, or the DNS records without testing each change.

  • Using the visitor's email address as the From address, which makes the message look spoofed.
  • Using a free Gmail or Yahoo address as the From address for mail sent from your domain.
  • Publishing two SPF records for one domain instead of merging them into a single record.
  • Changing the SMTP settings and the DNS records at the same time, so you cannot tell which change helped.
  • Treating a form's success message as proof of delivery without ever checking the inbox.
  • Skipping the test email after every change, so a new mistake goes unnoticed for weeks.

Frequently asked questions

Can I use my Gmail address as the From address on a WordPress form?

No. The From address should be a real address on your own domain, such as [email protected]. A Gmail address in From claims the mail comes from Google's domain, which your server is not allowed to send for, so receiving servers often reject it or mark it as spam. Put the visitor's address in Reply-To instead, so you can still answer them with one click.

Do I need SPF, DKIM and DMARC for a small site with few form entries?

Yes, at least SPF or DKIM. Google has required SPF or DKIM from every sender to personal Gmail accounts since February 1, 2024, with no exception for small sites. DMARC becomes required only for bulk senders, but adding a DMARC record with a policy of none still helps receiving servers trust your mail and gives you reports about failures.

Why did my contact form stop sending email after I moved to a new host?

A move changes the mail route. The new host may block PHP mail, block outbound SMTP ports, or require different SMTP credentials than the old host. Re-enter the SMTP settings for the new host, check that port 587 is open, and send a test email. Also check the DNS records, because SPF and DKIM entries that named the old host may no longer cover the new one.

Will an SMTP plugin fix a form that never sends anything?

Only if the form actually generates the email. SMTP fixes the delivery route, not the form. If the form fails validation, blocks the entry as spam, or has a broken notification rule, no mail is created for SMTP to send. Check the form's entries or submissions list first. If entries are saved but no mail arrives, SMTP is the right fix.

How long should I wait after adding SPF, DKIM or DMARC records before retesting?

Wait at least a few hours, because DNS changes spread across the internet over time rather than instantly. If you retest too soon, the old records may still be in use and the result will mislead you. After waiting, send a fresh test email and submit a real form entry, then check the inbox and the spam folder before changing anything else.

Does WordPress 6.9 change how contact form email works?

WordPress 6.9 made email more reliable by setting the sender address by default, using wordpress@ plus your site address, and by protecting encoding headers between mail calls. It did not add a mail server or SMTP settings to WordPress. You still need a working mail route, a From address on your own domain, and SPF, DKIM and DMARC records for delivery.

Sources

  1. Mail - Advanced Administration Handbook WordPress Developer Resources
  2. wp_mail() - Function WordPress Developer Resources
  3. More-reliable email in WordPress 6.9 Make WordPress Core
  4. Email sender guidelines Google
  5. How To Test Your SMTP Connection WP Mail SMTP
  6. How to Fix WordPress Not Sending Emails Issue SiteGround

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test