Bugzilla

> Reiterating the same concepts is not productive, so please stop.

Well, I'm happy to stop reiterating the same argument the minute that you acknowledge that you're comparing apples with pears. You're comparing a user error edge case which is rather unlikely with a very common case. If we can't have a perfect solution, we should have one that works well in the more likely use case. That's what **you** said during our call, IIRC. I even tried to mitigate any exchange selection confusion by clearly displaying an info message. Whilst TB cannot accurately tell whether we're dealing with a user error case, the user most likely can. Sadly in your deliberation you have ignored that suggestion, as you have ignored my e-mail to the people involved here.

So in absence of any acknowledgement, the only option I have is to repeat the point. So please adhere to efficient and productive communication before telling others to mend their ways :-(

The patch here has the three problems: 1) It opens an additional vulnerability 2) It affects on-premise Exchange servers 3) It has a UX issue in that a non-functioning option is presented 4) Existing Owl users can't set up a new account 5) it has implementation issues.

Yes, I repeated that now, but again, you didn't address these concerns directly related to the new patch.

I saw a new comment just came in in which you report on testing with the O365 test accounts. That's insufficient since the patch also affects on-premise Exchange accounts where after bug 1598861 the "authoritative" server reply will now be completely ignored. Also, please comment on comment #118, last dot point "Policy question".

> Reiterating the same concepts is not productive, so please stop.

Well, I'm happy to stop reiterating the same argument the minute that you acknowledge that you're comparing apples with pears. You're comparing a user error edge case which is rather unlikely with a very common case. If we can't have a perfect solution, we should have one that works well in the more likely use case. That's what **you** said during our call, IIRC. I even tried to mitigate any exchange selection confusion by clearly displaying an info message. Whilst TB cannot accurately tell whether we're dealing with a user error case, the user most likely can. Sadly in your deliberation you have ignored that suggestion, as you have ignored my e-mail to the people involved here.

So in absence of any acknowledgement, the only option I have is to repeat the point. So please adhere to efficient and productive communication before telling others to mend their ways :-(

The patch here has the five problems: 1) It opens an additional vulnerability 2) It affects on-premise Exchange servers 3) It has a UX issue in that a non-functioning option is presented 4) Existing Owl users can't set up a new account 5) it has implementation issues.

Yes, I repeated that now, but again, you didn't address these concerns directly related to the new patch.

I saw a new comment just came in in which you report on testing with the O365 test accounts. That's insufficient since the patch also affects on-premise Exchange accounts where after bug 1598861 the "authoritative" server reply will now be completely ignored. Also, please comment on comment #118, last dot point "Policy question".