@jeman_wp
I suspect this might be linked to how the emails are being sent – are you using any other email plugins? Try deactivating these or consider adding in a plugin that queues emails in a database and sends them in stages.
I don’t use any other plugin for sending emails. What plugins are you suggesting for this type of job?
How can I delete all subscribers from the DB? It could be a good feature to have in the plugin.
I tried to remove all entries in the db wp_usermeta where meta_key is like S2.
But in the subscribers tab in the plugin settings I can still see them all but without any e-mail address.
@jeman_wp
Public Subscriber are stored in the ‘subcribe2’ table in the database so you can drop the table.
Registered Subscribers have data stored in the user and usermeta tables. The easiest way to unsubscribe them is in the Bulk Management sedction at the bottom of the Subscribe2->Subscribers page in the Registered Subscribers tab and Unsubscribe users from all categories.
The other option is to uninstall and re-install the plugin. This would remove all subscriber data and settings – beware if you’ve customised the email notification template that you’d loose that too.
Hi there,
What is this option in the plugin settings
Restrict the number of recipients per email to (0 for unlimited):
?
Because it looks to be my issue. From the documentation it is not really comprehensible what it is used for.
Can you please specify a bit more in detail?
Thank you
@jeman_wp
The below is from the FAQ, does that help?
Some hosting providers place a restriction on the maximum number of recipients in any one email message. Some hosts simply block all emails on certain low-cost hosting plans.
Subscribe2 provides a facility to work around a restriction of the maximum number of recipients per email by sending batches of emails. To enable this feature, go to Subscribe2->Settings and locate the setting to restrict the number of recipients per email. If this is set to 30 then each outgoing email notification will only contain addresses for 30 recipients.
Reminder: Because Subscribe2 places all recipients in BCC fields, and places the blog admin in the TO field, the blog admin will receive one email per batched delivery. So if you have 90 subscribers, the blog admin should receive three post notification emails, one for each set of 30 BCC recipients.
Batches will occur for each group of message as described above. A site like this with many public and registered subscribers could conceivably generate a lot of email for your own inbox.
So this can’t solve my issue.
I don’t get why some(not all) of my subscribed users are getting spammed by a lot of e-mails, between 20 and 40 of them sometimes.
Also I don’t understand why I should use a plugin which queues the emails in a db.
I lately re-categorized the website categories and I thought this might have messed up the subscribing system, but for those users I also checked if there were any duplicates in the db and I found nothing like this.
Do you have any idea why this is happening?
thanks
@jeman_wp
Let’s see if I can try to explain this a little better.
WordPress and Subscribe2 run on a web server – the purpose of these servers is to serve web pages to your human readers and also to bots from search engine companies for example.
Subscribe2 takes the WordPress post content and converts it into an email for sending. Now, while your web server _can_ send emails it really isn’t designed to do this as a primary function so it is a low priority task and things can easily start to go wrong. for example, becuase it isn’t a primary task and your hosting provider have most likely made a pledge you you to deliver a certain amount of ‘uptime’ they will have configure the server to assign email sending a low priority, they will kill long duration scripts and will limit the amount of emails you can send in pre-specified time periods.
So, Subscribe2 will regularly fall victim to hosting companies limits which can result in failed emails or conversely duplicate emails. Why? Well the entire internet email system is designed to guarantee delivery first and foremost – even if that means multiple delivery; that is considered better than failure. Second reason might be because the server keeps resetting the emailing list and starting again – hence the duplication.
The suggestions above, staging the deliver by queuing the emails for delivery for example should relieve many of the issues you seem to be getting.
I just published a post and Subscribe2 sent out a seemingly endless string of duplicate emails. I myself got at least 200 I would estimate. I have deleted the plugin after downloading the subscribers to a CSV file. Never again. This is a show-stopping issue and I regret having to move on from Subscribe2.
-
This reply was modified 8 years, 10 months ago by
silverliebt.
