isync/mbsync cannot connect to outlook.office365.com #5898
-
|
Under Ubuntu 20.04 LTS on WSL2, mbsync (provided by the isync package) cannot connect to outlook.office365.com. Specifically, running
with the skeleton ~/.mbsyncrc file:
in place yields the output:
Compiling isync-1.3.3 from source on Ubuntu 20.04 LTS/WSL2 yields the same behavior.
The above .mbsyncrc file contains no username or password lines because these are not necessary to expose a discrepancy between the expected and actual behavior. If I replace .mbsyncrc with my complete config file, I get the same output on Ubuntu/WSL2 as above and no files are transferred, whereas on other systems mbsync will successfully sync the files. A secondary issue is that it is not helpful for the only error message to be printed to be of the form "... : Success." That might well be a problem with mbsync itself. strace output attached (note: strace was run with 'Maildir-test' in place of 'Maildir' in the .mbsyncrc file since in the latter case the strace output exposes the names of all of my mail folders). Microsoft Windows [Version 10.0.19041.450] |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
|
Was able to sync my gmail (it's pulling down a decade of email in that screencap below).
All WSL sees is a tcpv4 socket on port 993. There is no real path to a WSL actionable here. Moving to discussion, |
Beta Was this translation helpful? Give feedback.
-
|
Thanks. mbsync works great for me on other systems --- it is only on WSL where I am having problems. That's why I posted here first. Granted, I don't have a standalone Ubuntu 20.04 system, so I can't do a head-to-head comparison. Perhaps this is an isync/ubuntu 20.04 issue that does not involve WSL. If I may ask: what happens if you run mbsync with the .mbsyncrc file I posted above? What Linux distribution and isync version are you using? |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
.mbsyncrc files are white-space sensitive and I messed up the white space in the original posting. It was supposed to be:
That fixes all of the "unknown keywords." Sorry about that. I just installed Ubuntu 18.04 on WSL2 and I can confirm that mbsync works as expected there. So I assume this is an issue with Ubuntu 20.04 and/or mbsync. I will open a ticket elsewhere and mark this as answered. Thanks for the help. |
Beta Was this translation helpful? Give feedback.
Was able to sync my gmail (it's pulling down a decade of email in that screencap below).
All WSL sees is a tcpv4 socket on port 993. There is no real path to a WSL actionable here. Moving to discussion,
but you'll almost certainly get better eyeballs on this submission in a place where isync people hang out.