Hi @davidschwartzer,
Check with your hosting server, if they have an error log, it will give more explanation of why it’s not working.
Check this with your hosting provider, they have access to your server logs and will be able to tell you where and why emails are being blocked.
Without fail it is always down to a server-side limitation or restriction.
These restrictions broadly fall into one of three areas. These are the sender details, the header details, and restrictions on the number of messages sent.
Sender Details. You may need to ensure that the email notification is being sent from an email address on the same domain as your blog. So, if your blog is https://www.example.com the email should be something like [email protected]. To do this go to Subscribe2->Settings and carefully select from the dropdown list where it says “Send Email From”. Here you will see “Post Author”, then the name of your blog, and then the names of your administrator-level users. It may be wise to set up a dummy user account specifically to send the emails from and make sure you give that account an on-domain email address.
Header Details. 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.
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 messages as described above. A site like this with many public and registered subscribers could conceivably generate a lot of email for your own inbox.
Restrictions on the number of messages sent. In order to combat spam, many hosts are now implementing time-based limitations. This means you are only allowed to send a certain number of messages per unit time, 500 per hour for example. Subscribe2 does not have a workaround for this inbuilt but see the next question.
Thanks