Troubleshooting
MailPoet Not Sending Emails: Causes and How to Fix It

Short answer
MailPoet usually stops sending because its background queue is stuck, the sending method is misconfigured, or your host limits outgoing mail. Send a test email, check the System Status page under MailPoet Help, fix WP-Cron if it is not running, and confirm your SMTP or sending service details.
Key takeaways
- A stuck sending queue is the most common cause.
- MailPoet > Help > System Status shows cron and queue errors.
- Low-traffic sites may need a real server cron job.
- Hosts often block or limit PHP mail, so use SMTP or a sending service.
- Emails marked sent but unseen usually point to SPF, DKIM or DMARC gaps.
Why is MailPoet not sending emails?
MailPoet usually stops sending because its background sending task is not running, the sending method is misconfigured, or your host blocks or limits outgoing mail.
MailPoet does not send every email the moment you click Send. It adds the newsletter to a queue, and a background task works through that queue in small batches. If that task stalls, emails sit in the queue and nothing goes out.
The other big group of causes sits outside the plugin. Your hosting server may block PHP mail, an SMTP login may have expired, or your domain may lack the DNS records that inbox providers expect. In those cases MailPoet tries to send, but the email is rejected or lands in spam.
The good news is that MailPoet tells you a lot about what is wrong if you know where to look. Start with the checks below before changing any settings.
How do you check what MailPoet is actually doing?
Open MailPoet > Help > System Status to see whether the cron task is running, when it last ran, and whether the sending queue reports errors.
The System Status page is the most useful screen for this problem. MailPoet explains each item in its guide to understanding the System Status page.
Look at these items first:
- Cron ping or task scheduler status, which shows if MailPoet can trigger its own background process
- Last run times for the sending task, which tell you if it stopped recently
- Sending queue status, including paused or failed states
- Current sending method and any error messages next to it
Next, open the Emails list and look at the status under each newsletter. A newsletter stuck on Sending with a number like 0 of 500 means the queue never started. A paused newsletter usually shows an error message with a Resume link.
Also check the Send a test email button under MailPoet > Settings > Send With. If the test works but newsletters do not, the problem is the queue. If the test fails too, the problem is the sending method.
Is the MailPoet sending queue stuck?
Yes, a stuck queue is the most common cause; it happens when the background task cannot run, often because WP-Cron is disabled or the site gets too few visits.
MailPoet's background task depends on WordPress being able to run scheduled jobs. WordPress uses WP-Cron, which only fires when someone visits the site. On a quiet site or a staging site, that may not happen often enough. The WordPress cron handbook explains this behavior in detail.
Common reasons the queue stalls:
DISABLE_WP_CRONis set to true in wp-config.php, but no real server cron job was added- The site is behind a login wall, maintenance page or HTTP password, so loopback requests fail
- A security plugin or firewall blocks requests the site makes to itself
- A caching layer serves cached pages so WordPress code never runs
Our guide on whether WP-Cron runs automatically explains what triggers scheduled tasks and why quiet sites fall behind.
MailPoet's own article on sending that does not work walks through these checks. If your host has disabled WP-Cron, set up a real cron job. Our guide on disabling WP-Cron and using a real cron job shows how.
To test loopback requests, open Tools > Site Health. If it reports that loopback requests or scheduled events failed, fix that first. The WordPress team documents these checks in the Site Health screen guide.
Is your sending method set up correctly?
Check MailPoet > Settings > Send With; if you use your host or SMTP, the credentials, port and encryption must match your provider exactly, or every email fails.
MailPoet supports three broad sending options:
| Sending method | How it works | Common failure |
|---|---|---|
| MailPoet Sending Service | MailPoet sends through its own servers | Unverified sender domain, account limits, key not activated |
| Your web host (PHP mail) | The server's mail function sends the email | Host blocks or throttles PHP mail |
| SMTP or third-party service | Your provider's SMTP or API sends the email | Wrong password, port, encryption or expired API key |
If you send through your host, many shared plans cap hourly email or block PHP mail entirely. Ask your host about their limits, or switch to SMTP or a dedicated service.
If you use SMTP, confirm the host name, port (commonly 587 for TLS or 465 for SSL), username and app password. Our MailPoet SMTP settings guide covers each field.
If you use the MailPoet Sending Service, confirm the key is active and the sender address uses a domain you have verified. MailPoet may hold sending until the domain is authorized. Plan features and limits change, so check MailPoet's current plan page for your quota.
Are sending frequency limits slowing things down?
Sometimes emails are sending, just slowly, because MailPoet's sending frequency setting only lets a set number of emails out per few minutes.
When you send through your host or SMTP, MailPoet lets you pick a sending frequency. This protects you from your host's hourly cap. If the frequency is low and your list is large, a newsletter can take many hours to finish.
This looks like a failure, but it is the plugin respecting your limits. Check the progress number on the Emails list. If it climbs slowly, sending works.
Raise the frequency only if your host or provider allows more. Sending faster than the cap can get your account blocked, which causes a much bigger problem.
Are your emails being sent but landing in spam?
If MailPoet shows emails as sent but subscribers never see them, the messages are probably filtered as spam or rejected because your domain lacks SPF, DKIM or DMARC records.
Gmail, Yahoo and other inbox providers now expect bulk senders to authenticate their domain. Google's email sender guidelines list the requirements, including SPF, DKIM, DMARC and an easy unsubscribe.
Fix deliverability with these steps:
- Use a From address on your own domain, not a free Gmail or Yahoo address
- Add or correct SPF and DKIM records for the service that sends your mail
- Publish a DMARC record, starting with a monitoring policy
- Keep the unsubscribe link in every newsletter
- Remove addresses that bounce repeatedly
Our guide to SPF, DKIM and DMARC for WordPress email explains each record in plain English.
Also ask a few subscribers to check spam and promotions folders. If emails are there, the plugin is working and the fix is all about reputation and authentication.
Could a plugin or theme conflict be the cause?
Yes, another plugin can break MailPoet's queue or replace the mail function, especially other SMTP plugins, security plugins and aggressive caching or optimization tools.
A second email plugin, such as an SMTP plugin, can override how WordPress sends mail. That is fine for transactional email, but it can confuse which settings MailPoet is really using.
Security plugins can block the requests MailPoet uses to trigger its queue. Caching and minification plugins sometimes break the admin screens where you resume sending.
To find a conflict:
- Take a backup or use a staging copy
- Deactivate all plugins except MailPoet
- Switch to a default theme like Twenty Twenty-Five
- Send a test and resume the queue
- Turn plugins back on one at a time until it breaks again
Our plugin conflict guide covers this process in more detail.
What if only automatic emails are not sending?
When newsletters work but welcome emails, post notifications or WooCommerce follow-ups fail, the automation itself is usually inactive, misconfigured or waiting on a trigger that never fired.
Automatic emails run on triggers, such as a new subscriber confirming or a new post being published. If the subscriber never confirms, or the trigger list is wrong, nothing is scheduled.
Check these points:
- The automation or automatic email is set to Active
- The subscriber is confirmed if you use double opt-in
- The trigger uses the right list or segment
- Post notification timing matches when you actually publish
We cover these in more depth in MailPoet automation not working.
How do you fix MailPoet not sending, step by step?
Work from the simplest check to the hardest: send a test, read System Status, fix cron, confirm the sending method, then check deliverability and conflicts.
Here is the full order we suggest:
- Send a test email from MailPoet > Settings > Send With
- Open MailPoet > Help > System Status and note any errors
- Resume any paused newsletter from the Emails list
- Check Tools > Site Health for loopback or scheduled event problems
- Confirm WP-Cron runs, or add a real server cron job
- Re-enter SMTP or API credentials and test again
- Ask your host about email limits and blocked ports
- Add SPF, DKIM and DMARC records for your sending service
- Test for plugin and theme conflicts on staging
- Turn on WordPress debugging and read the log if errors persist
For step 10, see how to enable debug mode in WordPress. Errors in the log often name the exact file or service that failed.
When should you contact MailPoet support or your host?
Contact your host if PHP mail or SMTP ports are blocked, and contact MailPoet support if System Status shows errors you cannot clear after fixing cron and credentials.
Before you reach out, collect useful details. MailPoet support usually asks for the System Status report, which you can copy from the same page. Your host will want the exact error message and the time you tried to send.
If you use the free plugin, you can also post in the MailPoet support forum on WordPress.org. Include your WordPress version, PHP version and sending method, but never post passwords or API keys.
How can you stop MailPoet sending problems coming back?
Use a dedicated sending service, keep cron reliable, authenticate your domain, and check System Status after updates so small problems are caught early.
A few habits prevent most repeat problems:
- Use the MailPoet Sending Service or a dedicated SMTP provider instead of your host's PHP mail
- Add a real cron job if your site gets little traffic
- Keep MailPoet, WordPress and PHP up to date
- Test one newsletter to yourself before every big send
- Clean your list of hard bounces and inactive addresses
If you are new to the plugin, our guide on how to use MailPoet in WordPress covers setup from the start, including the sending options.
Frequently asked questions
Why does MailPoet say sending but nothing goes out?
The background task that processes the queue is probably not running. Check MailPoet's System Status page, confirm WP-Cron works, and make sure nothing blocks the site from calling itself, such as a password wall or firewall rule.
Does MailPoet need WP-Cron to send emails?
MailPoet relies on a background task scheduler to process its queue. If WP-Cron is disabled or rarely triggered on a quiet site, sending stalls. Adding a real server cron job usually fixes slow or stuck queues.
Why do MailPoet test emails work but newsletters do not?
A working test proves the sending method is fine. The issue is usually the queue, a paused newsletter, or a sending frequency so low that large lists take hours. Check the progress number on the Emails list.
Can my web host stop MailPoet from sending?
Yes. Many shared hosts block PHP mail, limit emails per hour, or block SMTP ports. Ask your host about limits, or switch to the MailPoet Sending Service or a dedicated SMTP provider.
Why are MailPoet emails going to spam?
Inbox providers expect bulk senders to authenticate their domain. Use a From address on your own domain, add SPF and DKIM records for your sending service, publish a DMARC record, and keep a clear unsubscribe link.
Sources
- Sending Does Not Work MailPoet Knowledge Base
- Understanding the MailPoet System Status Page MailPoet Knowledge Base
- Site Health Screen WordPress.org Documentation
- Email sender guidelines Google Workspace Admin Help
- MailPoet plugin support forum WordPress.org
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.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


