> we just focus on ensuring that the ordering from comment 13 is respected. Agreed. > As a lower order check, the autodiscover check should not be able to interrupt the process and discard results from the higher order checks. No. I've explained: If AutoDiscover returns HTTP 401, we *know* for a fact that the credentials we have are wrong. The user must first enter the correct credentials, before we proceed. It makes no sense to continue with known-wrong credentials. They will fail for any kind of config, even IMAP from config.xml. If you fail at the IMAP password verification, you give the user no hint that the username might be wrong, and you run into exactly the situation explained in comment 33.
Bug 1599029 Comment 35 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
> we just focus on ensuring that the ordering from comment 13 is respected. Agreed. > As a lower order check, the autodiscover check should not be able to interrupt the process and discard results from the higher order checks. No. I've explained: If AutoDiscover returns HTTP 401, we *know* for a fact that the credentials we have are wrong. The user must first enter the correct credentials, before we proceed. It makes no sense to continue with known-wrong credentials. They will fail for any kind of config, even IMAP from config.xml. This is a speciality of the on-premise Exchange servers. We are able to detect the specific situation and react correctly. Your suggestion would break that. If you fail at the IMAP password verification, you give the user no hint that the username might be wrong, and you run into exactly the situation explained in comment 33.
> we just focus on ensuring that the ordering from comment 13 is respected. Agreed. > As a lower order check, the autodiscover check should not be able to interrupt the process and discard results from the higher order checks. No. I've explained: If AutoDiscover returns HTTP 401, we *know* for a fact that the credentials we have are wrong. The user must first enter the correct credentials, before we proceed. It makes no sense to continue with known-wrong credentials. They will fail for any kind of config, even IMAP from config.xml. This is a speciality of the on-premise Exchange servers. We are lucky to be able to detect the specific situation and react correctly. Your suggestion would break that. If you fail at the IMAP password verification, you give the user no hint that the username might be wrong, and you run into exactly the situation explained in comment 33.
> we just focus on ensuring that the ordering from comment 13 is respected. Agreed. > As a lower order check, the autodiscover check should not be able to interrupt the process and discard results from the higher order checks. No. I've explained: If AutoDiscover returns HTTP 401, we *know* for a fact that the credentials we have are wrong. The user must first enter the correct credentials, before we proceed. It makes no sense to continue with known-wrong credentials. They will fail for any kind of config, even IMAP from config.xml. This is a speciality of the on-premise Exchange servers. We are lucky to be able to detect the specific situation and react correctly. Your suggestion would break that. If you skip that, use IMAP, and fail at the IMAP password verification, you give the user no hint that the username might be wrong, and you run into exactly the situation explained in comment 33.
> we just focus on ensuring that the ordering from comment 13 is respected. Agreed. > As a lower order check, the autodiscover check should not be able to interrupt the process and discard results from the higher order checks. No. I've explained: If AutoDiscover returns HTTP 401, we *know* for a fact that the credentials we have are wrong. The user must first enter the correct credentials, before we proceed. It makes no sense to continue with known-wrong credentials. They will fail for any kind of config, even IMAP from config.xml. This is a speciality of the on-premise Exchange servers. We are lucky to be able to detect the specific situation and react correctly. Your suggestion would break that. If you skip that, and fail at the IMAP password verification, you give the user no hint that the username might be wrong, and you run into exactly the situation explained in comment 33.
> we just focus on ensuring that the ordering from comment 13 is respected. Agreed. > As a lower order check, the autodiscover check should not be able to interrupt the process and discard results from the higher order checks. No, that doesn't automatically follow. I've explained: If AutoDiscover returns HTTP 401, we *know* for a fact that the credentials we have are wrong. The user must first enter the correct credentials, before we proceed. It makes no sense to continue with known-wrong credentials. They will fail for any kind of config, even IMAP from config.xml. This is a speciality of the on-premise Exchange servers. We are lucky to be able to detect the specific situation and react correctly. Your suggestion would break that. If you skip that, and fail at the IMAP password verification, you give the user no hint that the username might be wrong, and you run into exactly the situation explained in comment 33.