sls added the comment:
I opened a new PR.
I picked up some of FirefighterBlu3's suggestions and added some unittests and
refactoring to assist. Hope this helps.
--
___
Python tracker
<https://bugs.python.org/issue29
Change by sls :
--
keywords: +patch
pull_requests: +12148
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue29539>
___
___
Python-
sls added the comment:
I closed my PR. I'd just rename "senderrs" to "mta_status" or so as
aforementioned change means not just storing errors.
FirefighterBlu3, do you open a PR for this? I'd like to see this moving into
3.8 as we don't compile Python from source b
sls added the comment:
Did you make a PR ? I didn't notice this issue and did a quick fix:
https://github.com/python/cpython/pull/12104
I was hoping this or similar fixes would be implemented in 3.7.x
Anyways. I'd suggest to return both success and errors for each recipient.
sendmail
Change by sls :
--
keywords: +patch
pull_requests: +12111
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue36148>
___
___
Python-
New submission from sls :
MTA status codes (visible via setdebuglevel(1)) are not accessible as the
`sendmail`-method stores them only locally (code, resp).
I suggest to store the mta status codes, for instance: "250, b'2.0.0 Ok: queued
as XYZ" etc. in an instance attribute (tuple)
