Message246419
| Author |
barry |
| Recipients |
barry, catalin.iacob, jesstess, python-dev, r.david.murray, sandro.tosi, zvyn |
| Date |
2015年07月07日.15:30:33 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1436283034.34.0.333471965021.issue15014@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
I have a patch to support initial-response, which I'll be posting here after a bit of clean up and a full (local) test run, with documentation. I ended up adding a keyword argument `initial_response_ok=True` to .login() and .auth(). The reason for this is that some clients may wish to force smtplib to do challenge/response.
By default, mechanisms that support it (e.g. AUTH PLAIN) will send the initial response. Setting `initial_response_ok=False` in either SMTP.auth() or SMTP.login() will prevent smtplib from sending the initial response, and instead deal with challenge/response.
I made initial_response_ok a keyword argument. |
|