[Plugin: Subscribe2] Showing WP-Cron's importance in Description

@grubbyseismic,

This post was made nearly 5 years ago when cron was not part of the WordPress core. You don’t need any additional plugin now provided you are using a recent version of WordPress.

Oh I see!
I may just leave the recipients restriction in place and see how it gets on!

There was definitely no mail being sent (as of yesterday), apart from single-recipient tests.

I have now, however, added a job into the releavant part of control panel of the server. It is due to fire in about three minutes, then again at the same time on a weekly basis.

I used the hack you suggested previously to “un-stick” the cron schedule (i.e. change the post-type twice). The next job, according to WP, is next week.

So I suppose that means I’m no closer to finding out why there was no mail being sent in the first place?…

@grubbyseismic,

You can try using the setting to limit the number of email recipients per out going email; that is what the old DREAMHOST parameter did.

If emails are still failing check with your hosting provider about their restrictions on outgoing server emails.

Yes, I realise that’s the fallback.

Hopefully with the cron schedule in place it will work! Otherwise I’m worried my client will enforce another plugin to be used, though that isn’t your problem!

Out of interest, it’s the PHP function mail() that would be blocked, isn’t it?

@grubbyseismic,

It is that function, it’s more throttled then blocked and further down the line really. mail() usually sends the details to sendmail or postfix on the server, these are binary applications rather than the PHP mail() which is just a function.