The initial configuration dialog gives the possibility to set individual IMAP and SMTP ports (for SSL/STARTTLS).
Expected behavior
After the email address has been entered and the domain of the respective mail provider has been identified from Delta Chat, it should correct the default values for IMAP and SMTP port and security automatically (by referring to the internal provider database).
Actual behavior
After the email address has been entered and the domain of the respective mail provider has been identified from Delta Chat, it does not correct the default values for IMAP and SMTP port and security automatically. (Posteo generally recommends STARTTLS security, which is also set in the interal provider database.)
To make the issue more understandable: People like me who are forced to use an alias address (e.g. ending with “.at” instead of “.de”) cannot log in unless the unique user ID is entered in the “Advanced” section. The default values in there are those for SSL security. Although Delta Chat can connect to Posteo with SSL just fine, it is neither recommended from Posteo nor does it match the respective parameters from the internal provider database. This could lead to a lot of wrong configuration setups every time a mail alias becomes part of the game…
so you basically want that the provider db details are filled in into the advanced fields?
I still don’t quite understand what you want. is there a bug or do you only want visual feedback for what the core is resolving the automatic values into?
From my personal view, I would call it a bug, although from a developers view, it currently might be a lack of support. That is why I have created a “feature proposal” in the forum rather than an issue on Github.
I think I should explain how users with a mail alias would deal with the situation:
Entering alias address, and password, result: bad login credentials.
Entering alias address, and password, expanding “Advanced”, and entering the real address (user ID), and password (for SMTP), result: ready, but SSL is used.
Instead, for users without alias address:
Entering address, and password, result: ready, and STARTTLS (recommended by Posteo) is used.
My concern is: Users with alias address would not think about changing port and security values as well, they just try and succeed, that’s it. They would not know about a wrong configuration unless anything does not work out right. This could be avoided by Delta Chat, by considering the parameters stored in the provider database.
When I use my alias address (".at"), I must expand “Advanced” where SSL values are set as “(Default)”. I know of course that these are not default for Posteo, so I must change them accordingly. But who else is about to know that? Most people would check out the (wrong) default settings and see Delta Chat works fine, that’s it.
BTW, the latest core version (1.39) is used in Desktop release 1.4.2.