Emails Not Sending

If subscribers aren’t receiving Benecaster emails, the cause is almost always one of four things: no SMTP configured, the queue is throttled, the email type is switched off, or the message is being delivered but filtered as spam.

Work through them in that order — the checks get progressively more involved.

Start With the Queue Depth

Go to Benecaster → Settings → Email and look at the queue depth. It tells you which half of the problem you have.

• Queue depth is zero, and no email arrived — the email was never queued, or it was sent and lost after handoff. Skip to The email type is switched off and Delivered but filtered.
• Queue depth is large and not falling — emails are queued but not going out. That’s a sending problem: continue below.

1. WordPress Has No Working SMTP

This is the most common cause by a wide margin, and it isn’t specific to Benecaster — it affects every plugin on the site that sends mail.

By default WordPress sends through PHP’s mail() function, which most hosts either disable or route in a way that mail providers reject outright. Benecaster does not include its own mail transport; it hands messages to WordPress.

Check: send yourself a test from any plugin that offers one, or use an SMTP plugin’s built-in test. If nothing arrives from any source, SMTP is the problem.

Fix: install and configure an SMTP plugin — WP Mail SMTP and FluentSMTP are both widely used — pointed at a real transactional provider. See SMTP Setup.

Avoid sending through a personal mailbox provider. Consumer Gmail and Outlook accounts have low limits and aggressive automated blocking, and a batch of subscriber emails looks exactly like the behavior they’re built to stop.

2. The Sending Rate Is Throttling the Queue

Benecaster dispatches from an internal queue at a configurable rate — Emails per hour, default 300, range 10–2,000.

If the rate is set well below your volume, mail still sends, just slowly. A backlog after a bulk enrollment or a large import is normal and clears on its own.

Check: watch the queue depth over several minutes. Falling steadily means it’s working through the backlog — that’s throttling, not failure. Static or rising means something else is wrong.

Fix: raise the rate to match what your SMTP provider actually allows, and no higher. Setting it above your provider’s ceiling causes deferrals or blocks, which is worse than sending slowly. See Why are my episode emails sending slowly? for how to pick a number.

Note that admin and security emails bypass the queue entirely and send immediately. If you’re receiving license notices but subscribers aren’t getting welcome emails, the queue is the thing to look at.

3. The Email Type Is Switched Off

Each email type has a per-show toggle in Benecaster → Settings → Email. Toggles are per show, so an email can be live on one show and off on another — worth checking if the problem only affects one podcast on a multi-show install.

Check: confirm the specific email you expect is enabled for the specific show involved.

Also check whether a filter is suppressing it. benecaster_email_should_send can block a send from a snippet in your theme or another plugin, and produces exactly the same symptom as a disabled toggle. If the toggle is on and nothing is queuing, search your site’s custom code for that filter name.

4. Delivered, but Filtered as Spam

If the queue drains and your provider’s logs show successful delivery, the mail is arriving and being filed somewhere the subscriber isn’t looking.

Check: your SMTP provider’s dashboard is the authority here. It will show accepted, delivered, bounced, and complained. If it shows delivered, the problem is downstream.

Fix: authenticate your sending domain — SPF, DKIM, and DMARC records. Transactional providers document exactly which DNS records to add, and this single step resolves the large majority of spam-filing problems. Sending from an address at your own domain, rather than a free mailbox provider, matters for the same reason.

Ask the affected subscriber to check their spam folder and mark the message as not spam, which helps future deliveries to that person.

When It’s One Subscriber, Not All

If mail flows normally except to one person, the cause is specific to them rather than to your configuration:

• They unsubscribed. Broadcasts respect unsubscribe preference; transactional emails like welcome and token reset do not, so an unsubscribed subscriber still receives those.
• Their address has hard-bounced and your provider has suppressed it. Provider dashboards maintain a suppression list — check whether they’re on it.
• The address on their account has a typo. Check the subscriber record in Benecaster → Subscribers.

If a Subscriber Needs Their Feed URL Now

Don’t leave someone waiting while you debug delivery. Open their record in Benecaster → Subscribers and copy their feed URL directly, then send it by whatever channel already works.

Their URL is also always available to them on the subscriber account page once they’re logged in — no email required.