> you say this bug is invalid
I say that simply because the reproduction steps start with entering a wrong password. That's not a valid setup, that's why I said INVALID. That invalid login is what caused the downhill problems with the configs.
For Exchange servers, you must enter the password, and possibly even a different username, otherwise nothing will work. This is needed a) for the config, but also b) for login later. It's actually helpful that we detect this case here and ask for the username. Otherwise we'd later try to log in with the email address as username, and it still won't work, independent where the config came from. So, this is actually important.
Bug 1599029 Comment 16 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
> you say this bug is invalid
I say that simply because the reproduction steps start with entering a wrong password. That's not a valid setup. That invalid login is what caused the downhill problems with the configs.
For Exchange servers, you must enter the password, and possibly even a different username, otherwise nothing will work. This is needed a) for the config, but also b) for login later. It's actually helpful that we detect this case here and ask for the username. Otherwise we'd later try to log in with the email address as username, and it still won't work, independent where the config came from. So, this is actually important.