Author Topic: Failed to set sender (Read 492 times)

copeasetic · May 29, 2014, 03:31:34 pm

Hi there,

I am running into an issue where mailings will get "stuck" until I kill the running process then wait for Cron to fire the mailing again (every 15 minutes).

The emails that are caught in this are thrown as bounces - which it not accurate as they were not actually sent.

The error coming back is "[SMTP: Invalid response code received from SMTP server while sending email. This is often caused by a misconfiguration in the Outbound Email Settings. (code: -1, response: )]

Once I kill the process and cron fires again the mailing continues for about 10 minutes then locks up again.

The mail servers I am hitting are enterprise servers and they are not reporting any issues on their end. My Civi instance just seems to disapear until the mailing is restarted at the next cron.

Please note: My instance is installed on a dedicated machine with 8 core XEON with 16GB RAM on a 100Mb pipe running CentOS Linux 6.x (not certain this info is needed, but thought I would offer it anyway)

Drupal 7.28
Civi 4.4.5

I am happy to provide any data requested as I have root access to the machine.

Thanks in advance!

Jamie

Donald Lobo · May 29, 2014, 04:09:33 pm

can u try this patch

Code: [Select]

index fab73ea..5644beb 100644
--- a/CRM/Mailing/BAO/MailingJob.php
+++ b/CRM/Mailing/BAO/MailingJob.php
@@ -660,12 +660,13 @@ VALUES (%1, %2, %3, %4, %5, %6, %7)
       if (is_a($result, 'PEAR_Error') && !$mailing->sms_provider_id) {
         // CRM-9191
         $message = $result->getMessage();
-        if (strpos($message,
-            'Failed to write to socket'
-          ) !== FALSE) {
+        if (
+          strpos($message, 'Failed to write to socket') !== FALSE ||
+          strpos($message, 'Failed to set sender') !== FALSE
+        ) {
           // lets log this message and code
           $code = $result->getCode();
-          CRM_Core_Error::debug_log_message("SMTP Socket Error. Message: $message, Code: $code");
+          CRM_Core_Error::debug_log_message("SMTP Socket Error or failed to set sender error. Message: $message, Code: $code");
 
           // these are socket write errors which most likely means smtp connection errors
           // lets skip them

lobo

Chris Burgess · May 29, 2014, 04:12:46 pm

Not recently, but on previous CiviCRM's I saw this happen when it "choked" on an invalid email address that had sneaked past CiviCRM. CiviCRM would find it was unable to deliver that message, and rather than moving on to the next one would simply lock up.

IDK if that bug was fixed, but the first place I'd check would be for email addresses which don't seem right.

- Your mail server logs may hold a clue - look for errors which happen when CiviCRM chokes.
- The CiviCRM logfile (path varies) may show some output or a backtrace allowing you to identify the email in question.
- Enabling SMTP on your webserver and configuring it to pass messages to the mailservers might make the error message more visible (but you need to be OK with handling SMTP on the webserver, and happy configuring a mailserver, to take this route).

EDIT: That earlier issue I recalled - from 2.0 days! - was discussed in http://forum.civicrm.org/index.php/topic,3268.msg14384.html and apparently fixed in https://issues.civicrm.org/jira/browse/CRM-3108

CiviCRM Community Forums (archive)

News:

Author Topic: Failed to set sender (Read 492 times)

copeasetic

Failed to set sender

Donald Lobo

Re: Failed to set sender

Chris Burgess

Re: Failed to set sender