Tomas Nordin <tom...@posteo.net> writes: > Oswald Buddenhagen <oswald.buddenha...@gmx.de> writes: > >> On Sat, Nov 25, 2023 at 01:02:43PM +0000, Tomas Nordin wrote: >>>Does it confirm any suspicions maybe? >>> >> yes. you need to try GSSAPI, and if that still doesn't work, PLAIN. > > I am getting somewhere with PLAIN (AuthMechs PLAIN under > IMAPAccount). But I am getting warnings as this > > C: 0/1 B: 0/2 F: +0/0 *0/0 #0/0 N: +0/0 *0/0 #0/0 > Warning: lost track of 4457 pulled message(s) > Warning: lost track of 213 pushed message(s) > C: 0/1 B: 0/2 F: +4/213 *0/0 #0/0 N: +0/4457 *0/0 #0/0 > IMAP error: unexpected tag .wrap > C: 1/1 B: 1/2 F: +4/213 *0/0 #0/0 N: +0/4457 *0/0 #0/0 > > and I sort of forgot that I first tried this with offlineimap. Would it > be safe to erase the content of the relevant maildir folders and start > anew with mbsync. (Thinking there is some confusions between the ways > the two syncers name the files...). With safe I mean I dont want > everything to get deleted on the server side.
I was restless to get this done, it seems now obvious that yes, one can restart everything. I removed the cur new tmp .mbsyncstate.journal .mbsyncstate.new .uidvalidity directories and files from the folders. I tried to make sure not to change anything on the server side with the following configuration options under Channel Create Near Expunge None Sync Pull I got a number of errors like this IMAP command 'UID FETCH 323 (INTERNALDATE BODY.PEEK[])' returned an error: UID FETCH 323 (INTERNALDATE BODY.PEEK[]) but it was just to rerun mbsync until silent and all mail was retrieved. I have now configured it back so I can delete mail on the far side. All is good. Thanks for all work on this program. Have a nice evening -- Tomas _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel