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 amcgregor
Recipients Dadeos, amcgregor, barry, cheryl.sabella, christian.heimes, dstufft, r.david.murray, tyrone-zhao
Date 2020-10-02.20:11:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1601669500.4.0.695038817911.issue36094@roundup.psfhosted.org>
In-reply-to
Content
Howdy!  One of my projects, Marrow Mailer (formerly TurboMail) has received a bit of a flood of reports and erroneous pull requests attempting to correct this bug in the invocation of smtplib by Mailer.

https://github.com/marrow/mailer/issues/83 is our own tracking issue, with https://github.com/marrow/mailer/pull/91 as the most "successful" pull request with more detailed (contextualized) traceback, comparison, and links to official documentation. (Also, yay, worked around the problem here by recovering my "native" issue tracker account rather than trying to sign in with GitHub.)

This appears to be a clear regression. The particular reason why I'm unwilling to accept these patches to Mailer is that passing a hostname at SMTP_SSL instantiation time will cause the connection to be initiated from within __init__ itself, prior to any ability to set the diagnostic logging level, which is boo, hiss. Initializers actually doing things is un-good, beyond diagnostic logging not being an optional keyword argument.  (Instantiation != procedural invocation.)
History
Date User Action Args
2020-10-02 20:11:40amcgregorsetrecipients: + amcgregor, barry, christian.heimes, r.david.murray, dstufft, cheryl.sabella, tyrone-zhao, Dadeos
2020-10-02 20:11:40amcgregorsetmessageid: <1601669500.4.0.695038817911.issue36094@roundup.psfhosted.org>
2020-10-02 20:11:40amcgregorlinkissue36094 messages
2020-10-02 20:11:40amcgregorcreate