CiviCRM Community Forums (archive)

The problem:

CiviMail's current behavior seems to be, when it encounters a problem with the SMTP connection in the middle of sending out a mailing, it gives up completely on the remaining messages in the queue, marks them all as "bounced" and puts the corresponding email addresses on hold.

One possible solution:

Make CiviMail a little more persistent. When it encounters an interruption, it should pause until the next cron run, then try to start up at the same place in the queue. It's very possible that the issue will have corrected itself by then.

Another problem:

It is extremely hard to figure out what went wrong when (part of) a mailing fails to send. Thus we get things like:

• Topic: "Unknown bounce type: Could not parse bounce email" http://forum.civicrm.org/index.php/topic,10148.0.html
• Topic: Intermittent SMTP error http://forum.civicrm.org/index.php/topic,19002.0.html

Another possible solution:

Figure out a way for CiviMail to be more informative in these cases. What was the exact SMTP error? Was it a "returned email" bounce or a lost connection?

... What do you all think, should I post this as a feature request ticket?