Mail delivery fails due to SMTPRecipientsRefused exception, then retries forever.

[lmacken@…]

We are currently using TurboMail to send out tons of mail every day for some pieces of infrastructure for the Fedora Project (https://hosted.fedoraproject.org/projects/bodhi). I have noticed recently that TurboMail will suddenly stop dispatching, and will stop sending mails. The messages get enqueued, because I have debugging messages after it that do get printed out..

Is there any way to prevent/debug this issue better?

[fs]

I think this happens if an exception is thrown inside of TurboMail. After that I suspect that the worker thread hangs and no mail is sent anymore. I recommend that you use my patches (#11-#20 in this trac). I suspect that especially the patch in #17 may help you.

[lmacken@…]

The patch from Ticket #17 help bring the error to the surface:

SMTPRecipientsRefused: {u'bodhi': (550, '5.1.1 <bodhi>... User unknown')}

..but it then proceeded to infinitely attempt to enqueue this email. I think it may be much more valuable if this patch was re-worked to simply output the error, and move on.

[fs]

I think TurboMail should do much more in regards of error handling. I mailed some proposals to Matt but got no answer so far. I definitely do not want that a single failure will cause a mail to be silently dropped but I agree that there should be a point where we just have to drop mails. I'm currently on a paid project where I definitely need a more robust error handling so I'm willing to spend some time on that issue in the next months.

If someone is interested in joining the party, please send a mail to felix dot schwarz (at) schwarz dot eu.

[amcgregor]

For slightly more robust debugging, please see ticket #17 and change set r28.

[amcgregor]

I've added a specific exception handler to deal with this error. Messages that fail with this exception are logged then removed from the queue, as of r34.