You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee=Noneclosed_at=Nonecreated_at=<Date2014-01-22.18:17:39.924>labels= ['easy', 'type-feature', 'library', 'expert-email']
title='Add support for AUTH command to poplib'updated_at=<Date2014-01-23.13:55:51.385>user='https://bugs.python.org/dveeden'
I use 'AUTH PLAIN <secret>' to login to a POP3 server with a proxy user. I can't use 'pass_()' as I need to supply a admin user and the user to proxy into.
This is basically rfc 5034 support? Sounds like a good idea.
I'm going to mark this issue as 'easy' because it isn't a whole lot of code, but for anyone who wants to tackle it, know that understanding the RFC and getting it *right* is not necessarily trivial, because: rfc :)
A client should send CAPA and check if there is a SASL tag in the response (e.g. "SASL PLAIN").
===============================
+OK Dovecot ready.
AUTH PLAIN base64_encoded_info
+OK Logged in.
LIST
===============================
I've replace the base64 encoded authentication info with 'base64_encoded_info'
For other authentication mechanisms the response can be longer (it may contain a challenge) and the request may only contain the mechanim.
I don't have a server which supports anything else than AUTH PLAIN, so I could verify/test this.
imaplib has an API for handling that kind of thing. Maybe we can model the poplib support off of that API. It would be nice to be consistent, assuming it in fact makes sense for poplib as well.
Activity
dveeden commentedon Jan 22, 2014
I use 'AUTH PLAIN <secret>' to login to a POP3 server with a proxy user. I can't use 'pass_()' as I need to supply a admin user and the user to proxy into.
bitdancer commentedon Jan 22, 2014
This is basically rfc 5034 support? Sounds like a good idea.
I'm going to mark this issue as 'easy' because it isn't a whole lot of code, but for anyone who wants to tackle it, know that understanding the RFC and getting it *right* is not necessarily trivial, because: rfc :)
dveeden commentedon Jan 23, 2014
As far as I understood the RFC:
A client should send CAPA and check if there is a SASL tag in the response (e.g. "SASL PLAIN").
===============================
+OK Dovecot ready.
AUTH PLAIN base64_encoded_info
+OK Logged in.
LIST
===============================
I've replace the base64 encoded authentication info with 'base64_encoded_info'
For other authentication mechanisms the response can be longer (it may contain a challenge) and the request may only contain the mechanim.
I don't have a server which supports anything else than AUTH PLAIN, so I could verify/test this.
bitdancer commentedon Jan 23, 2014
imaplib has an API for handling that kind of thing. Maybe we can model the poplib support off of that API. It would be nice to be consistent, assuming it in fact makes sense for poplib as well.