-
Notifications
You must be signed in to change notification settings - Fork 307
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
Cannot connect to Cyrus IMAP 2.5 - hangs on login #600
Comments
Hm, weird. The server sends a response to |
Thanks! Yes! It does! It works now! The output now looks like this:
|
Re-opening because this is just a workaround, it would be nice to investigate what exactly is going on. |
Let me know, if there is anything I can help with. I will. BTW: I am aware that the Cyrus IMAP 2.5.10 is quite outdated (released Oct 2016). But it still does its job. ;) |
I am using the general example to Dial and Login to the IMAP server. I can DialTLS but I am failing to Login.
Code:
It hangs on the Wait(). If the Wait() is not specified, it passes through with:
failed to login: &{T1 0xc000079260 <nil>}
I used the
options := &imapclient.Options{ DebugWriter: os.Stdout, }
which prints out this:And the code stalls and never finishes.
I tried other IMAP servers and was able to connect to it. I am using the Cyrus IMAP server with several email clients - desktop, mobile, webmail and everything works OK.
When I looked at the outputs, it looks like it may be because it is missing something like
OK LOGIN Completed
confirmation.I have looked into the RFC 9051 and the LOGIN and it states:
This makes me thinking that it is OK that the server does not respond to the LOGIN message (although, I would also rather see it does). But since it proceeds further with the CAPABILITY announcement it somewhat implies that the LOGIN went through OK.
Anyone came across this and is it a problem (unusual use case) with the imap package or is it a problem of the Cyrus IMAP server, or both?
Thanks in advance!
The text was updated successfully, but these errors were encountered: