CiviCRM Community Forums (archive)

Hi,
I have installed and configured CiviCRM 3.3 Beta 1.
I done all tests using a group with 3 recipients (one is faked to perform tests), and CiviMail worked properly.

When I send mass mailing at 4100 recipients, Cronjob send only at first 190-210 recipients in Group and CiviMail Report Interface showa always Running Status.

The scheduling is not closed, cronjob process don't send email anymore.  All stay in pending!

I can track opens, bounces and click-troughts.. I can't track replies and forward.

I tried to set Mail Spool but I have the same problem.

I can send 10.000 email for a day using my SMTP Server on Webfaction.com

I used with successful CiviMail in CiviCRM 3.1.4

Can you help me?

jscm
Milan (Italy)

Hi,
Running Cron Manually I've got an error message.

Fatal error: Maximum execution time of 30 seconds exceeded in ~/101112_crm/sites/all/modules/civicrm/packages/Mail/RFC822.php on line 428

it sent at 198 recipients.
Status stay Running.

Hey jscm,

what's your mailer configuration settings?

3.3 uses divides the mailing into multiple jobs and each cron run it sends a limited amount of mails.

it Seems like that after the first CronJob, that not complete the Mass Mailing Run, the next Cronjobs don't find any Mass Mailing Process to Complete.

Ok!.. I will try.
Maybe I don't understand english but if I send email at my server  (at mailbox sender) I can send only one email.
Can you explain?
I read... and I understand now!

Someone have good news for me?

Similar problem here with 3.3.1 but in our case we are not hitting max_execution_time. This is on a site that has recently been upgraded from 3.2.3 to 3.3.1 . In 3.2.3, mailings were working correctly. Since the upgrade, mailings get stuck at 200 recipients. Visiting /civicrm/mailing/queue?reset=1 as uid 1 does not solve the problem, the mailings are still stuck. Mailer Batch Limit was set to 200. I tried changing this to 0 but this did not help. Mailer Job Size was empty, I tried setting this to 0 but this made no difference.

mysql> select * from civicrm_mailing_job j where j.is_test = 0 and ( j.status = 'Running' and j.end_date IS null );
+-----+------------+---------------------+---------------------+----------+---------+---------+----------+-----------+------------+-----------+
| id  | mailing_id | scheduled_date      | start_date          | end_date | status  | is_test | job_type | parent_id | job_offset | job_limit |
+-----+------------+---------------------+---------------------+----------+---------+---------+----------+-----------+------------+-----------+
| 712 |        332 | 2010-12-10 09:34:59 | 2010-12-10 09:39:04 | NULL     | Running |       0 | NULL     |      NULL |          0 |         0 |
| 713 |        332 | 2010-12-10 09:34:59 | 2010-12-10 09:39:04 | NULL     | Running |       0 | child    |       712 |          0 |       220 |
| 719 |        334 | 2010-12-10 11:47:55 | 2010-12-10 11:52:02 | NULL     | Running |       0 | NULL     |      NULL |          0 |         0 |
| 720 |        334 | 2010-12-10 11:47:55 | 2010-12-10 11:52:02 | NULL     | Running |       0 | child    |       719 |          0 |       326 |
+-----+------------+---------------------+---------------------+----------+---------+---------+----------+-----------+------------+-----------+

Is there anything extra that needs to be done to get mailings working after upgrading to 3.3? The client is getting annoyed that every time we upgrade their Civi, mailings break. (Happened going from 3.1 to 3.2 due to changes in permissions required for the cron job user, e.g. needing "view all contacts".)

Edit: have had a look at CRM/Mailing/BAO/Job.php in 3.3.1 and I don't understand how it's intended to deal with part-finished child jobs. The deficiency here may well be in my understanding rather than the code, but AFAICS:

runJobs_pre():
- select Scheduled parent jobs;
- for each, create 1 or more Scheduled child jobs and set parent to Running.

runJobs():
- select first Scheduled child job;
- if status isn't Running (we already know it isn't because we selected only Scheduled) then queue job, set start time and change to Running;
- deliver job;
- if delivery completed, mark job Complete.

runJobs_post():
- select Running parent jobs;
- for each, if there are no incomplete child jobs then mark parent job complete.

deliver():
- iterates through recipients & sends mails, returning false if it hits $config->mailerBatchLimit before completing the job.

So what is supposed to happen if a child job hits $config->mailerBatchLimit before completion? I can't find code in CRM/Mailing/BAO/Job.php that deals with this case, AFAICS they get left in limbo and that fits with what is happening on the site in question.

Thanks in advance for any advice,

Dave

can u'll apply the following patch:

svn diff CRM/Mailing/BAO/Job.php
Index: CRM/Mailing/BAO/Job.php
===================================================================
--- CRM/Mailing/BAO/Job.php     (revision 31195)
+++ CRM/Mailing/BAO/Job.php     (working copy)
@@ -87,7 +87,8 @@
                           AND   j.is_test = 0
                           AND   ( ( j.start_date IS null
                           AND       j.scheduled_date <= $currentTime
-                          AND       j.status = 'Scheduled'
+                          AND       j.status = 'Scheduled' )
+                OR     ( j.status = 'Running'
                           AND       j.end_date IS null ) )
                           AND (j.job_type = 'child')
                           AND   {$mailingACL}

thanx

lobo