> I'm implementing the council decision now. No, you do not. TB Council decision says: "Exchange should only be advertised to the user if the other supported protocols such as IMAP are not available." For many Office365 users, IMAP is not enabled, so we're testing that. You yourself asked that in comment 14. That's what I do. My patch implements exactly that. Your patch removes known working configs and advertises configs that will not work. That makes no sense.
Bug 1592258 Comment 76 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
> I'm implementing the council decision now. No, you do not. TB Council decision says: "Exchange should only be advertised to the user if the other supported protocols such as IMAP are not available." For many Office365 users, IMAP is not enabled, so we're testing that. You yourself asked that in comment 14: "If Exchange was available, AND the normal IMAP/POP auth failed: that would be the appropriate place to advertise this alternative." That's what I do. My patch implements exactly that. Your patch removes known working configs and advertises configs that will not work. That makes no sense.
> I'm implementing the council decision now. No, you do not. TB Council decision says: "Exchange should only be advertised to the user if the other supported protocols such as IMAP are not available." For many Office365 users, IMAP is not enabled, so we're testing that. You yourself asked that in comment 14. That's what I do. My patch implements exactly that. Your patch removes known working configs and advertises configs that will not work. That makes no sense.