WordPress not sending email: get form leads to your inbox

WordPress not sending email: where it fails

WordPress normally hands messages to the server through PHP mail unless a plugin or host changes that route. Hosts may restrict it, and an unauthenticated web server may struggle to deliver to Gmail or Outlook. Messages can be rejected or filtered into spam while the website appears to work.

• The form never submits

  A validation error, broken script or spam check can stop the message before email is involved. If the page keeps spinning or shows an error, investigate that first.

• The server cannot send

  A blocked connection, expired credential or rejected sender can stop the handoff. Match the sending log to the time of your test instead of repeatedly reinstalling the form.

• The inbox filters it

  The provider may accept a message that later lands in spam or quarantine. An accepted status is useful evidence, but someone still needs to check the destination.

The WordPress wp_mail reference explicitly distinguishes successful processing from successful receipt. Start with one labeled test, its time and its destination so you can follow the same message through each system.

A working form protects your Google leads

Someone can find you on Google, compare your services and write a detailed request that never reaches your team. The immediate problem is the lost conversation after the visit. Fixing SMTP protects that contact path; it does not promise better Google rankings.

These findings describe contact options visible in the audited HTML, not email delivery tests. They show why the contact route deserves attention before more traffic is sent to a site. A form that exists still needs its own delivery check.

Our WordPress web design hub connects these checks with the rest of the customer journey. The WordPress conversion guide covers what visitors need before they choose to contact you.

Choose an SMTP plugin and mail provider

An SMTP plugin connects WordPress to a sending service; it is not the mailbox or service itself. WP Mail SMTP, FluentSMTP and Post SMTP are options to evaluate neutrally. Choose around your provider, required authentication and available logs, then keep one active mail-routing plugin.

• A real business mailbox

  An existing mailbox can suit a modest flow of inquiries. Use a business-owned account and confirm its sending rules, limits and recovery access before relying on it for website notifications.

• A transactional service

  Brevo, SendGrid, Mailgun, Amazon SES and Postmark are services to compare for automated messages. Check domain verification, account approval, delivery records and plugin compatibility before choosing.

• SMTP or an API

  Some plugin connections use the provider's API instead of SMTP. Both can provide an authenticated route; the important questions are who sends the message and how you trace a failure.

Check the current plugin edition for the connection and logging you need. Provider fees and plugin licensing are separate decisions, and a paid plugin cannot repair an unverified domain by itself. Prefer a setup the business can access after a staff or agency change.

WordPress SMTP Gmail: use the right login

For an eligible Gmail or Google Workspace account, manual SMTP uses smtp.gmail.com, port 587 with STARTTLS, the full email address and an App Password. Google's app sending guidance explains the available routes. Your ordinary Gmail password is not the credential to paste into WordPress.

Server: smtp.gmail.com
Port: 587
Encryption: STARTTLS
Authentication: enabled
Username: your full Google email address
Password: a dedicated App Password

An App Password requires 2-Step Verification and may be unavailable under account restrictions. Google prefers Sign in with Google where supported; see its App Password guidance. If that option is missing, use a supported OAuth connection or ask your Workspace administrator instead of weakening account protection.

Workspace SMTP relay is a separate option

A Workspace administrator can configure the SMTP relay for approved senders and the server's authentication method. It is not enabled by changing the SMTP hostname alone. Google documents the administrator setup in Workspace SMTP relay.

Microsoft 365: prefer an OAuth connection

Microsoft 365 is more complicated than entering a username and password. SMTP AUTH is often disabled through organization or mailbox settings, and security defaults can disable it too. Your administrator should review Microsoft's SMTP AUTH guidance before changing the account.

Prefer your plugin's Microsoft OAuth integration, with the required administrator consent, or an authenticated transactional service. For example, WP Mail SMTP's Microsoft mailer uses Microsoft's API. Confirm the required plugin edition and permissions before buying or authorizing it.

SPF, DKIM and DMARC in plain words

SMTP authenticates your site's connection to the provider. Domain authentication helps the receiving inbox verify that the provider is allowed to represent your business. SPF lists senders, DKIM signs messages, and DMARC checks their relationship to the visible From domain.

Google's sender guidelines require SPF or DKIM for all senders to personal Gmail accounts, and SPF, DKIM and DMARC for bulk senders. Authentication helps smaller sites too, though it does not guarantee inbox placement.

Type: TXT
Name: example.com
Value: v=spf1 ip4:192.0.2.10 ~all

Type: TXT
Name: _dmarc.example.com
Value: v=DMARC1; p=none; rua=mailto:dmarc@example.com

Get DKIM records from the actual sending provider, including its selector and key or CNAME targets. Do not invent a key or replace unrelated DNS records. Have the person responsible for business email review changes so the website repair preserves existing staff mail.

WordPress not sending email: the 15-minute fix

Treat 15 minutes as a target for a straightforward setup with approved accounts, DNS access and credentials ready. Domain verification, provider approval or Microsoft consent can take longer. Before changing anything, save the current settings and take a recoverable backup.

1. Step 1

   Identify one missing message

   Submit a labeled test and record the page, time and destination. Check the form recipient, existing entries and spam folder so you know whether the failure starts before or after the sending attempt.

2. Step 2

   Connect one authenticated provider

   Configure one mail-routing plugin with your business mailbox or transactional account. Use the provider's supported SMTP, OAuth or API method, and deactivate overlapping routing plugins after saving their settings.

3. Step 3

   Verify the sender domain

   Publish the provider's required DNS records and wait for verification. Set an authorized From address, and put the visitor's validated email in Reply-To so staff can answer them without impersonating their domain.

4. Step 4

   Send a plugin test email

   Send a clearly labeled test to controlled Gmail and Outlook inboxes where possible. Check inbox, spam and quarantine; record any provider rejection rather than treating a green plugin status as delivery proof.

5. Step 5

   Inspect authentication headers

   Open the received message's original or headers and inspect Authentication-Results for SPF and DKIM pass. Check DMARC and alignment with your sender domain; investigate failures before calling the setup complete.

6. Step 6

   Enable useful logs and entry storage

   Record sending status and provider identifiers through the plugin, provider or suitable logging tool. Enable form-entry storage separately if needed, restrict who can read it and choose a retention period for messages and attachments.

7. Step 7

   Submit the real form again

   Test the public form on a phone, including each language and notification route. Confirm the staff inbox, stored entry and any visitor confirmation; test replying to the visitor, then record the working configuration and owner.

Contact Form 7 not sending email: check routing

If your WordPress contact form is not sending email but the plugin test arrives, inspect the form's notification settings. Check the To address, enabled notifications, field tags and conditional routing. Contact Form 7's mail setup documentation explains the sender and additional headers.

To: sales@example.com
From: Website <website@example.com>
Reply-To: [your-email]

Entry storage is a separate feature to confirm, not something SMTP adds automatically. Verify that a test submission is actually saved and readable by the right staff. If there is no stored copy, fixing delivery later cannot recreate inquiries that were never recorded.

Keep form delivery on your care checklist

Mail can stop after an account password change, a disconnected authorization, a hosting move or a DNS edit. Keep a short record of the provider, sender, form destinations and person responsible. Make that record accessible to the business without putting secrets in an ordinary document.

Use our guides to WordPress backups, safe WordPress updates and WordPress security to protect the rest of this workflow. If you want one team to own the repair and follow-up checks, see WordPress management.