Re: Nightmare with inbox case (Inbox / INBOX)

[Josh B. <jo...@be...>]

On Mon, Mar 06 2017, 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)
>   * 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)

When syncing from outlook.office365.com, I have had similar sounding issues (tags, resets).  I have not debugged in a while, but some months ago I got suspicious that the exchange server was fumbling buffers.  I now use:

PipelineDepth 1

in .mbsyncrc and this seems to have cleared up the problems.  This is suboptimal since it makes accessing outlook even slower, but oh well...

Also, in the past I have had trouble syncing some meeting invitation/etc messages, perhaps excluding them is something to try.

FWIW I'm syncing to a local Maildir.

- Josh

> I'm close of having my sync working perfectly, but I don't know how to 
> sort problems related to some emails, any hints ?
>
> Regards
>
> Le 17/02/2017 à 23:08, Oswald Buddenhagen a écrit :
>> On Fri, Feb 17, 2017 at 11:03:19AM +0100, Florian Lombard wrote:
>>> Gmail side, they are either Inbox/subfolder or INBOX/subfolder
>>> I found what was the root cause of that: subfolders created with
>>> thunderbird use INBOX, subfolders created with outlook 2016 use Inbox
>>>
>> accoring to the imap spec, differing capitalizations of INBOX are
>> irrelevant - it's always the same box.
>>
>> however, now that i think of it, mbsync is broken in this regard (it
>> fails to make the pattern matching case insensitive). i should fix that.
>>
>> if you're in a hurry, we're in workaround land now.
>> i think you can script it: first use mbsync -l to get a list of folders,
>> and have the script generate a list of actual channels from that
>> according to your mapping rules, and bind them in a group. then run the
>> actual sync.
>> this should be particularly feasible if this is a one-off migration.
>>
>>> Can I change the patterns of the base channel to stop ignoring INBOX/*
>>> and Inbox/* , ignore the warnings but will not this results in double
>>> transfer of the mails in those subfolders ?
>>>
>> double transfer seems likely, but i didn't think too much about it. i'm
>> pretty sure nothing good will come out of it.
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>> _______________________________________________
>> isync-devel mailing list
>> isy...@li...
>> https://lists.sourceforge.net/lists/listinfo/isync-devel
>
> ------------------------------------------------------------------------------
> 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
> isy...@li...
> https://lists.sourceforge.net/lists/listinfo/isync-devel