Le 07/03/2017 à 10:23, Oswald Buddenhagen a écrit : > On Mon, Mar 06, 2017 at 05:10:45PM +0100, Florian Lombard wrote: >> I've ended up with a python script creating the config files with the >> correct mappings (whatever Inbox google side and always INBOX outlook side) >> >> This part is now working ;) >> >> I'm still facing a few problems : >> >> * Mbsync tries to select folders with /NoSelect flags on the google >> side (those are folders with only subfolders in them, no message) >> > i just tried that with gmail, and the only folder marked that way is > [Gmail], for which the exclusion definitely works here. > 'mbsync -Dn -l <channelname>' should give a clue. > > my work account has an intermediate folder in the hierarchy, and it > cannot be manually marked as \noselect, so i use this config: > Patterns INBOX* !INBOX/lists Unfortunately, I can't do that, that will exclude the subfolders of this folder Anyway, it's not a big deal, it's not stopping sync of the mailbox >> * unexpected tag errors (always on the same mailboxes) >> * connection reset by peer (outlook side), I thought it was only after >> 10 imap commands errors that outlook was disconnecting clients. I >> suspect that this happens after the same messages, I need to -DN >> those boxes to be sure >> * some mails are refused by outlook (without explanations, would be >> too easy) >> > these all sound like Business As Usual (TM) with outlook. That's what's scarying me :( Random errors went away with the Pipeline set to 1 >> I'm close of having my sync working perfectly, but I don't know how to >> sort problems related to some emails, any hints ? >> > if it really can be nailed to specific mails, -DN (with the 1.2 branch > from git) is the way to go. note: incredible amounts of data, highly > privacy-relevant. try -Dn first, that's only the imap protocol log and > includes only message sizes. > > one thing i already know is that mails which are considered too big > cause a BAD response from outlook (which is just stupid; it should be > NO). MaxSize will prevent this, obviously at the cost of an incomplete > sync (but you really have no choice in this case unless you control the > receiving server's limits). Yeah I just noticed that from a HUGE -DN log BAD error after a 21 MB mail (which is strange, default message limit of office 365 is 25 MB I've set mail limit to 50 MB and sync is in progress, I'll notify of the results
I'm so happy that neither gmail nor outlook.com are in full compliance of the IMAP specs ... ------------------------------------------------------------------------------ Announcing the Oxford Dictionaries API! The API offers world-renowned dictionary content that is easy and intuitive to access. Sign up for an account today to start using our lexical data to power your apps and projects. Get started today and enter our developer competition. http://sdm.link/oxford _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
