-
-
Notifications
You must be signed in to change notification settings - Fork 97
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
Support other TLS provider and unify cargo features #493
Comments
Sorry for the delay. Looks definitely like a TLS issue, but does not look obvious to me at first glance. When I compare with my logs:
I notice that your server drops straight the Does your server support STARTTLS? If so, could you try? PS: you can now download a pre-built binary from the CI, which prevents you to rebuild the project. This only work if you use default cargo features! |
This is the full error: |
To summarize: |
Ok... Sad news. Just two comments:
And nothing else happens. It looks like it is trying to build the IMAP client for ever.
Thanks for checking this out! |
It basically means that the server does not support STARTTLS as well. Although he infinite loop is strange, I will check if there is not an issue with the retry algorithm
After investigation from Rustls, it's not a TLS version issue but more a ciphersuites one. Your server seems to only support an old, insecure algorithm (DHE) that is purposefully not handled by Rustls.
If I do not mistake, meli only supports native-tls.
Stay tuned! I will update this issue every time a new step is done. |
FWI, I change the scope of this issue. It now stands for cargo features unification and support for different TLS providers (which would solve your initial issue). |
Hi,
Since you are testing v1.0.0 I am coming back with this issue. Today I was able to build the master branch from source (something that had failed in all my previous attempts). But I am still unable to access my university account.
My config.toml looks like this:
When I run
himalaya
I am asked for my pass password, and when I type it I get the following error. This has not changed with respect to v0.9.0.The output of
himalaya --debug
is:The output of
himalaya --trace
is:I don´t know what causes this issue, but I have successfully configured other mail clients with essentially the same config. I hope this can be fixed...
Thanks!
The text was updated successfully, but these errors were encountered: