WordPress sends mail through PHP by default, and on most hosting that mail quietly does not arrive. There is no error, no bounce, and nothing in the dashboard to tell you — the password reset simply never lands, and the customer assumes your site is broken.
The fix is to send through a real mail server that authenticates as you, which is what SMTP does. These guides cover connecting one: the ports and encryption choices and which combination your host actually permits, app passwords versus OAuth, and the specific setup steps for the providers most sites use.
Getting connected is only half of it. The other half is deliverability — whether the receiving server believes the mail is really from you. That is DNS work rather than WordPress work, and the three records involved are covered here, as is the question of what to do when mail is accepted but filed as spam.
A further group of articles is diagnostic, because email fails in ways that look identical from the dashboard. Authentication refused, connection refused, connection timed out, a message accepted then rejected downstream, a queue that stops draining. Each has a different cause and a different fix, and the logs tell you which one you have.
If mail is failing right now, start with the diagnostic articles rather than the setup guides. Reconfiguring a connection that was never the problem is the most common wasted afternoon here.
Troubleshoot an SMTP 550 spam block in WordPress by stopping blind retries, preserving the exact response and SMTP stage, comparing accepted mail, and fixing the proven policy cause.
Diagnose WordPress emails stuck in a queue by preserving the backlog, checking scheduler and worker health, isolating stale locks or bad jobs, and draining a marked sample safely.
Configure Microsoft 365 SMTP for WordPress without weakening tenant security. Check mailbox permissions, authentication, sender identity, and a real delivery event.
Connect WordPress to Gmail SMTP with an organization-owned OAuth client, an exact redirect URI, limited access, protected tokens, and a tested revocation path.
Improve WordPress email placement by checking authentication, sender reputation, recipient quality, content, volume, and real mailbox results.
Configure WordPress SMTP with an approved sender, protected authentication, one traceable transport route, and tests using real site events.
Diagnose missing WordPress email by tracing the trigger, wp_mail, SMTP transport, provider response, and final delivery before changing configuration.