Skip to content
This repository has been archived by the owner on Oct 19, 2022. It is now read-only.

"Login failed" without any further information #617

Open
phil294 opened this issue Jun 30, 2020 · 1 comment
Open

"Login failed" without any further information #617

phil294 opened this issue Jun 30, 2020 · 1 comment
Labels
bug Something isn't working

Comments

@phil294
Copy link

phil294 commented Jun 30, 2020

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:

  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
  2. Same with detailed information:

    • Insert complete detailed information, including ports
    • Expected / actual behavior: same as 1.
  3. 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.
  4. 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
  5. 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:
Login error

lima-city.de login information:
lima-city login info

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):

  • Device: Samsung Galaxy S4 Mini, see LineageOS Wiki
  • OS: MicroG+LineageOS 14.1 (Android 7.1.2)

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.

@Boehrsi
Copy link
Collaborator

Boehrsi commented Jul 1, 2020

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) 👍 .

@Boehrsi Boehrsi added the bug Something isn't working label Jul 1, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants