That explains why it didn't work for me. I did log in to the account with Firefox, but with a different IP address. I also am using the account creation dialog, obviously. It seems there are 3 independent (!) problems: 1. It doesn't automatically detect the authentication method. -> The auth method needs to be added to the config object. We cannot do that in the ISPDB, because TB 68 would then also try to do it for Outlook and fail, so the only idea I have right now is to make a special hack for Office365 in the code, until TB 68 is dead. I might have a better idea later. 2. The OAuth2 doesn't actually grant access, unless a browser login happened before. -> No idea what the fix would be. 3. Users with disabled IMAP and other custom settings get a non-working config. -> The backed out patch fixes that.
Bug 1528136 Comment 108 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
That explains why it didn't work for me. I did log in to the account with Firefox, but with a different IP address. I also am using the account creation dialog, obviously. It seems there are 3 independent (!) problems: 1. It doesn't automatically detect the authentication method -> The auth method needs to be added to the config object. We cannot do that in the ISPDB, because TB 68 would then also try to do it for Offic365 and fail, so the only idea I have right now is to make a special hack for Office365 in the code, until TB 68 is dead. I might have a better idea later. 2. The OAuth2 doesn't actually grant access, unless a browser login happened before. -> No idea what the fix would be. 3. Users with disabled IMAP and other custom settings get a non-working config. -> The backed out patch fixes that.
That explains why it didn't work for me. I did log in to the account with Firefox, but with a different IP address. I also am using the account creation dialog, obviously. It seems there are 3 independent (!) problems: 1. It doesn't automatically detect the authentication method -> The auth method needs to be added to the config object. We cannot do that in the ISPDB, because TB 68 would then also try to do it for Offic365 and fail, so the only idea I have right now is to make a special hack for Office365 in the code, until TB 68 is dead. I might have a better idea later. 2. The OAuth2 doesn't actually grant access, unless a browser login happened before. -> No idea what the fix would be. We probably need to emulate a Firefox browser more. 3. Users with disabled IMAP and other custom settings get a non-working config. -> The backed out patch fixes that.
That explains why it didn't work for me. I did log in to the account with Firefox, but with a different IP address. I also am using the account creation dialog, obviously. It seems there are 3 independent (!) problems: 1. It doesn't automatically detect the authentication method -> The auth method needs to be added to the config object. We cannot do that in the ISPDB, because TB 68 would then also try to do it for Offic365 and fail, so the only idea I have right now is to make a special hack for Office365 in the code, until TB 68 is dead. I might have a better idea later. 2. The OAuth2 doesn't actually grant access, unless a browser login happened before. -> No idea what the fix would be. We probably need to emulate a Firefox browser more. I'd start with the user agent string. 3. Users with disabled IMAP and other custom settings get a non-working config. -> The backed out patch fixes that.
That explains why it didn't work for me. I did log in to the account with Firefox, but with a different IP address. I also am using the account creation dialog, obviously. It seems there are 3 independent (!) problems: 1. It doesn't automatically detect the authentication method -> The auth method needs to be added to the config object. We cannot do that in the ISPDB, because TB 68 would then also try to do it for Offic365 and fail, so the only idea I have right now is to make a special hack for Office365 in the code, until TB 68 is dead. I might have a better idea later. 2. The OAuth2 doesn't actually grant access, unless a browser login happened before. -> No idea what the fix would be. We probably need to emulate a Firefox browser more. I'd start with the user agent string, but only for this domain, obviously. 3. Users with disabled IMAP and other custom settings get a non-working config. -> The backed out patch fixes that.
That explains why it didn't work for me. I did log in to the account with Firefox, but with a different IP address. I also am using the account creation dialog, obviously. It seems there are 3 independent (!) problems: 1. It doesn't automatically detect the authentication method -> The auth method needs to be added to the config object. We cannot do that in the ISPDB, because TB 68 would then also try to do it for Offic365 and fail, so the only idea I have right now is to make a special hack for Office365 in the code, until TB 68 is dead. I might have a better idea later. 2. The OAuth2 doesn't actually grant access, unless a browser login happened before. -> No idea what the fix would be. We probably need to emulate a Firefox browser more. I'd start with the user agent string. But only for this domain, obviously. 3. Users with disabled IMAP and other custom settings get a non-working config. -> The backed out patch fixes that.