This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author David Ford (FirefighterBlu3)
Recipients David Ford (FirefighterBlu3), barry, r.david.murray
Date 2018-06-05.05:02:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1528174935.81.0.592728768989.issue29539@psf.upfronthosting.co.za>
In-reply-to
Content
Yes, it is distinctly intended to collect the results for every recipient as in modern MTAs, there's more than just success/fail results. This is to collect data such as queue ID and the MTA's programmatic response for each individual recipient. I have several needs of knowing if the message was immediately relayed, queued for later because of a remote issue, queued because of MTA issue, graylisted or blocked because of milter reasons, or ... any of a list of failure reasons.

This data can be collected if there is only one recipient per message, but that is considerably resource expensive.

Without this patch, when sending to say 100 recipients, the only response returned to the caller is the very last (100th) result. A 250 then assumes that all 100 were transmitted successfully when in truth, the first 99 could have failed.

Yes, I'll make a PR, do the CLA, and add some tests.
History
Date User Action Args
2018-06-05 05:02:15David Ford (FirefighterBlu3)setrecipients: + David Ford (FirefighterBlu3), barry, r.david.murray
2018-06-05 05:02:15David Ford (FirefighterBlu3)setmessageid: <1528174935.81.0.592728768989.issue29539@psf.upfronthosting.co.za>
2018-06-05 05:02:15David Ford (FirefighterBlu3)linkissue29539 messages
2018-06-05 05:02:15David Ford (FirefighterBlu3)create