Skip to content

Sending to a large list quickly

From a few thousand recipients onwards the question comes up how long a send takes — and what the numbers in the backend mean while it runs.

This guide explains how sending works and shows the two levers that make it faster.


How one run works

A newsletter does not go out in one go. Sending happens in runs, triggered by the cron.

Within a run the plugin hands the mails to your mail server one at a time and ticks each one off right after handing it over. The run ends when one of these happens:

Time is up Over the command line there is no limit. Otherwise the run stops by itself ten seconds before your server's time limit
The cap is reached Newsletters per run, 200 out of the box
The queue is empty Done
Three rejections in a row The mail server is unhappy right now. The rest is left for later

If a run ends on time, it schedules the next one immediately — it does not wait for the next interval. If it ends at the cap, it waits: the cap is a brake you set yourself.

Delivery does not happen within the run

The plugin hands the mail to your mail server; delivery happens afterwards, by that server. So the send is finished before the last mail has arrived.

What „278 / 3731" means

The first number is the processed recipients — not necessarily the sent ones. A mail that failed for good, say at an invalid address, counts too.

What happened to which address is in the delivery log: Sent, In queue, Next attempt at … or Not sent, each with a reason.

If a third number appears, recipients have been deleted since the start — see Sending and scheduling.

If the browser hangs or breaks off

Clicking Start sending can run the browser into a timeout. That looks worse than it is.

Question Answer
Are the mails so far out? Yes. Each one is ticked off individually
Are the rest lost? No. They stay in the queue, the next run takes them
Does anyone get one twice? At most the single one being handed over at the moment of the break
Is sending stuck now? No. A lock prevents two runs at once; if a run breaks off hard, it is released at once

Since 2.1.0 a run stops by itself ten seconds before the time limit anyway. Breaking off mid-work is the exception.


The arithmetic

What goes out within an hour is:

cap per run × runs per hour

With the default of 200 and an hourly interval that is 200 mails an hour — at 3731 recipients a good three days. With 500 every 15 minutes it is 2000 an hour and under two hours.

The run itself is not the bottleneck: it finishes within seconds and then waits for the next interval.

Getting faster

The most effective step is a real cron job on the server.

Without a server cron With a server cron
What runs WP-Cron, triggered by page views A cron job of the operating system
Time limit PHP's, often 30 seconds none
Newsletters per run do not set to 0 may be 0: no cap
Interval 15, 30 or 60 minutes as often as you like, say every 5 minutes

With a server cron and no cap, one run sends everything that is waiting. How to set it up is under Sending settings.

Without a server cron do not set 0

Then sending runs inside a visitor's page view, and that ends at PHP's time limit. Instead of raising the cap, set up the external cron.

The cap still makes sense

Many hosts allow only a certain number of mails per hour. A cap just below that avoids your mail server rejecting anything at all — better than repeating rejected mails later.

„Start sending" with large lists

The button sends in portions of at most twenty seconds and carries on by itself, with Send next portion and Pause next to it. It no longer hangs in the browser.

For watching it is fine. For day-to-day operation let the cron do the work — it needs no open browser.