Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
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
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Hosting · Info

WP Engine SMTP Settings Explained: What Each Option Does

WP Engine SMTP Settings Explained: What Each Option Does

Short answer

WP Engine does not provide its own SMTP server or email inboxes, so SMTP settings come from a third-party provider such as SendGrid, Mailgun or Google Workspace. Enter that provider's host, port, encryption and login in an SMTP plugin, add its DNS records, and send a test email.

Key takeaways

  • WP Engine recommends a third-party email service for site mail.
  • SMTP settings come from your provider, not from WP Engine.
  • Use port 587 with TLS or port 465 with SSL, matched correctly.
  • API mailers can be more reliable than plain SMTP.
  • Add SPF, DKIM and DMARC where your DNS is hosted.
  • Test password resets, forms and order emails after setup.

What are WP Engine SMTP settings?

WP Engine SMTP settings are the mail server details you enter in an SMTP plugin, such as host, port, encryption and login, so WordPress sends email through a third-party provider instead of the server.

WP Engine is a managed WordPress host. It does not host email inboxes, and it does not give you its own SMTP server to send from. WordPress on WP Engine can send basic mail, but WP Engine recommends a dedicated email service for reliable delivery.

WP Engine explains this in its support article on sending email on WP Engine. Check that page for its current limits and recommendations.

So when people talk about WP Engine SMTP settings, they mean the settings for a provider such as SendGrid, Mailgun, Postmark, Amazon SES, Google Workspace or Microsoft 365, entered in a plugin on a WP Engine site.

Why use SMTP on a WP Engine site?

SMTP sends mail through an authenticated email service, which improves delivery and gives you logs, while default server mail often lands in spam or goes missing.

WordPress sends mail with the wp_mail() function. By default, that hands mail to the server. Mail from a shared web server usually lacks proper authentication for your domain.

Receiving servers such as Gmail and Outlook check whether a message really comes from your domain. Without SPF, DKIM and DMARC alignment, they may reject it or mark it as spam.

An SMTP provider solves this. It signs mail for your domain, keeps a good sending reputation, and shows you whether each message was delivered.

If you are new to the idea, our guide on how to set up SMTP in WordPress covers the full setup on any host.

What does each SMTP setting do?

Each SMTP field tells WordPress where to send mail, how to secure the connection, and how to prove it may send for your domain.

SettingWhat it doesTypical value
SMTP hostThe provider's mail server addressGiven by your provider
PortThe network port for the connection587 for STARTTLS or 465 for SSL/TLS
EncryptionHow the connection is securedTLS (STARTTLS) or SSL
AuthenticationWhether a login is requiredOn
UsernameYour SMTP login or API userProvider account or API username
PasswordYour SMTP password or API keyStore securely, not in plain text if possible
From emailThe address mail is sent fromAn address on your own domain
From nameThe sender name people seeYour site or business name

Use the exact host, port and encryption pair your provider documents. A mismatch, such as port 465 with TLS selected, is one of the most common reasons SMTP fails.

Which port and encryption should you choose?

Use port 587 with TLS (STARTTLS) or port 465 with SSL, matching your provider's instructions; avoid port 25, which is often blocked for outgoing web server mail.

Port 587 starts as a plain connection and upgrades to encryption with STARTTLS. Port 465 uses encryption from the first byte, which plugins usually label SSL. RFC 8314 describes the modern standard for these submission ports.

Both are secure when set correctly. The key is that port and encryption must match.

If neither works, the problem is rarely WP Engine blocking you. Check the host name, credentials and any IP restrictions on the provider side first.

Should you use an API mailer instead of SMTP?

If your provider offers an API connection in your mail plugin, it is often more reliable than SMTP, because it uses HTTPS and avoids port and encryption problems.

Plugins such as WP Mail SMTP support API mailers for several providers. Instead of host and port, you paste an API key and choose a sending domain.

API connections are less affected by firewall rules and connection timeouts. They also tend to give clearer error messages.

Whichever method you choose, the provider still needs to verify your domain with DNS records. Our explainer on what WP Mail SMTP is covers the mailer options in more detail.

Which plugin should you use for SMTP on WP Engine?

Use a well-maintained SMTP plugin such as WP Mail SMTP, FluentSMTP or Post SMTP; WP Engine does not require a specific one.

WP Mail SMTP on WordPress.org is one of the most widely used. It supports generic SMTP and many API mailers, and includes a test email tool.

Install one SMTP plugin only. Two plugins trying to take over wp_mail() can conflict and cause messages to fail without an obvious error.

Some form and newsletter plugins also have their own sending settings. Make sure they either use WordPress mail or have their own provider set up, not both.

What DNS records do you need for SMTP on WP Engine?

Add the SPF, DKIM and sometimes DMARC records your email provider gives you, at wherever your domain's DNS is hosted.

Your DNS might be at WP Engine, at your registrar, or at Cloudflare. Records go wherever the nameservers point, not necessarily at WP Engine. Our guide to WP Engine DNS settings explains how to check.

SPF lists which services may send for your domain. Keep a single SPF record and include every sender in it, such as your email inbox provider and your SMTP service.

DKIM adds a signature that proves a message is genuine. DMARC tells receivers what to do when checks fail. For step-by-step details, see how to set up SPF, DKIM and DMARC.

How do you test SMTP settings on WP Engine?

Send a test email from your SMTP plugin, check that it arrives in the inbox, and look at the message headers for passing SPF, DKIM and DMARC.

Most SMTP plugins include a test email screen. Send a test to a Gmail or Outlook address, since they show authentication results clearly.

Then test the real flows: a password reset, a contact form message and, if you run a shop, an order email. Each plugin may send mail slightly differently.

Our guide on how to test WP Mail SMTP walks through reading the results.

What if SMTP still does not work on WP Engine?

Check the plugin's error log first, then confirm credentials, port and encryption, and look at your provider's activity log for rejected messages.

Authentication errors usually mean a wrong username, password or API key. Our guide to the SMTP could not authenticate error covers that message in detail.

If the test passes but real mail is missing, a form or shop plugin may override the sender address. Set the Force From Email option in your SMTP plugin if it has one.

If you suspect a platform limit, contact WP Engine support. They can confirm whether outgoing connections from your environment are restricted.

No; this is general technical information about sending email, not legal advice about consent, marketing rules or data protection.

If you send marketing email, laws in your region may require consent and an unsubscribe link. Ask a qualified adviser about your obligations.

For transactional mail such as password resets and receipts, the main concern is delivery, which the settings above address.

Frequently asked questions

Does WP Engine have an SMTP server?

No. WP Engine does not offer its own SMTP server or email hosting. It recommends sending site email through a third-party provider, configured in WordPress with an SMTP or mailer plugin. Check WP Engine's support docs for current details.

What SMTP port should I use on WP Engine?

Use the port your email provider documents, usually 587 with TLS or 465 with SSL. Make sure the encryption setting matches the port, since a mismatch is a frequent cause of connection errors.

Can I use Gmail SMTP on a WP Engine site?

Yes. Google Workspace and personal Gmail can send through an SMTP plugin, often using the Google API connection rather than a password. Sending limits apply, so busy sites usually choose a dedicated transactional email service instead.

Why are emails from my WP Engine site going to spam?

Usually because mail is not authenticated for your domain. Send through an SMTP provider, then add the SPF, DKIM and DMARC records it gives you. Use a from address on your own domain rather than a free mailbox.

Where do I add SPF and DKIM records for a WP Engine site?

Add them wherever your domain's DNS is hosted. That might be WP Engine, your registrar or Cloudflare. Check which nameservers your domain uses, then add the records your email provider supplies in that DNS panel.

Sources

  1. Sending Email on WP Engine WP Engine
  2. wp_mail() WordPress Developer Resources
  3. WP Mail SMTP WordPress.org Plugin Directory
  4. RFC 8314: Cleartext Considered Obsolete RFC Editor

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

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.