Author barry
Recipients barry, catalin.iacob, jesstess, python-dev, r.david.murray, sandro.tosi, zvyn
Date 2015-06-22.20:39:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1435005578.23.0.281667811094.issue15014@psf.upfronthosting.co.za>
In-reply-to
Content
I believe this change broke RFC 4954's AUTH command when the optional initial-response is expected.  $4 "The AUTH Command" says:

AUTH mechanism [initial-response]
   ...
   initial-response: An optional initial client response.  If present,
   this response MUST be encoded as described in Section 4 of [BASE64]
   or contain a single character "="

It's possible that some SMTP servers only look for a string like

   AUTH PLAIN <base64-gobbledygook>

and won't issue a challenge if it's missing.  Such an example is found in the lazr.smtptest and used by the testing SMTPd in GNU Mailman.  It's possible that the servers are not standards compliant (I haven't completely groked RFC 4422), but still, since this is a backward incompatible change and breaks existing code, there should be some way of making smtplib.login() provide the initial-response, and it probably ought to be the default for backward compatibility.
History
Date User Action Args
2015-06-22 20:39:38barrysetrecipients: + barry, r.david.murray, jesstess, sandro.tosi, catalin.iacob, python-dev, zvyn
2015-06-22 20:39:38barrysetmessageid: <1435005578.23.0.281667811094.issue15014@psf.upfronthosting.co.za>
2015-06-22 20:39:38barrylinkissue15014 messages
2015-06-22 20:39:38barrycreate