CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site

This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviMail (Moderator: Piotr Szotkowski) »
  • Processing Premature Bounces
Pages: [1]

Author Topic: Processing Premature Bounces  (Read 1007 times)

Denver Dave

  • Ask me questions
  • ****
  • Posts: 471
  • Karma: 9
Processing Premature Bounces
January 12, 2009, 11:54:55 am
Processing Premature Bounces

It looks like this issue, discussed at http://forum.civicrm.org/index.php/topic,5245.0.html may not go away soon and it looks like other CiviCRM installations may have the same issue.

Basically, some emails are bounced without even being sent.  When this happens, usually, but maybe not always, an email has a "Connection Refused" error and then that email and every other remaining email in the batch gets bounced.  Previous and later batches are fine, unless a similar error occurs.  This has been happening for us for the last 6 months, although we didn't realize it at first.  We have a procedure to resend the bounces discussed in the link above, but there might be a better way.

Since we are controlling the sending, there must be a routine that loops through each email in the batch and sends out the email.  When a problem happens, then all later emails in the batch are also bounced.  Can someone tell me where this routine is?   Perhaps the routine could be modified so that when a connection refused message happens, that the routine tries again before giving up on that email and the rest of the batch.  Perhaps since the error does not happen very often, if we tried 2 or 3 times before giving up, all the emails would go out and eliminate us having to process emails 2 or 3 times to get all the emails out. 

What do you think?  Possibility?
« Last Edit: January 13, 2009, 11:46:45 am by Denver Dave »

Piotr Szotkowski

  • Moderator
  • I live on this forum
  • *****
  • Posts: 1497
  • Karma: 57
Re: Processing Premature Bounces
January 13, 2009, 02:28:15 am
Quote from: Denver Dave on January 12, 2009, 11:54:55 am
Basically, some emails are bounced without even being sent.  When this happens, usually, but maybe not always, an email has a "Connection Refused" error and then that email and every other remaining email in the batch gets bounced.

As we discussed before, if the connection refused is generated on *your* end (i.e., by the server that sends the emails, rather than the recipient’s server), then it’s quite logical that further emails from this batch won’t be accepted either.

Did you try to confirm that it’s not your server that refuses the connection?

Quote
Since we are controlling the sending, there must be a routine that loops through each email in the batch and sends out the email.  When a problem happens, then all later emails in the batch are also bounced.  Can someone tell me where this routine is?

The call trace goes like this: bin/civimail.cronjob.php → CRM_Mailing_BAO_Job::runJobs() → CRM_Mailing_BAO_Job::deliver() → CRM_Mailing_BAO_Job::deliverGroup()
If you found the above helpful, please consider helping us in return – you can even steer CiviCRM’s future and help us extend CiviCRM in ways useful to you.

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviMail (Moderator: Piotr Szotkowski) »
  • Processing Premature Bounces

This forum was archived on 2017-11-26.