In this article, we\u2019ll explain some likely reasons WordPress isn\u2019t sending emails. Then we\u2019ll show you how to fix this issue and configure your contact forms<\/a><\/span> so that they properly deliver emails as well. Let\u2019s go!<\/p>\n\n\n\n\n\n By default, WordPress uses the PHP mail() function to send emails. Unfortunately, many hosting servers are not configured to use this function, making it impossible to process those emails.<\/p>\n\n\n\n Another reason emails from your site may not get delivered is unintended side effects from efforts to reduce spam. Most email providers attempt to verify that an email is coming from the address it claims.<\/p>\n\n\n\n However, the address used to send email from your website likely uses spoofing<\/a><\/span>. Without spoofing, an email sent from your website might look like \u201cadmin@yourserver.yourwebhost.com\u201d. Spoofing enables you to change that address to a more reasonable one, such as \u201cadmin@yourwebsite.com\u201d.<\/p>\n\n\n\n Unfortunately, spoofing can also serve nefarious purposes, and without authentication, email providers can\u2019t tell the difference. Mailbox providers check three DNS records \u2014 SPF, DKIM, and DMARC \u2014 to decide whether to trust a message, and mail sent through PHP\u2019s mail() function typically carries none of them. We\u2019ll show you how to add those records below. Therefore, it can sometimes cause your emails to end up in recipients\u2019 spam folders.<\/p>\n\n\n\n In addition to spoofing, there are a lot of other reasons why emails might go to spam. Some of the most common possibilities are:<\/p>\n\n\n\n A flagged IP address is easy to check: look up your server\u2019s sending IP with a blocklist checker such as MXToolbox<\/a>. If it shows up on a list, request delisting through that blocklist\u2019s own process, ask your host to investigate, or switch to a reputable SMTP or transactional email service that sends from its own well-maintained IPs.<\/p>\n\n\n\n One way to keep your emails out of the spam bin is to use Simple Mail Transfer Protocol (SMTP) rather than PHP mail(). This protocol is the industry standard and uses proper authentication.<\/p>\n\n\n\n Put simply, emails sent via authenticated SMTP have a higher chance of being delivered than those sent with PHP\u2019s mail() function. You can use a few different methods to set up your WordPress site to send emails via SMTP.<\/p>\n\n\n\n SMTP gets your mail sent; SPF, DKIM, and DMARC get it believed. These three DNS records are how mailbox providers verify that a message really comes from your domain. They\u2019re no longer optional. Google\u2019s Email sender guidelines<\/a> have required SPF or DKIM from every sender to Gmail accounts since February 1, 2024, and warn that unauthenticated messages \u201cmight be marked as spam or rejected.\u201d Senders of 5,000 or more messages per day need all three.<\/p>\n\n\n\n Here\u2019s what each record does, in plain language:<\/p>\n\n\n\n Mail sent through PHP\u2019s mail() function typically carries none of these, which is a big part of why it gets junked. You add all three as DNS records wherever your domain\u2019s DNS is managed, but the values themselves come from whichever service actually sends your mail: DreamHost if you send through DreamHost\u2019s SMTP servers, Google if you send through Gmail or Google Workspace, or your transactional email service if you use one. Records copied from a provider you don\u2019t send through won\u2019t pass verification. If DreamHost sends your mail, DreamHost\u2019s help docs walk through each one: adding an SPF record<\/a>, DKIM records<\/a>, and creating a DMARC policy<\/a>.<\/p>\n\n\n\n To verify your setup, send a message to a Gmail address you own, open it, and choose Show original<\/em>. You should see \u201cPASS\u201d next to SPF, DKIM, and DMARC.<\/p>\n\n\n\n Before you change any settings, take 2 minutes to confirm the problem. You may not need the full fix at all.<\/p>\n\n\n\n First, check your admin email address. In your WordPress dashboard, go to Settings > General<\/em> and look at the Administration Email Address<\/em> field. A simple typo here, or an address on a domain that isn\u2019t yours, is enough to break notifications. While you\u2019re at it, confirm the From<\/em> address in your contact form plugin matches your website\u2019s domain.<\/p>\n\n\n\n Next, send a test email. The WP Mail SMTP<\/a> plugin we use throughout this guide includes a built-in email test \u2014 send a message to an address you control, then check both the inbox and the spam folder. If the test fails, the error it returns tells you where to look. If it lands in spam, your emails are sending but failing trust checks. Missing authentication is the most common cause, so start with the SPF, DKIM, and DMARC records above.<\/p>\n\n Now that we\u2019ve touched on a few reasons WordPress emails aren\u2019t making it to their intended recipients, let\u2019s look at three ways to fix the problem.<\/p>\n\n\n\n Using your hosting account email is the simplest way to get your WordPress messages moving as expected. We\u2019ll show you how to set this up, using our own DreamHost web hosting<\/a><\/span> as an example.<\/p>\n\n\n\n Begin by downloading and installing the WP Mail SMTP<\/a><\/span> plugin. From your WordPress dashboard, navigate to WP Mail SMTP > Settings<\/span>.<\/p>\n\n\n There are several fields you\u2019ll need to fill in on this screen. From Email<\/span> is the address from which you want your emails sent. You\u2019ll also need to check the Force From Email<\/span> box. The From Name<\/span> field is the name you\u2019d like the email to come from. You can check the Force From Name<\/span> box if you\u2019d like.<\/p>\n\n\n\n Finally, select Other SMTP<\/span> as your mailer. Doing this will cause a Return Path<\/span> section to appear. Be sure to click on the box in that section as well.<\/p>\n\n\n\n Now you can populate the other SMTP options. We\u2019ll use DreamHost to demonstrate again, but the information should be similar if you use another web host.<\/p>\n\n\n First, make sure to toggle on Authentication<\/span>. For the SMTP Host,<\/span> use \u201csmtp.dreamhost.com\u201d. When you select TLS<\/span> encryption, the plugin should auto-populate the SMTP port<\/span> as \u201c587\u201d.<\/p>\n\n\n\n Next, you can enter your DreamHost email address<\/a> and password<\/a>. Finally, click on the Save Settings<\/span> button, and you should be ready to go. You can try sending a test email to be sure that everything is working properly. All current DreamHost SMTP values are listed in DreamHost\u2019s email client configuration overview<\/a> if you want to double-check them.<\/p>\n\n\n\n If you prefer, you can send your site\u2019s mail through a Gmail or Google Workspace account. This method also uses the WP Mail SMTP plugin, but it\u2019s significantly more involved: you\u2019ll create your own app in Google Cloud Console so WordPress has authorized access to Google\u2019s API. Per WP Mail SMTP\u2019s setup guide<\/a>, the manual route takes roughly 30\u201360 minutes, and you\u2019ll have to repeat it if you ever switch Google accounts.<\/p>\n\n\n\n There is a shortcut: WP Mail SMTP Pro includes a One-Click Setup for the Google Workspace \/ Gmail mailer that connects your site in under 2 minutes, with no manual configuration. If you\u2019d rather never open Google Cloud Console, that\u2019s the route to take.<\/p>\n\n\n\n For the manual setup, start in the plugin. Navigate to WP Mail SMTP > Settings<\/em>, fill out the From Email<\/em> and From Name<\/em> fields as described above, and select Google \/ Gmail<\/em> as your mailer. A new Google \/ Gmail<\/em> section will appear \u2014 keep this tab open, since you\u2019ll paste two values into it shortly.<\/p>\n\n\n\n In a new tab, log in to your Google account and open the Google Cloud Console<\/a>. Click the project drop-down in the top toolbar, select New Project<\/em>, give the project any name you\u2019d like, and click Create<\/em>.<\/p>\n\n\n\n Next, enable the Gmail API. In the console\u2019s sidebar, go to APIs & Services > Library<\/em>, then find the Gmail API<\/em> under the Google Workspace<\/em> category (or simply search for it) and click Enable<\/em>.<\/p>\n\n\n\n Before Google will issue credentials, it asks you to configure an OAuth consent screen. Choose External<\/em> unless your organization uses Google Workspace, then enter an app name and your contact email address. You can click Save and Continue<\/em> through the remaining prompts \u2014 you\u2019re the only person who will ever see this screen.<\/p>\n\n\n\n Now create the credentials. Go to APIs & Services > Credentials<\/em>, click Create Credentials > OAuth client ID<\/em>, and choose Web application<\/em> as the application type. Switch back to your WP Mail SMTP tab, copy the Authorized Redirect URI<\/em> shown there, paste it into the Authorized redirect URIs<\/em> field in Google Cloud Console, and click Create<\/em>.<\/p>\n\n\n\n Google will display your Client ID<\/em> and Client Secret<\/em>. Paste both into the matching fields in the WP Mail SMTP settings and click Save Settings<\/em>. When the page refreshes, click Allow plugin to send emails using your Gmail account<\/em> and sign in to grant permission.<\/p>\n\n\n\n Two final steps: if Google created your app with a Testing<\/em> publishing status, switch it to production (WP Mail SMTP\u2019s Google Workspace \/ Gmail documentation<\/a> covers that step, and every screen above, in click-by-click detail). Then send a test email to confirm the connection is working.<\/p>\n\n\n\n If your site sends more than the occasional notification \u2014 order receipts, password resets, or anything at volume \u2014 a dedicated transactional email service is the sturdiest option. Services like SendLayer, SMTP.com, Brevo, Mailgun, and Amazon SES exist solely to deliver application email from authenticated, well-maintained infrastructure.<\/p>\n\n\n\n WP Mail SMTP includes built-in mailers for these providers (SendLayer is its top recommendation<\/a>), and because those integrations use each provider\u2019s direct API, your mail still goes out even if your host blocks SMTP ports. Most offer free tiers to start: Brevo, for example, includes 300 free emails per day, per the WP Mail SMTP plugin page. Setup is usually just an account, a couple of DNS records to verify your domain, and an API key pasted into the plugin.<\/p>\n\n\n\n Here\u2019s the short version:<\/p>\n\n\n\n![\"Ad](\"https:\/\/www.dreamhost.com\/blog\/wp-content\/themes\/blog2018\/assets\/img\/lazy-loading-transparent.webp\"){kind=spacer}
<\/div>\n\n\n\n\n Why You\u2019re Not Receiving Emails From WordPress<\/span><\/h2>\n\n\n\n
How to Stop Email From Going to Spam<\/span><\/h2>\n\n\n\n
\n
Add SPF, DKIM, and DMARC Records to Your Domain<\/span><\/h3>\n\n\n\n
\n
Before You Start: Confirm What\u2019s Actually Failing<\/span><\/h2>\n\n\n\n
How to Set Up WordPress to Send Emails Via SMTP (3 Ways)<\/span><\/h2>\n\n\n\n
1. Send Email Using Your DreamHost SMTP Settings (WP Mail SMTP)<\/span><\/h3>\n\n\n\n
![\"The](\"https:\/\/www.dreamhost.com\/blog\/wp-content\/smush-webp\/2021\/02\/3ad7ab01-db45-46fc-a883-9235ae526e5a_dh-wp-not-sending-email-2.jpg.webp\")
<\/figure>\n<\/div>\n\n\n![\"WP](\"https:\/\/www.dreamhost.com\/blog\/wp-content\/smush-webp\/2021\/02\/92d57bc1-c6ba-491d-b9c5-c2b0ffb33e4d_dh-wp-not-sending-email-5.jpg.webp\")
<\/figure>\n<\/div>\n\n\n2. Send Email Using Your Gmail or Google Workspace Account<\/span><\/h3>\n\n\n\n
3. Send Email Using a Transactional Email Service<\/span><\/h3>\n\n\n\n
Which Sending Method Should You Pick?<\/span><\/h3>\n\n\n\n
![\"The](\"https:\/\/www.dreamhost.com\/blog\/wp-content\/smush-webp\/2021\/02\/7b0e3743-7b58-42e2-9951-08da63d8b249_dh-wp-not-sending-email-3.jpg.webp\")
<\/figure>\n<\/div>\n\n\n![\"The](\"https:\/\/www.dreamhost.com\/blog\/wp-content\/smush-webp\/2021\/02\/47d065b3-b71a-40b2-a3ee-1774566d6562_dh-wp-not-sending-email-13.jpg.webp\")
<\/figure>\n<\/div>\n\n\n![\"Settings](\"https:\/\/www.dreamhost.com\/blog\/wp-content\/smush-webp\/2021\/02\/3954e843-8b5b-4d1b-9706-98ad5b444559_dh-wp-not-sending-email-14.jpg.webp\")
<\/figure>\n<\/div>\n\n\n