[wip] adding link2xt's dc_config.txt -- listing TODOs for configure issues … #1832
Conversation
…found from user testing
| 9. configure: connection refused error suggests to check the inbox, even if IMAP can't connect | ||
|
|
||
| If connection is refused, it does not make sense to suggest checking | ||
| the inbox. Especially if IMAP failed or domain can't be resolved. | ||
|
|
||
| Current error message is too broad and usually irrelevant and not helpful: | ||
|
|
||
| Some providers place additional information in your inbox; you can | ||
| check them eg. in the web frontend. Consult your provider or friends | ||
| if you run into problems. | ||
|
|
||
| Which providers place information about failed login attempts into | ||
| inbox? Is it helpful or just "someone from ... tried to login with | ||
| incorrect password"? |
There was a problem hiding this comment.
GMX and Yahoo do send you a helpful error email IIRC. However, the provider-db also shows this information, so it is actually not needed.
Moreover, many users will probably not understand "Some providers place additional information in your inbox; you can check them eg. in the web frontend." And "Consult your provider or friends if you run into problems" is a nice advice but many users will ask their techie friends anyway and the provider will probably not help.
Together with point 8 we could do:
IMAP login failed.
Trying example.org ... port closed
Trying imap.example.org ... could not resolve address
Trying mail.example.org ... incorrect login
(and if it seems to be the password, tell the user to check the pw, as we already do)
|
Incorrect, in fact I just fixed it in #1835. In current master, the problem is here for IMAP: |
|
Some of the issues are already fixed, some I have moved to https://github.com/orgs/deltachat/projects/26 I keep track of all of them locally too, so none of them will be lost. |
|
thanks for taking care! |
…found from user testing.