-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jason R. Mastaler wrote: > Stephen Warren <[EMAIL PROTECTED]> writes: > >>> Bugfix in SMTP mode that allows TLS and SMTP AUTH to be used together. TLS >>> has >>> to come first, before AUTH, or else you'd get this kind of error: >>> >>> smtplib.SMTPException: SMTP AUTH extension not supported by server. >> Which SMTP server is this with? >> >> According to the RFC, as soon as STARTTLS is issued (and accepted), the >> server MUST forget/reset all knowledge of the client - HELO hostname >> parameter, AUTH status, etc. >> >> This implies to me that any reasonable server would allow the client to >> send AUTH, STARTTLS, AUTH again, since the STARTTLS would un-AUTH the >> client, so the signon sent by the server after STARTTLS should offer AUTH. > > It's with Postfix.
Hmm. How bizarre! > I see what you're saying, but for some reason before this change TLS > and AUTH wouldn't work together, and now they do. For the purposes of > TMDA, I don't see any problems with reversing their order in SMTP.py > like I did, do you? The change to TMDA is the right thing to do either way. I was just surprised that you'd found an SMTP server that had an issue with the original code. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF50K1hk3bo0lNTrURAmzZAJ9quZG3dDYotAmvLHGPgjWTuekAhACg/ovd 8I84PT32TGuh6DTJD20A2s4= =aiCn -----END PGP SIGNATURE----- _________________________________________________ tmda-workers mailing list ([email protected]) http://tmda.net/lists/listinfo/tmda-workers
