This exact patch that you back out was the result of a direct TB Council decision, specifically regarding this patch. Not only the MFA case, but also the case that IMAP might be disabled, as well as other custom configurations, were part of the TB Council discussion and decision basis. You violate TB Council decisions by backing this out. > disabled IMAP - which there is little reason for anyone to do Many admins restrict access to the absolute minimum necessary, based on the officially supported applications, use cases and policies that are in place at their company. What we think about their motivations is not relevant. > MFA is supported for all there is no reason to do this autodetection See my comments 93, comment 98 and others before. I personally created a paid Office365 test account for you and given it specifically to you. --- Independent: It doesn't work at all for me. Even my Office365 test accounts that have IMAP *enabled* and need MFA do not work after your fix.
Bug 1528136 Comment 100 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
This exact patch that you back out was the result of a direct TB Council decision, specifically regarding this patch. Not only the MFA case, but also the case that IMAP might be disabled, as well as other custom configurations, were part of the TB Council discussion and decision basis. You violate TB Council decisions by backing this out. > MFA is supported for all there is no reason to do this autodetection See my comments 93, comment 98 and others before. I personally created a paid Office365 test account for you and given it specifically to you. > disabled IMAP - which there is little reason for anyone to do Many admins restrict access to the absolute minimum necessary, based on the officially supported applications, use cases and policies that are in place at their company. What we think about their motivations is not relevant. --- Independent: It doesn't work at all for me. Even my Office365 test accounts that have IMAP *enabled* and need MFA do not work after your fix.
This exact patch that you back out was the result of a direct TB Council decision, specifically regarding this patch. Not only the MFA case, but also the case that IMAP might be disabled, as well as other custom configurations, were part of the TB Council discussion and decision basis. You violate TB Council decisions by backing this out. > MFA is supported for all there is no reason to do this autodetection See my comments 93, comment 98 and others before. I personally created a paid Office365 test account for you and given it specifically to you. > disabled IMAP - which there is little reason for anyone to do Many admins restrict access to the absolute minimum necessary, based on the officially supported applications, use cases and policies that are in place at their company. What we think about their motivations is not relevant. You just broke their users without any need. If there is any code conflict, let's fix that. --- Independent: Your fix doesn't work at all for me. Even my Office365 test accounts that have IMAP *enabled* and need MFA do not work after your fix.
If there is any code conflict, let's fix that. I'd be happy to help. This exact patch that you back out was the result of a direct TB Council decision, specifically regarding this patch. Not only the MFA case, but also the case that IMAP might be disabled, as well as other custom configurations, were part of the TB Council discussion and decision basis. You violate TB Council decisions by backing this out. > MFA is supported for all there is no reason to do this autodetection See my comments 93, comment 98 and others before. I personally created a paid Office365 test account for you and given it specifically to you. > disabled IMAP - which there is little reason for anyone to do Many admins restrict access to the absolute minimum necessary, based on the officially supported applications, use cases and policies that are in place at their company. What we think about their motivations is not relevant. Let's fix it instead of breaking users. --- Independent: Your fix doesn't work at all for me. Even my Office365 test accounts that have IMAP *enabled* and need MFA do not work after your fix.
If there is any code conflict, let's fix that. I'd be happy to help. This exact patch that you back out was the result of a direct TB Council decision, specifically regarding this patch. Not only the MFA case, but also the case that IMAP might be disabled, as well as other custom configurations, were part of the TB Council discussion and decision basis. You violate TB Council decisions by backing this out. > MFA is supported for all there is no reason to do this autodetection See my comment 93, comment 98 and others before. I personally created a paid Office365 test account for you and given it specifically to you. > disabled IMAP - which there is little reason for anyone to do Many admins restrict access to the absolute minimum necessary, based on the officially supported applications, use cases and policies that are in place at their company. What we think about their motivations is not relevant. Let's fix it instead of breaking users. --- Independent: Your fix doesn't work at all for me. Even my Office365 test accounts that have IMAP *enabled* and need MFA do not work after your fix.