CiviCRM Community Forums (archive)

Here is a list of my woes with CiviMail and what I've tried. (version 3.4.5)

Every mailing needs cron too jumpstart it from Scheduled to Running:

https://www.example.org.nz/sites/all/modules/civicrm/bin/civimail.cronjob.php?name=username&pass=password&key=sitekey

This starts the mailing and is successful for mailings to under 1000 people (we think - reporting for open rates looks normal).

Both mailings we've tried over 1000 recipients gets stuck at 1000. Any further jabbing of the cron run above caused another email to send.

Now I can't tell who has had the latest email, as I had to cancel it to stop the multiples sending (or so I thought at the time) and the civicrm_mailing tables in phpmyadmin show 1489 recipients (the total of the mailing).

I have tried the debugging but nothing seems to write to the log file:
http://wiki.civicrm.org/confluence/display/CRMDOC32/Debugging

I'm OK with having to run cron to make it go as it seems I probably haven't set up the crontab properly. But the problem with getting stuck at 1000 is serious and the organisation is angry.

What is causing this?


EDITED: We eventually solved this by moving from shared hosting to VPS. The shared hosting was timing out at 300 seconds, which wasn't enough time to either send the mailing or record who had received it.

Now the mailing to 1200 people goes out in a minute, which is great.

Moral of the story: don't install CiviCRM on shared hosting. (It wasn't my decision to do that, by the way!)

Check our CiviMail Mailer settings--you may have it set to send only 1000 per run. Also perhaps confirm manually that none of the emails are duplicates--could be that duplication is in the DB, not in CiviMail...

Mailer batch limit is set to 0.

There are no duplicate emails in the system.

Thanks for the patch, I'll try that.