Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.2.7

Bug #147 sendMailsInQueue() questionable failure handling....
Submitted: 2003-10-23 17:13 UTC
From: gabe at websaviour dot com Assigned: quipo
Status: Closed Package: Mail_Queue
PHP Version: Irrelevant OS:
Roadmaps: (Not assigned)    
Subscription  
Comments Add Comment Add patch


Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know! Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem : 28 - 8 = ?

 
 [2003-10-23 17:13 UTC] gabe at websaviour dot com
Description: ------------ If send_mail returns an error then sendMailsInQueue() aborts immediately. While this is presumably meant to handle fatal send mail errors related to misconfiguration, it should be noted that errors can be generated as a result of the contents of the mail itself. In my case one of the email addresses I was sending to had a bad domain name in it. In that case I still want to continue sending subsequent mails without having to go into the container and manually delete the bad entry.

Comments

 [2004-01-09 15:57 UTC] quipo
CVS version should be a step forward to a better error handling, but it's far from being perfect. At least, now the function doesn't die anymore on single failure in a queue of mails...
 [2004-07-11 22:35 UTC] gurugeek
Dear Maintainer, Your package mail_queue has currently 2 open bugs. We urge you to take the necessary steps to solve the reported issues at your soonest convenience. If the bug issue hasn’t been addressed yet you are kindly asked to take the necessary steps to ensure a prompt resolution of the problem. If you already addressed the reported problem feel free to change the bug status as soon as possible. Regards David Costa PEAR Quality Assurance pear-qa@lists.php.net
 [2004-07-12 13:52 UTC] quipo
I guess this bug can be closed. The error handling is not perfect but it's already better and more usable than before. If someone finds the time to propose a patch with an even better solution, he's welcome.