Author Topic: Civimail cronjob not processing messages (Read 12837 times)

CiviTeacher.com · January 18, 2011, 06:30:27 pm

I've got some news, mostly bad. I believe that the host in my situation is rejecting the VERP-formed email FROM address as an unwanted bulk message that violates their outgoing mail policy.

I found this out by looking in my CiviCRM.log file located in /sites/default/files/civicrm/templates_c/en_US/ConfigandLog/

There is a huge log file in there, which I cleared out and then ran some new tests.

@ChrisChinchilla, try finding your log file, clearing and reading the most recent entries as a result of some new tests.

This is what the log said:

Code: [Select]

                            [_arguments] => Array
                                (
                                    [0] => Verification failed for <b.177.61924.66b0473f8582cb5e@friendsoftheflathead.ca>
                                    [1] => Unrouteable address
                                    [2] => Sender verify failed
                                )

                            [_greeting] => ns1.otherdatanetworks.com ESMTP Exim 4.69 #1 Tue, 18 Jan 2011 19:09:13 -0700
We do not authorize the use of this system to transport unsolicited,
and/or bulk e-mail.
                            [_esmtp] => Array
                                (
                                    [ns1.otherdatanetworks.com] => Hello localhost [127.0.0.1]
                                    [SIZE] => 52428800
                                    [AUTH] => PLAIN LOGIN
                                    [HELP] => 
                                )

                        )

                    [type] => ->
                    [args] => Array
                        (
                            [0] => Invalid response code received from SMTP (outbound mail) server while attempting to send email.  This is often caused by a misconfiguration in the CiviCRM Outbound Email settings. Please verify the settings at Administer CiviCRM >> Global Settings >> Outbound Email (SMTP).

This is the message from the host.

Code: [Select]

                                            [_greeting] => ns1.otherdatanetworks.com ESMTP Exim 4.69 #1 Tue, 18 Jan 2011 19:09:13 -0700
We do not authorize the use of this system to transport unsolicited,
and/or bulk e-mail.

What I interpret from this is that the VERP b.177.61924.66b0473f8582cb5e@friendsoftheflathead.ca is an "unroutable address" and rejected according to their EXIM SMTP server.
Unfortunately with olderversions of CiviCRM I could turn off the VERP in Step 2 or Step 3 of the new mail process , and send emails without VERP. CiviCRM 3.3.2's options are less clear - and appears to disallow turning off VERP.
It should be noted that the outgoing settings for SMTP are correct and email is sent normally through other aspects of CiviCRM, but that's cause only CiviMail uses VERP, and VERP is causing the fail.

So, what can we do (besides find a new host)?

@Lobo, can we bring back the VERP options for CiviMail?

Donald Lobo · January 18, 2011, 07:59:02 pm

stoob:

i think later versions have allowed "more" options rather than less options. We've always used VERP and do feel that it is important for civimail. You'll need to convince your host to relax the rules and/or hack the code to not use VERP

lobo

CiviTeacher.com · January 18, 2011, 08:52:44 pm

Thanks, I agree the client chose a host that is not ideal. Wasn't my recommendation. I will recommend they move hosts.

However, regarding your thoughts about the number of options, unfortunately that's not true.

3.3 doesn't allow VERP to be turned off, whereas 3.1 did.

Personally I don't care, but some people might not be in a position of switching hosts, and wouldn't appreciate their VERP option being removed.

Here are some screenshots showing a 3.1 site I maintain.

xavier · January 18, 2011, 11:03:42 pm

Quote from: Stoob on January 18, 2011, 08:52:44 pm

3.3 doesn't allow VERP to be turned off, whereas 3.1 did.

That was a misnamed option, this VERP was only applied to the replies, not for the bounces. However, on 3.x, the sendmail outbound solution had a bug (in the pear library if I recall) so the bounce was never handled.

X+

ChrisChinchilla · January 19, 2011, 01:33:47 pm

All that's in my error log is this...

Jan 19 15:32:12 [info] civimail.cronjob.php

?? These are the worst kind of problems, ones that don't have any messages...

ChrisChinchilla · January 19, 2011, 02:23:33 pm

Also tried commenting out bootstrap lines as mentioned, adding admin user to admin group, even though it is the 0 user anyway and still nothing...

Every time I make a change, I recreate the mailing, still nothing happens...

At this moment I'm considering switching from Civi, which is a real shame, but we need to send our mailouts!

Donald Lobo · January 19, 2011, 02:50:40 pm

might want to get on IRC and ask folks if they can help. the last time someone had this issue (a few days ago), it was due to a redirect. So kinda hard to guess and figure things out.

If you are a developer, you can try seeing where the code exits/dies

lobo

CiviTeacher.com · January 19, 2011, 08:40:14 pm

chris, are you sure that was the error from the CiviCRM.log? That's all you got?

lobo also brings up a good point. check your .htaccess and httpd.conf files for weird mod_rewrites and 301 redirects on your domain.

ToddFur · January 24, 2011, 01:33:00 pm

I am having this problem too.....

Cron Daemon to me
show details 2:30 PM (0 minutes ago)
--2011-01-24 14:30:01-- http://xxx.xxx.xxx.xxx/drupal/sites/all/modules/civicrm/bin/civimail.cronjob.php
Connecting to xxx.xxx.xxx.xxx:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 0 [text/html]
Saving to: `civimail.cronjob.php'

0K 0.00 =0s

2011-01-24 14:30:02 (0.00 B/s) - `civimail.cronjob.php' saved [0/0]

Is this a bug or did I enter in the wrong cron job command? I have it set for:

/usr/bin/wget --post-data='name=XXXXXX&pass=XXXXXX&key=XXXXXXXXXXXX' http://xxx.xxx.xxx.xxx/drupal/sites/all/modules/civicrm/bin/civimail.cronjob.php

CiviTeacher.com · January 27, 2011, 07:03:55 pm

I'm not sure why you have the "/drupal" in your path. Maybe you installed drupal in a sub-directory? If so that is ok, I just wanted to double check.

Try running the .php file from a browser like so:

Code: [Select]

http://xxx.xxx.xxx.xxx/drupal/sites/all/modules/civicrm/bin/civimail.cronjob.php?name=XXXXXX&pass=XXXXXX&key=XXXXXXXXXXXX

Did that do anything?

If so, then you know the problem is your cronjob.

Now to debug the cronjob. Maybe you don't need "/usr/bin/wget" maybe just "wget" is ok.

Maybe you need to add some arguments like -O and > /dev/null and all that stuff.

I suggest writing a simple PHP script (not in civicrm or anything, just regular PHP) using the PHP mail() function and using a cronjob to run it. Have the script send you an email once a minute, or do something really obvious where you know if it's working or not. This will help you determine if you cronjob syntax is incorrect.

xavier · January 27, 2011, 10:19:37 pm

if you have php cli, please try to use it instead of wget as described in the book

X+

ChrisChinchilla · February 01, 2011, 11:31:52 pm

Took a look in my .htaccess, nothing unusual in there, can't find any other conf files really... I might contact my hosts, see if they changed anything recently...

ChrisChinchilla · February 02, 2011, 02:26:44 am

I've been doing some digging about in code and have sort of tracked down what, IMHO, might be the problem...

I looked into the file that is run by cron and found...

   CRM_Mailing_BAO_Job::runJobs_pre($batch_size);
   CRM_Mailing_BAO_Job::runJobs();
   CRM_Mailing_BAO_Job::runJobs_post();

So, then I delved into the functions called by these lines, pretty much wherever I debug the code to find the vale of $job, which I assume is what is being generated by the functions, it is empty, even though there are definitely jobs to be processed.

Having no insight into the greater workings of Civi, I wonder of the problems might be :

Time zone issues?
The db upgrade when I upgraded to 3.2/3.3 didn't work properly and thus no jobs are being returned...

xavier · February 02, 2011, 03:08:39 am

Could you update your profile on the forum and say what version you are using ?

Remember a bug like that on 3.2.x (or was it a beta) ? Been fixed on the latest version I think

X+

ChrisChinchilla · February 02, 2011, 03:21:47 am

I'm using 3.3.2

I've tracked down the problem, on line 581 of /civicrm/CRM/Mailing/BAO/job.php

if i comment out these lines...

if ( $mailingJob->find( true ) ) {
// mailing have been canceled at run time.
if ( $mailingJob->status == 'Canceled' ) {
return false;
}
} else {
// mailing have been deleted at run time.
return false;
}

it works... ??

CiviCRM Community Forums (archive)

News:

Author Topic: Civimail cronjob not processing messages (Read 12837 times)

CiviTeacher.com

Re: Civimail cronjob not processing messages

Donald Lobo

Re: Civimail cronjob not processing messages

CiviTeacher.com

Re: Civimail cronjob not processing messages

xavier

Re: Civimail cronjob not processing messages

ChrisChinchilla

Re: Civimail cronjob not processing messages

ChrisChinchilla

Re: Civimail cronjob not processing messages

Donald Lobo

Re: Civimail cronjob not processing messages

CiviTeacher.com

Re: Civimail cronjob not processing messages

ToddFur

Re: Civimail cronjob not processing messages

CiviTeacher.com

Re: Civimail cronjob not processing messages

xavier

Re: Civimail cronjob not processing messages

ChrisChinchilla

Re: Civimail cronjob not processing messages

ChrisChinchilla

Re: Civimail cronjob not processing messages

xavier

Re: Civimail cronjob not processing messages

ChrisChinchilla

Re: Civimail cronjob not processing messages