You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 19, 2022. It is now read-only.
Describe the bug
When I log in with my custom mail server configuration, very similar to #162 (same ports), the only error message I see is "Login failed". It should work however, my provided login information is definitely correct. But the more immediate problem here is that there doesnt seem to be a way to see the cause of the failure (see screenshot below)
To Reproduce
Occurrence: always
Steps to reproduce the behavior: This will be somewhat verbose as the behavior varies from case to case. The main issue is with point 1:
Normal login with custom information:
Configure mail settings: Manual settings
Custom mail server from https://lima-city.de. See screenshot below for connection details
Insert correct credentials and mail address, click "Sign in"
Expected behavior: successful login
Acutal behavior: Loading progress continues until 86.0%, then error "Login failed" without details
Same with detailed information:
Insert complete detailed information, including ports
Expected / actual behavior: same as 1.
Endless loading screen with invalid password:
Insert wrong password, then sign in
Expected behavior: Error: Invalid credentials
Actual behavior: Loading progress continues until 65.0%, then stops and loads forever, not even an error message. Need to kill the app.
Without specifying mail server addresses (they do not match the email address domain name):
Remove mail server entries
Expected behavior: Error: Could not connect to server
Actual behavior: Loading progress continues until 80.0%, then error "Login failed" without details
With IMAP TLS port:
Insert correct mail servers and password like step 1
Set IMAP port to 143, leave IMAP Security at "Automatic", then sign in
Expected behavior: Same as 1, as lima-city seems to accept port 143 via TLS
Actual behavior: Loading progress continues until 86.0%, then error "Login failed" with detailed message (yey!) Could not connect to mail.lima-city.de:143: async_native_tls: error:1408F10B:SSL routines:ssl3_get_record:wrong version number:ssl/record/ssl3_record.c:332:
Screenshots
Login error:
lima-city.de login information:
App information (please complete the following information):
App version: v0.600.3.1006 – according to Aurora Store, from where I installed it
Plugin version, Delta Chat Core version, Flutter version: I'm sorry, but I cannot see any way to determine those version numbers.
Smartphone (please complete the following information):
Additional context
Interestingly, I faced very similar issues with Delta Chat: I could not connect with the lima-city mail server either. In that case, I got the error message that the SMTP connection to port 25 was rejected – even when I typed in SSL/465 which sounds very much like #162 too. But that issue was fixed, it seems. And this isnt Delta Chat, so probably not related.
Thanks for this report. This level of comprehensiveness is pretty pretty rare. That you face something similar with Delta Chat makes totally sense, as we are using the same core / backend under the hood (https://github.com/open-xchange/flutter-deltachat-core) 👍 .
Describe the bug
When I log in with my custom mail server configuration, very similar to #162 (same ports), the only error message I see is "Login failed". It should work however, my provided login information is definitely correct. But the more immediate problem here is that there doesnt seem to be a way to see the cause of the failure (see screenshot below)
To Reproduce
Occurrence: always
Steps to reproduce the behavior: This will be somewhat verbose as the behavior varies from case to case. The main issue is with point 1:
Normal login with custom information:
Same with detailed information:
Endless loading screen with invalid password:
Without specifying mail server addresses (they do not match the email address domain name):
With IMAP TLS port:
Could not connect to mail.lima-city.de:143: async_native_tls: error:1408F10B:SSL routines:ssl3_get_record:wrong version number:ssl/record/ssl3_record.c:332:
Screenshots
Login error:
lima-city.de login information:
App information (please complete the following information):
Smartphone (please complete the following information):
Additional context
Interestingly, I faced very similar issues with Delta Chat: I could not connect with the lima-city mail server either. In that case, I got the error message that the SMTP connection to port 25 was rejected – even when I typed in SSL/465 which sounds very much like #162 too. But that issue was fixed, it seems. And this isnt Delta Chat, so probably not related.
Internal Bug Tracker.
The text was updated successfully, but these errors were encountered: