We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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.
The text was updated successfully, but these errors were encountered:
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
PR #1820 implements a first shot at this, a very basic support of PREAUTH.
PREAUTH
Sorry, something went wrong.
d64a19b
befaa7b
No branches or pull requests
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
It returns:
This is not supported by curl although part of the IMAP RFC.
The text was updated successfully, but these errors were encountered: