Simplenews for Drupal 5
| Project: | Simplenews |
| Version: | 5.x-1.5 |
| Component: | Usability |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
We are using the Simplenews module to send out 2 different newsletters per month with about 1800 subscribers per issue (1st and 15th of the month). Up until our October 1st issue, we did not have any problems (that we were aware of). Now it is showing that the newsletter that was to have been sent is still currently being sent by cron run 13 days after it was sent.
I have been chatting with the hosting company to see if it was an account mail limit issue. This is potentially part of issue. The
limit is 1500 per hour.
I would like to know a few things:
- in the installation documentation for Simplenews, it says that when I send by cron, the "initial send time" needs to be set to zero. When I took over the site, the setting was 100 seconds and the "cron throttle" was set to 300. The cron run in my siteadmin looks to be currently set to run every hour on the 15 minute mark.
If I change the simplenews "initial send time" setting to zero, will Simplenews send 300 emails every hour according to the cron? And do I understand this correctly that the way it was set up before, it would send up until the 100 seconds expired then not send anymore?
- the hosting company cleared the queue of emails that had not been sent from the newsletter from the beginning of the month. On my
newsletters page, the Oct. 1st newsletter is still listed as being sent by cron. Do I have to delete this newsletter in order to send
the next one?
Can anyone help?
Thank you.
Andrew
#1
#2
Drew,
I am trying to help support Simplenews, but it is beyond my ability to work with the D5 version (I am now learning the Simplenews D6 version). I am not familiar with the "initial send time" setting, as that has been eliminated from D6 version. Have you considered upgrading to D6? If you did, you would probably not be having these issues.
Thanks,
captaindav
http://drupalanswer.com
#3
We will likely be upgrading over the next 6 months but I would really like to know why this is happening now. There have been no issues up until this point. In the installation notes for Simplenews v.5, it says that if you are using a cron, then the "initial send time" should be set to zero. Which I did. I sent a new newletter to see if the issue was resolved but it is not. Assuming the cron is set up right (it has not been changed), what would cause this to malfunction now??
Drew
#4
Drew,
I am sorry I am unable to support D5 Simplenews. Perhaps someone else, who is familiar with D5 Simplenews, will suggest some potential causes of this issue.
The only other option I could see is to create a test environment for your website, so you could try changing various settings, and then doing test sends to a dummy email server that does not actually send out the emails. But this is probably as much work as upgrading! This was my concern initially, that you could spend as much time fixing the problem in D5 as it would take to upgrade to D6.
Thanks,
captaindav
http://drupalanswer.com
#5
Thanks anyway, captaindav. I have a few other ideas. And if there's anyone out there that has any other ideas, I'm listening.
Drew
#6
To get back to a good starting point:
* In the table simplenews_newsletters set the s_status of all records to '2'.
* In the table simplenews_subscriptions set the s_status of all records to '0'.