Cron works ok, jobs ok, but no mail or SMS

[clarkac]

I have explained this problem in a different thread, but as I understand this better I think this is an installation problem so it's better to start a new topic.  This is because I hope the answer may help others if they run into this.
I have 3 sites that are in fact all subdomains of my main site, with Civi installed in each for different projects - 4.3.2 in each case.  In all of them cron runs ok and the jobs run ok.  The problem is that in only one site do mail & sms'es actually get sent.  To make the problem more exasperating, one site that I upgraded (yesterday) from 4.2.9 where mail/sms were working now doesn't work in 4.3.2     This  site has exactly the same cron userid/password/site key and mail and sms settings as before the upgrade.  The second site has a newly installed 4.3.1 upgraded to 4.3.2 and I have never managed to get mail & sms sent there, although cron and the jobs all run ok.  The third site works perfectly.

Ideas/comments please? - this is such a time waster!  The output from cron is as follows (but of course cron runs ok, and the jobs all list as running ok)
HTTP request sent, awaiting response... 200 OK
 Length: 0 [text/html]
 Saving to: `STDOUT'

      0K                                                        0.00 =0s

 2013-05-04 10:15:02 (0.00 B/s) - `-' saved [0/0]

[Donald Lobo]

Sorry about the time waster, but unfortunately there are lots of variations in systems / dbs / files etc and potentially a few lurking bugs too

As i've mentioned in some of my other replies, at this stage you (or someone else who knows php/mysql) will potentially need to go in and debug the two sites which are not sending mail/sms and figure out what is happening and why

lobo

[clarkac]

Thanks for the reply - can you give me a suggestion of where I should start debugging this?  Bearing in mind that all the variables in the application - like user/password/site key etc - are all the same, and yet in one instance work and in another fail?

[Donald Lobo]

You should skim the developer book: http://book.civicrm.org/developer/

for the cron/scheduled jobs, i'd start investigating at the api layer and go from there

In the past similar issues have been due to one of the following:

a. file permissioning issues
b. cms authentication
c. user permissioning for certain functionality

lobo

[kharding]

Thanks for the reply - can you give me a suggestion of where I should start debugging this?  Bearing in mind that all the variables in the application - like user/password/site key etc - are all the same, and yet in one instance work and in another fail?

Is the outgoing email account the same across all accounts?  Have you checked exim or mailserver logs to see what happens?
 
I recently had a server configuration issue where the mailserver was refusing to send emails because the VERP email address that CiviCRM used to send the outbound email was not a genuine email account; had to switch to mail() to send the emails.

That being said, my maillings were marked as "completed" but all attempted deliveries were "bounced."

[clarkac]

Thanks for the suggestion.  I already changed the email address, thinking that might be the cause, although in the upgrade from 4.2.9 to 4.3.2 the email address was the same.
What happens is that the mail and the SMS are left as 'running'.

[sibro]

I had the same problem,  finally found the solution. In the civi config file you need to comment out mail logging.