Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

imap does not support PREAUTH #1818

Closed
nmorey opened this issue Aug 22, 2017 · 1 comment
Closed

imap does not support PREAUTH #1818

nmorey opened this issue Aug 22, 2017 · 1 comment
Labels
IMAP

Comments

@nmorey
Copy link

@nmorey nmorey commented Aug 22, 2017

I'm working on tunneling support for git imap-send (run curl through a preopened socket using
CURLOPT_OPENSOCKETFUNCTION and CURLOPT_SOCKOPTFUNCTION.

The command to open the socket (stdin/stdout) during testing is this one

ssh -q -C localhost /usr/sbin/imapd ./Maildir

It returns:

* PREAUTH [CAPABILITY IMAP4REV1 I18NLEVEL=1 LITERAL+ IDLE UIDPLUS NAMESPACE CHILDREN MAILBOX-REFERRALS BINARY UNSELECT ESEARCH WITHIN SCAN SORT THREAD=REFERENCES THREAD=ORDEREDSUBJECT MULTIAPPEND] Pre-authenticated user [...]

This is not supported by curl although part of the IMAP RFC.
@bagder bagder added the IMAP label Aug 22, 2017
bagder added a commit that referenced this issue Aug 22, 2017
@bagder
imap: support PREAUTH
a48f4be 
It is a defined possible greeting at server startup that means the
connection is already authenticated. See
https://tools.ietf.org/html/rfc3501#section-7.1.4

Test 846 added to verify.

Fixes #1818
@bagder bagder mentioned this issue Aug 22, 2017
Closed
@bagder
Copy link
Member

@bagder bagder commented Aug 22, 2017

PR #1820 implements a first shot at this, a very basic support of PREAUTH.

bagder added a commit that referenced this issue Aug 23, 2017
@bagder
imap: support PREAUTH
d64a19b 
It is a defined possible greeting at server startup that means the
connection is already authenticated. See
https://tools.ietf.org/html/rfc3501#section-7.1.4

Test 846 added to verify.

Fixes #1818
@lock lock bot locked as resolved and limited conversation to collaborators May 6, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
IMAP
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@nmorey @bagder