To connect an email account to WordPress, configure WordPress to send its outgoing messages—such as password resets, form notifications, and store alerts—through an email provider using SMTP or a provider-specific API or OAuth connection. This does not create an inbox inside WordPress. You will need a compatible mail plugin and the current connection details and authentication method supported by your provider.
Choose how WordPress will send email
WordPress generates messages through its mail function, wp_mail(). An SMTP plugin can connect that function to a mail service so messages are sent through an account or provider you choose, rather than relying only on the site’s default mail setup. WordPress.org’s support guidance on external SMTP describes this general arrangement.
| Route | What you need | Consider it when |
|---|---|---|
| Provider SMTP | The provider’s current SMTP server, port, encryption method, username, and authentication requirements. | You already have an email provider or mailbox and it supports SMTP access for your account. |
| Provider API or OAuth | A plugin integration and the provider’s current authorization process; this may require account authorization or application registration. | Your provider and plugin support a direct connection, or the provider requires an approved authorization flow. |
| Transactional-email service | An account with a service designed to send transactional messages, plus a plugin integration it supports. | Your sending volume, reliability needs, or operational setup makes a dedicated sending service suitable. |
Plugin listings name Gmail or Google Workspace and Microsoft 365 or Outlook integrations, as well as services such as Amazon SES, SendGrid, Mailgun, Postmark, and Brevo. The available mailers, permissions, and features depend on the specific provider and plugin. For example, see the vendor-submitted listings for FluentSMTP and Post SMTP. Neither an SMTP setup nor an API connection guarantees inbox placement.
Do not copy generic server or port settings from an unrelated guide. Check your provider’s current documentation or ask the account administrator for the correct values and permitted authentication method. Provider policies can change, and settings can differ by account.
#1 Best Overall
Connect the account and verify delivery
- Identify the messages and sender. Decide which WordPress messages need to go out and which authorized sender address and display name should appear on them. Use an address the provider allows your site to send from.
- Choose a compatible mail plugin and route. Check that the plugin supports your provider and the connection method you intend to use. Confirm any plugin or provider requirements in their current documentation.
- Get the provider’s connection instructions. For SMTP, obtain the server, port, encryption, username, and authentication requirements. For API or OAuth, follow the plugin’s and provider’s authorization instructions. Do not post passwords, app credentials, or API secrets in public support requests.
- Configure the mailer in WordPress. In the plugin’s settings, select the matching provider or an equivalent of “Other SMTP,” then enter the provider-approved details. Set the sender name and address as required by the provider and plugin.
- Send a test, then trigger a real site message. Use the plugin’s test-email function if available. Then submit the relevant form, trigger a password reset, or perform the store action that should send a notification. A successful test alone does not confirm that every site feature is using the intended sender or message path.
- Review errors and logs. If the plugin provides logs, inspect them for authentication, connection, or rejection details. Post SMTP’s plugin listing describes test-email and logging features; this is vendor-submitted product information, so check the installed version’s documentation for the exact workflow.
Troubleshoot messages that do not send
- Check sender authorization. Confirm that the From address is valid and permitted by the mail server or provider. WordPress.org’s troubleshooting guidance notes that WordPress may default to
wordpress@yourdomain.comwith “WordPress” as the From name, and warns that an address on a domain not handled by the mail server may fail. A plugin or provider may change the behavior, so check the values actually configured for your site. - Recheck credentials and authentication requirements. Make sure the username and credentials are current, and verify that the provider still permits the selected SMTP authentication method. If it requires API/OAuth authorization, use the supported flow instead of assuming a password-based SMTP setup will work.
- Check network restrictions. If credentials and sender settings are correct, ask your host whether it blocks the outbound connection or relevant port. A WordPress.org support answer on external SMTP configuration mentions server-side port or firewall restrictions as possible causes; your host can confirm whether they apply to your site.
- Use the provider’s instructions for account-specific settings. Do not assume that a particular port, app password, or authentication option is universal across Gmail, Microsoft 365, hosting email, or other providers. Current first-party provider instructions and administrator guidance take precedence over old forum answers.
Changing the mail route addresses how WordPress submits messages; it does not by itself establish that recipients’ mail systems will place them in the inbox. Confirm successful sending with the test and real-message checks above, and investigate any delivery or rejection details reported by the provider.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
