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

imap does not support PREAUTH #1818

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

Comments

Projects
None yet
2 participants
@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

imap: support PREAUTH
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

This comment has been minimized.

Show comment
Hide comment
@bagder

bagder Aug 22, 2017

Member

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

Member

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

imap: support PREAUTH
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 closed this in befaa7b Aug 23, 2017

@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.