Re: Issue with Office365

2024-08-15 Thread Marton Balazs
Ok, sorry and thanks. Best wishes, Marton On Thu, Aug 15, 2024 at 09:15:48PM GMT, Oswald Buddenhagen via isync-devel wrote: > On Thu, Aug 15, 2024 at 08:15:34AM -0400, Laurent Michel wrote: > > Gotcha. Though, I must say I did not have a “.mbsync” folder. That > > is still mysterious to me (I co

Re: Issue with Office365

2024-08-15 Thread Oswald Buddenhagen via isync-devel
On Thu, Aug 15, 2024 at 08:15:34AM -0400, Laurent Michel wrote: Gotcha. Though, I must say I did not have a “.mbsync” folder. That is still mysterious to me (I compilde isync from the git repo directly, main branch). git master since two years (and now 1.5.0) defaults to $XDG_STATE_HOME/isync/

Re: Issue with Office365

2024-08-15 Thread Marton Balazs
Date: Wed, 14 Aug 2024 23:10:57 +0100 > From: Marton Balazs balm...@gmail.com > To: Laurent Michel l...@thorgal.homelinux.org > Subject: Re: Issue with Office365 > > Do you have > ~/.mbsync/ ? > > My

Re: Issue with Office365

2024-08-15 Thread Laurent Michel
2024 23:10:57 +0100 From: Marton Balazs balm...@gmail.com To: Laurent Michel l...@thorgal.homelinux.org Subject: Re: Issue with Office365 Do you have ~/.mbsync/ ? My .mbsyncrc starts with SyncState * meaning the sync state files .mbsyncstate are in the local maildir folders. Without this it

Re: Issue with Office365

2024-08-14 Thread Marton Balazs
24, at 18:12, Marton Balazs wrote: > > ooops, forgot to cc the List :-) > > - Forwarded message from Marton Balazs balm...@gmail.com - > > Date: Wed, 14 Aug 2024 23:10:57 +0100 > From: Marton Balazs balm...@gmail.com > To: Laurent Michel l...@thorgal.homelinux.org >

Re: Issue with Office365

2024-08-14 Thread Laurent Michel
Thanks. I tried a few things based on your email. First I do not have any file anywhere going by the name “.mbsyncstate” ``` ldm@pildm:~ $ find . -name ".mbsyncstate" ldm@pildm:~ $ ``` I changed my mbsyncrc as you suggested to ``` IMAPAccount work Host outlook.office365.com User ….. PassCmd

Re: Issue with Office365

2024-08-14 Thread Laurent Michel
woods! — Laurent On 14 Aug 2024, at 18:12, Marton Balazs wrote: ooops, forgot to cc the List :-) - Forwarded message from Marton Balazs - Date: Wed, 14 Aug 2024 23:10:57 +0100 From: Marton Balazs To: Laurent Michel Subject: Re: Issue with Office365 Do you have ~/.mbsync/ ? My

Fwd: Re: Issue with Office365

2024-08-14 Thread Marton Balazs
ooops, forgot to cc the List :-) - Forwarded message from Marton Balazs - Date: Wed, 14 Aug 2024 23:10:57 +0100 From: Marton Balazs To: Laurent Michel Subject: Re: Issue with Office365 Do you have ~/.mbsync/ ? My .mbsyncrc starts with SyncState * meaning the sync state files

Re: Issue with Office365

2024-08-14 Thread Marton Balazs
As far as I understand, every now and then MS screws up UidValidity, which it really shouldn't do -- but it's MS. On these occasions Mbsync usually recovers most of my folders from this but on a few I get the error you mentioned. I then create an empty directory and pull all of my folders from M

Issue with Office365

2024-08-14 Thread Laurent Michel
Dear All, I had isync running flawlessly for a few years with OAUTH2. Recently, it seems like my organization must have done an “upgrade” to Office365. And now, everything is broken on my end. Specifically, each sync end as so: ``` ldm@pildm:~ $ mbsync -aV Reading configuration file /home/ld