# WordPress SMTP setup: configure and test your email

> To set up WordPress SMTP, connect one mail plugin to your sending provider, authorize the From address and verify the domain. Use the provider's hostname and credentials with its supported encryption, commonly port 587 with STARTTLS or 465 with implicit TLS, then test a real form submission through to the inbox.

Canonical: https://fer.marketing/wordpress-smtp
Author: Fernando Marcano, Fer Marketing
Updated: 2026-10-20

- **Plugin:** One active mail-routing plugin
- **Connection:** SMTP, OAuth or provider API
- **Domain:** SPF, DKIM and DMARC
- **Acceptance test:** Form, provider log and inbox

## Hire Fer to fix your WordPress SMTP and form delivery

We configure the sending plugin, check SPF, DKIM and DMARC, and test the affected form or notification through to your inbox. Send your site URL, the failing form or email, your hosting and mail providers, and the exact error if available. Fernando Marcano confirms scope and price in writing before work starts.

Fer LLC, Wyoming, US business · +1 310 734 8943

[Fix my WordPress SMTP](https://fer.marketing/contact#form)

## Why default WordPress mail can fail

Unless a host or plugin changes the transport, WordPress uses wp_mail() and PHPMailer to hand messages to PHP mail. That handoff depends on the web server's mail configuration. A host restriction or a sender the receiving system cannot authenticate can leave contact notifications, password resets and order emails undelivered.

The [WordPress wp_mail reference](https://developer.wordpress.org/reference/functions/wp_mail/) warns that a successful return means the sending method processed the request, not that the recipient received it. An SMTP mailer gives WordPress an authenticated sending route; it does not control the destination's spam decisions.

*Diagram: Follow the same message from the form through the sending provider to the receiving inbox. Each handoff needs its own evidence.*

If you do not yet know whether the form creates an email, start with [WordPress not sending email](https://fer.marketing/wordpress-not-sending-email). This guide covers configuring and validating the sending connection once you have identified the affected notification.

## Choose an SMTP plugin that supports your provider

The plugin connects WordPress to the sender. The provider supplies the account, permitted senders, quotas and delivery events. Choose both together: some mailer integrations use an HTTPS API instead of SMTP.

| Plugin | Official reference | Check before choosing |
| --- | --- | --- |
| WP Mail SMTP | [Other SMTP setup](https://wpmailsmtp.com/docs/how-to-set-up-the-other-smtp-mailer-in-wp-mail-smtp/) | Required mailer, authentication method and logging in the edition you plan to use. |
| Post SMTP | [Publisher's WordPress.org listing](https://wordpress.org/plugins/post-smtp/) | Supported provider connection, diagnostic logs and which alerts require an upgrade. |
| FluentSMTP | [Connection documentation](https://fluentsmtp.com/docs/) | Provider integration, connection routing and how your team will review failures. |

Keep one active mail-routing plugin for this setup. Save the previous configuration before deactivating an overlapping plugin, and check for host or custom-code mail overrides. Multiple plugins trying to replace the same sending route make diagnosis harder.

### Business mailbox or transactional email service?

A business mailbox may suit occasional notifications if its account rules and quotas fit your traffic. For order confirmations, password resets or a site with recurring automated mail, evaluate a transactional service such as Postmark, Brevo, Mailgun, SendGrid or Amazon SES. Compare sender verification, bounce visibility, access ownership and the plugin's supported integration. Check current plan limits directly before committing.

For example, [Amazon SES sandbox restrictions](https://docs.aws.amazon.com/ses/latest/dg/request-production-access.html) limit who can receive test mail until production access is approved. SES also uses [regional SMTP credentials](https://docs.aws.amazon.com/ses/latest/dg/smtp-credentials.html); its SMTP password is different from an AWS secret access key. A valid plugin setup cannot bypass those account requirements.

## How to configure SMTP in WordPress

Have WordPress administrator access, the provider account and access to the authoritative DNS zone ready. Save the current mail settings and take a recoverable [WordPress backup](https://fer.marketing/wordpress-backups). Use a business-owned provider account so a staff or agency change does not break the connection.

1. **Record the current failure.** Submit a labeled test and note its time, recipient and affected form. Save any error. Check the form's notification recipient before changing the transport.
2. **Activate one sending plugin.** Install your chosen plugin from its official source. In WP Mail SMTP, open WP Mail SMTP > Settings > General. Choose your provider's mailer, or Other SMTP for a manual SMTP connection.
3. **Set the sender identity.** Use a From address authorized by the provider and a recognizable business name. If all notifications should use that identity, enable Force From Email where available. Review multi-sender or multilingual sites before applying a site-wide override.
4. **Connect the provider.** For manual SMTP, enter the exact SMTP hostname, port, encryption, username and provider-issued credential, with authentication enabled. For OAuth or an API mailer, follow that integration's authorization flow instead; SMTP port fields may not apply.
5. **Authenticate the domain.** Copy the provider's required DNS names, types and values into the authoritative zone. Preserve existing senders, complete provider verification and confirm the intended From domain aligns for DMARC.
6. **Test the connection and the real notification.** Send a plugin test, then submit the public form. Confirm receipt, inspect authentication results and correlate the message with provider logs. Also test the password reset or order notification that prompted the repair.
7. **Document ownership and monitoring.** Record the provider, sender, connection method and person responsible for renewals or revoked access. Keep credentials out of handoff documents. Set log access and retention, and enable form-entry storage separately if needed.

Menu labels can change. Use the [WP Mail SMTP manual SMTP instructions](https://wpmailsmtp.com/docs/how-to-set-up-the-other-smtp-mailer-in-wp-mail-smtp/) alongside your provider's settings. Do not paste a normal mailbox password where the provider requires OAuth, an App Password or a dedicated SMTP credential.

## SMTP ports: match the encryption to the endpoint

| Port | Encryption | What to select |
| --- | --- | --- |
| 587 | STARTTLS | Often labeled TLS in a WordPress plugin. The connection upgrades to TLS before authentication. |
| 465 | Implicit TLS | Often labeled SSL. TLS starts as soon as the connection opens; this does not mean you should enable obsolete SSL protocols. |
| 25 | Provider-dependent | Do not assume it is available or appropriate for website submission. Hosts may block it; follow the provider's documented route. |

[Amazon SES documents both STARTTLS and TLS wrapper connections](https://docs.aws.amazon.com/ses/latest/dg/smtp-connect.html), including these common port pairings. Your chosen endpoint must support the pairing you enter. Do not select implicit TLS on a STARTTLS-only port, turn off encryption to hide a failure or disable certificate verification.

> **Hire Fer to resolve your SMTP connection error** We trace the failed connection, correct authentication or sender settings, and test the notification that is missing. Send your site URL, exact error, plugin name, and hosting and mail providers. We confirm the repair scope and price in writing. Fer LLC, Wyoming, US business · +1 310 734 8943. [Fix my WordPress SMTP](https://fer.marketing/contact#form)

## Gmail SMTP for WordPress: OAuth first, App Password if eligible

For a supported Google connection, prefer the plugin's Google authorization flow. For example, the [WP Mail SMTP Gmail mailer](https://wpmailsmtp.com/docs/how-to-set-up-the-gmail-mailer-in-wp-mail-smtp/) uses Google's API. Follow its current app, consent and redirect-URI instructions exactly, then authorize the business-owned account. That route does not need manual SMTP port settings.

**Manual Gmail SMTP settings for an eligible account**

```
SMTP host: smtp.gmail.com
Port: 587
Encryption: STARTTLS (often labeled TLS)
Authentication: enabled
Username: full Google email address
Password: dedicated Google App Password
Alternative: port 465 with implicit TLS (often labeled SSL)
```

Use an address the connected account is authorized to send as. These are settings, not working credentials.

These settings follow [Google's app sending documentation](https://knowledge.workspace.google.com/admin/gmail/send-email-from-a-printer-scanner-or-app). Google Workspace SMTP relay at smtp-relay.gmail.com is a separate administrator-configured option; switching the hostname alone does not authorize your web server.

[Google App Passwords](https://support.google.com/accounts/answer/185833) require 2-Step Verification and can be unavailable because of account restrictions. Google recommends Sign in with Google where supported. If App Passwords are missing, use an approved OAuth integration or ask the Workspace administrator. Google also revokes App Passwords when the account password changes.

> **Gmail login is not business-domain verification:** Connecting a personal Gmail account does not authorize arbitrary From addresses on your business domain. Use an authorized Google sender or authenticate the business domain with a suitable provider. Check the account's current sending limits and administrator policies.

## Authenticate the domain without breaking existing email

The SMTP login authorizes WordPress to use the provider. DNS authentication lets receiving systems evaluate the sending domain. Configure it for the actual provider and sender; copying a generic record from another site's tutorial can authorize the wrong service.

| Method | Purpose | What to configure |
| --- | --- | --- |
| SPF | Authorizes servers for the envelope sender domain, which may differ from the visible From. | Use the provider's specified domain or return-path subdomain. Merge authorized senders into one SPF record at that name. |
| DKIM | Signs mail so the receiver can verify the signing domain and signed content. | Publish the exact selector and TXT key or CNAME targets supplied by the provider. Enable signing there too. |
| DMARC | Checks the visible From domain against a passing, aligned SPF or DKIM identity. | Review the policy at _dmarc.your-domain. Preserve an existing policy; use reports to plan changes. |

[Google's SPF setup guide](https://knowledge.workspace.google.com/admin/security/set-up-spf) explains including all senders in a single record. Get DKIM records from the sending service; for Workspace, follow [Google's DKIM setup](https://knowledge.workspace.google.com/admin/security/set-up-dkim). [Google's DMARC instructions](https://support.google.com/a/answer/2466580) explain alignment and policy: p=none requests monitoring without asking for quarantine or rejection. Do not weaken an existing enforcement policy just to make a broken sender appear to work.

For personal Gmail recipients, [Google's sender guidelines](https://support.google.com/a/answer/81126) require SPF or DKIM for all senders, and SPF, DKIM and DMARC for bulk senders. Authentication is part of delivery, not a guarantee of inbox placement. Verify the records in DNS and the results on a newly delivered message.

> **SMTP setup does not normally require an MX change:** MX records route incoming mail. Preserve staff mail routing when adding the provider's outbound authentication records. Review the exact DNS change with whoever manages business email, especially if the provider asks for a custom return-path subdomain.

[Google's MX documentation](https://knowledge.workspace.google.com/admin/domains/set-up-mx-records-for-google-workspace) describes incoming delivery. Treat a mailbox migration as a separate change from connecting WordPress to an outbound sender.

## Test more than the plugin's green success message

- [ ] Send a labeled plugin test: Use inboxes you control, including Gmail and your team's actual mail system. Record the recipient, time and subject.
- [ ] Check inbox, spam and quarantine: Correlate the message with the provider's message ID, rejection or bounce. Provider acceptance and inbox placement are separate events.
- [ ] Inspect the received headers: In Gmail, open More > Show original. Check Authentication-Results for SPF, DKIM and DMARC, including which domains were evaluated.
- [ ] Submit each public form: Test both languages, conditional recipients, visitor confirmations and Reply-To. The plugin's test bypasses the form's notification settings.
- [ ] Test the affected system email: Use a controlled account for password resets or a safe test order for shop notifications. Confirm that each expected message arrives.
- [ ] Verify storage and failure visibility: Confirm whether the form stores entries. Limit log access and retention because logs can contain customer messages or reset links.

Google documents [how to view full message headers](https://support.google.com/mail/answer/29436). Document the tested form or notification, sender, provider event and received authentication results. Keep passwords, API keys and live reset links out of that record.

## WordPress SMTP troubleshooting by symptom

| Symptom | Check next | Useful action |
| --- | --- | --- |
| Timeout or cannot connect | SMTP hostname, port, encryption and host outbound restrictions. | Ask the host to check the exact destination and port. A supported provider API can be an alternative if SMTP egress is blocked. |
| Authentication failed | Username, credential type, account approval or revoked authorization. | Use the provider's SMTP credential or reconnect OAuth. For Gmail, check App Password eligibility rather than retrying the account password. |
| Sender rejected or not verified | Authorized From identity, provider domain verification and account restrictions. | Verify the intended sender and inspect the provider's exact rejection before changing the form. |
| Plugin test arrives, form email does not | Form recipient, notification rules, sender fields and whether a sending event exists. | Test the real form and correlate its timestamp with logs. Transport settings cannot repair a disabled notification. |
| Accepted but missing from the inbox | Spam, quarantine, bounces, suppression and authentication headers where available. | Inspect provider events and the recipient system. Avoid repeatedly resending a message to a suppressed address. |
| Worked before, stopped later | Revoked credentials, provider limits, plugin changes or DNS changes. | Compare the failure time with changes and re-test the affected route after correcting the cause. |

### Use the visitor's email in Reply-To, not From

Send notifications from an authorized site address. Put the visitor's validated address in Reply-To so staff can answer without sending as the visitor's domain. In Contact Form 7, review the [Mail tab and additional headers](https://contactform7.com/setting-up-mail/) and ensure each mail-tag matches a field in that form.

**Illustrative Contact Form 7 notification**

```
To: team@example.com
From: Website <website@example.com>
Additional headers:
Reply-To: [your-email]
```

Replace example.com with your authenticated domain and authorized addresses. [your-email] must be a valid email field in your form.

After the repair, include mail access and plugin updates in your [WordPress security checks](https://fer.marketing/wordpress-security-checklist). For ongoing checks, see [WordPress management](https://fer.marketing/services/wordpress-management).

## Get your SMTP connection and form delivery fixed

Fer Marketing is operated by Fer LLC, founded by Fernando Marcano. Send your site URL, affected form or notification, hosting and mail providers, and any error. We confirm scope and price in writing, then configure the sender, check domain authentication and test delivery.

- One supported sending connection and authorized sender identity.
- Provider-specific DNS checks that preserve existing business email.
- Plugin and real-form tests with received-message verification.
- A handoff covering settings, account ownership and follow-up checks.

https://fer.marketing/contact#form

## FAQ

### Do I need an SMTP plugin if my hosting already sends email?

Check the existing route first. If the host already provides authenticated sending and usable delivery records, another routing plugin may add a conflict. If WordPress relies on an unconfigured PHP mail route, configure one supported SMTP or API connection and test it.

### Which is better: WP Mail SMTP, Post SMTP or FluentSMTP?

Choose the plugin that supports your provider's authentication method and the logs your team needs. Verify those features in the edition you will use. Keep one active mail-routing plugin and compare the whole setup, including provider access and failure monitoring.

### Can I use Gmail SMTP with WordPress?

Yes, with a supported Google authorization connection or, for an eligible account, smtp.gmail.com and a dedicated App Password. Manual settings commonly use port 587 with STARTTLS or 465 with implicit TLS. Account policies and sending limits still apply.

### Should WordPress SMTP use port 465 or 587?

Use the combination documented by your provider: 587 with STARTTLS or 465 with implicit TLS when supported. Plugin labels may say TLS and SSL respectively. A mismatched port and encryption mode can prevent the connection.

### Will SMTP guarantee delivery to Gmail or Outlook?

No. A provider can accept mail that is later rejected, quarantined or filtered into spam. Verify the sender, authentication, provider events and actual recipient inbox. Finish by testing the public form rather than relying only on the plugin test.

### Will installing SMTP recover old missing form submissions?

No. SMTP changes future sending. Older inquiries can be recovered only if another system retained them, such as form-entry storage, a CRM, mail logs or a recipient mailbox. Check those records separately.

### Can Fer configure SMTP and fix the form too?

Yes. Send the site URL, affected form, provider and any error. Fer LLC, a Wyoming, US business founded by Fernando Marcano, can scope the connection, sender authentication and real-form testing. Scope and price are confirmed in writing before work begins; provider charges are separate.

A finished SMTP setup has evidence: an authorized sender, verified authentication and a real notification received by the intended team. Keep those checks with the site's maintenance notes.

## Hire Fer to fix your WordPress SMTP and form delivery

We configure the sending plugin, check SPF, DKIM and DMARC, and test the affected form or notification through to your inbox. Send your site URL, the failing form or email, your hosting and mail providers, and the exact error if available. Fernando Marcano confirms scope and price in writing before work starts.

Fer LLC, Wyoming, US business · +1 310 734 8943

[Fix my WordPress SMTP](https://fer.marketing/contact#form)