search

jobisoft / TbSync

[Thunderbird Add-On] Central user interface to manage cloud accounts and to synchronize their contact, task and calendar information with Thunderbird
https://github.com/jobisoft/TbSync/wiki/About:-TbSync
Mozilla Public License 2.0
801 stars 54 forks source link

TBSync EAS not working since 2-3 days #706

Closed oe3gwu closed 5 months ago

oe3gwu commented 7 months ago

Your environment

Kubuntu 23.10 Thunderbird from Repos with installed TBSync

TbSync + EAS Provider version: 4.8 Thunderbird version: 115.6.0

Expected behavior

TBSync should sync my Hotmail Account

Actual behavior

Not working. Always get the error to enter my password.

Steps to reproduce

Use an Hotmail Account with TBSync

Logs:

** Thu Jan 25 2024 18:38:19 GMT+0100 (Mitteleuropäische Normalzeit) **
[setSyncState] : State: prepare.request.options, Account: rainer_weninger@hotmail.com

** Thu Jan 25 2024 18:38:19 GMT+0100 (Mitteleuropäische Normalzeit) **
[Sending] : OPTIONS https://eas.outlook.com/Microsoft-Server-ActiveSync

** Thu Jan 25 2024 18:38:19 GMT+0100 (Mitteleuropäische Normalzeit) **
[setSyncState] : State: send.request.options, Account: rainer_weninger@hotmail.com

** Thu Jan 25 2024 18:38:19 GMT+0100 (Mitteleuropäische Normalzeit) **
[setSyncState] : State: eval.request.options, Account: rainer_weninger@hotmail.com

** Thu Jan 25 2024 18:38:19 GMT+0100 (Mitteleuropäische Normalzeit) **
[EAS OPTIONS with response (status: 200)] : 
responseText: 
responseHeader(MS-ASProtocolVersions): 2.5,14.0,14.1,16.0,16.1
responseHeader(MS-ASProtocolCommands):
Sync,SendMail,SmartForward,SmartReply,GetAttachment,FolderSync,FolderCreate,FolderD
lete,FolderUpdate,MoveItems,GetItemEstimate,MeetingResponse,Search,Settings,Ping,Ite
Operations,ResolveRecipients,Find

** Thu Jan 25 2024 18:38:19 GMT+0100 (Mitteleuropäische Normalzeit) **
[setSyncState] : State: prepare.request.setdeviceinfo, Account:
rainer_weninger@hotmail.com

** Thu Jan 25 2024 18:38:19 GMT+0100 (Mitteleuropäische Normalzeit) **
[setSyncState] : State: send.request.setdeviceinfo, Account: rainer_weninger@hotmail.com

** Thu Jan 25 2024 18:38:19 GMT+0100 (Mitteleuropäische Normalzeit) **
[Sending (EAS v14.0)] : POST https://eas.outlook.com/Microsoft-Server-ActiveSync
Cmd=Settings&User=rainer_weninger%40hotmail.com&DeviceType=TbSync&DeviceId=MZ
B559bf278587b0b4abbdbb92cb4ec

** Thu Jan 25 2024 18:38:19 GMT+0100 (Mitteleuropäische Normalzeit) **
[setSyncState] : State: passwordprompt, Account: rainer_weninger@hotmail.com

** Thu Jan 25 2024 18:38:21 GMT+0100 (Mitteleuropäische Normalzeit) **
[setSyncState] : State: send.request.setdeviceinfo, Account: rainer_weninger@hotmail.com

** Thu Jan 25 2024 18:38:21 GMT+0100 (Mitteleuropäische Normalzeit) **
[Sending (EAS v14.0)] : POST https://eas.outlook.com/Microsoft-Server-ActiveSync
Cmd=Settings&User=rainer_weninger%40hotmail.com&DeviceType=TbSync&DeviceId=MZB559bf278587b0b4abbdbb92cb4ec

** Thu Jan 25 2024 18:38:21 GMT+0100 (Mitteleuropäische Normalzeit) **
[setSyncState] : State: passwordprompt, Account: rainer_weninger@hotmail.com

** Thu Jan 25 2024 18:38:23 GMT+0100 (Mitteleuropäische Normalzeit) **
[EventLog] : 401


** Thu Jan 25 2024 18:38:23 GMT+0100 (Mitteleuropäische Normalzeit) **
[EventLog] : 401


** Thu Jan 25 2024 18:38:23 GMT+0100 (Mitteleuropäische Normalzeit) **
[setSyncState] : State: accountdone, Account: rainer_weninger@hotmail.com
Jumpiebeen commented 7 months ago

Is there any way to roll this back? I have the same issue for the same time period.

Debug: Fri Jan 26 2024 00:29:35 GMT-0600 (Central Standard Time) [TbSync init] : Start (4.8) Fri Jan 26 2024 00:29:35 GMT-0600 (Central Standard Time) [Thunderbird] : 115.6.0 on Linux Fri Jan 26 2024 00:29:35 GMT-0600 (Central Standard Time) [Loading module ] : OK Fri Jan 26 2024 00:29:35 GMT-0600 (Central Standard Time) [Loading module ] : OK Fri Jan 26 2024 00:29:35 GMT-0600 (Central Standard Time) [Loading module ] : OK Fri Jan 26 2024 00:29:35 GMT-0600 (Central Standard Time) [Loading module ] : OK Fri Jan 26 2024 00:29:35 GMT-0600 (Central Standard Time) [Loading module ] : OK Fri Jan 26 2024 00:29:35 GMT-0600 (Central Standard Time) [Loading module ] : OK Fri Jan 26 2024 00:29:35 GMT-0600 (Central Standard Time) [Loading module ] : OK Fri Jan 26 2024 00:29:35 GMT-0600 (Central Standard Time) [Loading module ] : OK Fri Jan 26 2024 00:29:35 GMT-0600 (Central Standard Time) [Loading module ] : OK Fri Jan 26 2024 00:29:35 GMT-0600 (Central Standard Time) [Loading module ] : OK Fri Jan 26 2024 00:29:35 GMT-0600 (Central Standard Time) [Loading module ] : OK Fri Jan 26 2024 00:29:35 GMT-0600 (Central Standard Time) [Initializing module] : Fri Jan 26 2024 00:29:35 GMT-0600 (Central Standard Time) [Initializing module] : Fri Jan 26 2024 00:29:35 GMT-0600 (Central Standard Time) [Initializing module] : Fri Jan 26 2024 00:29:35 GMT-0600 (Central Standard Time) [Initializing module] : Fri Jan 26 2024 00:29:35 GMT-0600 (Central Standard Time) [Initializing module] : Fri Jan 26 2024 00:29:35 GMT-0600 (Central Standard Time) [Initializing module] : Fri Jan 26 2024 00:29:35 GMT-0600 (Central Standard Time) [Initializing module] : Fri Jan 26 2024 00:29:35 GMT-0600 (Central Standard Time) [Initializing module] : Fri Jan 26 2024 00:29:35 GMT-0600 (Central Standard Time) [Initializing module] : Fri Jan 26 2024 00:29:35 GMT-0600 (Central Standard Time) [Initializing module] : Fri Jan 26 2024 00:29:35 GMT-0600 (Central Standard Time) [Initializing module] : Fri Jan 26 2024 00:29:35 GMT-0600 (Central Standard Time) [TbSync init] : Done Fri Jan 26 2024 00:29:35 GMT-0600 (Central Standard Time) [EventLog] : Default timezone has been found. Fri Jan 26 2024 00:29:35 GMT-0600 (Central Standard Time) [EventLog] : The IANA timezone <America/Ciudad_Juarez> cannot be mapped to any Exchange timezone. Fri Jan 26 2024 00:29:35 GMT-0600 (Central Standard Time) [EventLog] : The IANA timezone <Antarctica/Troll> cannot be mapped to any Exchange timezone. Fri Jan 26 2024 00:29:35 GMT-0600 (Central Standard Time) [EventLog] : The IANA timezone cannot be mapped to any Exchange timezone. Fri Jan 26 2024 00:29:35 GMT-0600 (Central Standard Time) [EventLog] : The IANA timezone cannot be mapped to any Exchange timezone. Fri Jan 26 2024 00:29:35 GMT-0600 (Central Standard Time) [EventLog] : The IANA timezone <SystemV/AST4> cannot be mapped to any Exchange timezone. Fri Jan 26 2024 00:29:35 GMT-0600 (Central Standard Time) [EventLog] : The IANA timezone <SystemV/AST4ADT> cannot be mapped to any Exchange timezone. Fri Jan 26 2024 00:29:35 GMT-0600 (Central Standard Time) [EventLog] : The IANA timezone <SystemV/CST6> cannot be mapped to any Exchange timezone. Fri Jan 26 2024 00:29:35 GMT-0600 (Central Standard Time) [EventLog] : The IANA timezone <SystemV/CST6CDT> cannot be mapped to any Exchange timezone. Fri Jan 26 2024 00:29:35 GMT-0600 (Central Standard Time) [EventLog] : The IANA timezone <SystemV/EST5> cannot be mapped to any Exchange timezone. Fri Jan 26 2024 00:29:35 GMT-0600 (Central Standard Time) [EventLog] : The IANA timezone <SystemV/EST5EDT> cannot be mapped to any Exchange timezone. Fri Jan 26 2024 00:29:35 GMT-0600 (Central Standard Time) [EventLog] : The IANA timezone <SystemV/HST10> cannot be mapped to any Exchange timezone. Fri Jan 26 2024 00:29:35 GMT-0600 (Central Standard Time) [EventLog] : The IANA timezone <SystemV/MST7> cannot be mapped to any Exchange timezone. Fri Jan 26 2024 00:29:35 GMT-0600 (Central Standard Time) [EventLog] : The IANA timezone <SystemV/MST7MDT> cannot be mapped to any Exchange timezone. Fri Jan 26 2024 00:29:35 GMT-0600 (Central Standard Time) [EventLog] : The IANA timezone <SystemV/PST8> cannot be mapped to any Exchange timezone. Fri Jan 26 2024 00:29:35 GMT-0600 (Central Standard Time) [EventLog] : The IANA timezone <SystemV/PST8PDT> cannot be mapped to any Exchange timezone. Fri Jan 26 2024 00:29:35 GMT-0600 (Central Standard Time) [EventLog] : The IANA timezone <SystemV/YST9> cannot be mapped to any Exchange timezone. Fri Jan 26 2024 00:29:35 GMT-0600 (Central Standard Time) [EventLog] : The IANA timezone <SystemV/YST9YDT> cannot be mapped to any Exchange timezone. Fri Jan 26 2024 00:29:35 GMT-0600 (Central Standard Time) [Loaded provider] : eas::Exchange ActiveSync (4.8) Fri Jan 26 2024 00:30:35 GMT-0600 (Central Standard Time) [setSyncState] : State: prepare.request.options, Account: outlook Fri Jan 26 2024 00:30:35 GMT-0600 (Central Standard Time) [Sending] : OPTIONS https://eas.outlook.com/Microsoft-Server-ActiveSync Fri Jan 26 2024 00:30:35 GMT-0600 (Central Standard Time) [setSyncState] : State: send.request.options, Account: outlook Fri Jan 26 2024 00:30:35 GMT-0600 (Central Standard Time) [setSyncState] : State: eval.request.options, Account: outlook Fri Jan 26 2024 00:30:35 GMT-0600 (Central Standard Time) [setSyncState] : State: passwordprompt, Account: outlook Fri Jan 26 2024 00:30:44 GMT-0600 (Central Standard Time) [EventLog] : 401 Fri Jan 26 2024 00:30:44 GMT-0600 (Central Standard Time) [EventLog] : 401

jobisoft commented 7 months ago

Microsoft apparently dropped support for plain password auth. You need to use the OAUTH option (3rd option when creating an EAS account).

jcs0596223 commented 7 months ago

I am having the same problem - my password is not being accepted but I can read/send email via IMAP. I think I have changed server authentication to OAUTH2 (5 th option) but it is still prompting me for the password. The third option is Kerberos

Jumpiebeen commented 7 months ago

As John said, you should delete the TBSync account and re-create it using the OATH option for authentication. On my version the OATH is labled Office365. Screenshot from 2024-01-27 08-25-32

jcs0596223 commented 7 months ago

Thanks - that appears to have done the trick. It was not at all obvious!

Dave-Lowndes commented 7 months ago

Deleting/re-creating as the Microsoft Office 365 setting worked for 1 of my 3 outlook.com accounts. The other 2 fail with:

The server does not provide information about the supported ActiveSync versions....

Setting the account to a specific AS version results in "Communication error (HTTP status 503)." Caching issue maybe?

oe3gwu commented 7 months ago

It works for me to use TBSync with OAuth2. To all that read this and have IMAP issues too, you need to use OAuth2 also on the IMAP Settings.

hugo-b-r commented 7 months ago

Hello. I recently had the same problem for my mail account and found this, posting it hoping it will be helpful to understand the issue.

So it doesn't seems to be a TbSync issue.

Dave-Lowndes commented 7 months ago

Deleting/re-creating as the Microsoft Office 365 setting worked for 1 of my 3 outlook.com accounts. The other 2 fail with:

The server does not provide information about the supported ActiveSync versions....

Today, 2 of 3 work with TbSync. Maybe the third will tomorrow!

Dave-Lowndes commented 7 months ago

Today, 2 of 3 work with TbSync. Maybe the third will tomorrow!

Just a few hours later - and now the 3'rd account is fine with TbSync too.

CharalamposKarampasis commented 7 months ago

Microsoft apparently dropped support for plain password auth. You need to use the OAUTH option (3rd option when creating an EAS account).

Hi all, A quick question, which of the following steps should I do when I am changing the OAUTH ? See attached photos Screenshot from 2024-01-29 16-57-41 Screenshot from 2024-01-29 16-58-46

Dave-Lowndes commented 7 months ago

SSL/TLS is what I'm using (successfully)

CharalamposKarampasis commented 7 months ago

SSL/TLS is what I'm using (successfully)

You had right , all done and sync!! At the beginning a had a message ''error''again but no matter I just click to continue and fixed.

Dave-Lowndes commented 6 months ago

I have 3 Outlook accounts configured and I'm finding that only the first synchronizes OK, others have failures (HTTP 503).

However, if I close Thunderbird, re-open it and then quickly open TbSync and use "Synchronize now" on say the 3'rd account it works, and now the first and second have the failures. I can now repeatedly use "Synchronize now" OK on the 3'rd account, and the other 2 repeatedly fail the same way.

Is something from the initial sync connection being held open so the others then fail?

jobisoft commented 6 months ago

That is related to a missing cookie implementation/support in TbSync. I somehow need to give all connections an independent cookie stores, otherwise they all try to use the same and that does not work. I am looking into this.

goshoom commented 5 months ago

I couldn't get it working since January, but I finally succeeded. I was connecting to outlook.com and the primary alias of my Microsoft account wasn't the one with outlook.com address. When I made that primary, TB sync has been able to connect. It's looks weird to me that I suddenly had to change the primary alias (to a different one than I actually want and used for years), but at least there is a solution. This doesn't seem to be an issue with TbSync as such; I was unable to connect to the new Outlook either.

jobisoft commented 5 months ago

The remaining issue is the cookie issue for more than one OAUTH account. Closing this as a dupe of https://github.com/jobisoft/TbSync/issues/713