Author Topic: Researching intermittent failed mailings (Read 1976 times)

Dennis Gray · July 05, 2011, 04:21:37 pm

For several months now we are having intermittent problems with civimail. In most cases, there is no problem but we have intermittent cases of mailings sent with 100% bounce rate. I have run a tcpdump script to monitor the traffic for over a week and can see no failures on connecting to civismtp during that period. I'm wondering if it would be worth while to analyze the soap messages but haven't figured out a way to capture them. Can someone be of any help?

(our production server is running CiviCRM 1.9. We are in the process up upgrading but it will be awhile yet)

shane · July 06, 2011, 06:38:57 am

Hi!

this happens because your server gets disconnected from our server and CiviCRM treats all attempted mailings as "bounced" after a disconnect. CiviCRM does not retry mailings.

hope this helps,

-Shane

Dennis Gray · July 06, 2011, 02:37:31 pm

We apparently are not getting disconnected when connect to your SMTP port but I think perhaps something is going wrong during the interchange of SOAP messages. That is what I'm trying to figure out how to monitor. It would be helpful to have a diagram of some sort those shows just how the interchange takes place.

Dennis Gray · July 06, 2011, 04:24:53 pm

Here is the tcpdump script that I am using. I have sent a test CiviMail message with some links.

tcpdump -n -p -s 1600 -i any -w civismtp-soap-test.cap "(src net 67.212.170.0/24 and dst port 443) or (src port 443 and dst net 67.212.170.0/24)"

When I start the tcpdump, I can see traffic if I reply to the CiviMail. I then try again and only try clicking through. I do not see any traffic, although the CiviMail report is incrementing the click through counter every time I click through.

shane · July 10, 2011, 08:51:20 pm

Hi.

A 100% bounce rate would not go through SOAP and would not be due to SOAP problems.

If this happens again, please notify us and we will check the bounce for any connection problems.

thx!

Dennis Gray · July 11, 2011, 03:48:31 pm

You mentioned to one of our other members in reply to her email that it was because our production release, 1.9, is single-threaded. Would this cause disconnects?

I'd still like to know how to monitor soap messages.

Thanks

shane · July 11, 2011, 08:43:24 pm

single-threaded comment was made in response to slow mailings question. 100% bounce is a different issue and is not caused by single-threaded version of civimail.

you can add some sort of logging into the soap.php file and dump the relevant request data into some file.

Dennis Gray · July 12, 2011, 04:06:38 pm

Thanks, Shane

I agree there are two issues but non-technical people perceive things as just a problem. We have some pretty large mailings done by several large committees and I can see how the single-threaded mode is causing things to be "slow" but we have to live with that until we upgrade. Our most serious problem is the 100% bounce issue.

You have said that it is probably not cause by soap issues so we would like to put some logging in somewhere to see where the failure might be. Using tcpdump is like finding a needle in a haystack. Can you (or anyone else) suggest where we might put the logging?

I will not be doing this myself but acting as an intermediary until we get a resource with more PHP skills than me.

Cheers

shane · July 21, 2011, 07:46:42 am

find the SoapServer.php file which is under <path_to_civicrm>/CRM/Utils/SoapServer.php

in that file edit the mailer_event_bounce function and add something like the following:

file_put_contents("/tmp/soap_debug_log", print_r(array($job, $queue, $hash),1), FILE_APPEND);

this is just an example of what you can log and depends on available params in mailer_event_bounce function in your version of civicrm.
this line of code will get hit whenever we send a bounce from civismtp.

NOTE: we don't guarantee any results nor are responsible for any problems that this may cause.

i would only put this in when you're debugging the problem and remember to comment it out for regular use.

thanks,

-Leyla
CiviSMTP Support

Dennis Gray · July 22, 2011, 05:05:13 pm

This is helpful and gives me a starting point but the real problem is when we get the internal bounces when there is a disconnect. I haven't found the part of the code that does that.

CiviCRM Community Forums (archive)

News:

Author Topic: Researching intermittent failed mailings (Read 1976 times)

Dennis Gray

Researching intermittent failed mailings

shane

Re: Researching intermittent failed mailings

Dennis Gray

Re: Researching intermittent failed mailings

Dennis Gray

Re: Researching intermittent failed mailings

shane

Re: Researching intermittent failed mailings

Dennis Gray

Re: Researching intermittent failed mailings

shane

Re: Researching intermittent failed mailings

Dennis Gray

Re: Researching intermittent failed mailings

shane

Re: Researching intermittent failed mailings

Dennis Gray

Re: Researching intermittent failed mailings