If I'm not explicitly calling a channel, wouldn't that section be ignored ?

The command I run to sync is: mbsync O365-all (no other options/channels)

The only time I run mbsync against any of the other channels is when I need
to re-sync the Archive.

Your point about using groups instead of channels for the -all is well
taken. Thanks. I'll make that change and I'll comment out the rest of the
channels just to be sure.

As for SyncState * this is in the config, just not under each channel. It
was my understanding that having these options outside a channel definition
would make it "global". Is my understanding incorrect? Here is that section
again (it was in my previous email too):

SyncState *
Sync All
Expunge Both

Also, I don't have MaxMessages defined AFAIK. Is there any other place this
could be set? What is the default value for this?

Thanks

On Wed, Feb 12, 2020 at 5:52 AM Oswald Buddenhagen <
oswald.buddenha...@gmx.de> wrote:

> On Tue, Feb 11, 2020 at 05:34:06PM -0500, Andy W wrote:
> >Channel O365-trash
> >        Master :O365-remote:"Deleted Items"
> >        Slave  :O365-local:"Trash"
> >
> >Channel O365-all
> >        Master :O365-remote:
> >        Slave  :O365-local:
> >        Patterns INBOX Archive Drafts Sent Junk Sent Trash
> >
> this cannot possibly go well - you have two conflicting definitions for
> the server side of Trash.
> even apart from this mistake, having multiple channels refer to the same
> boxes is a bad idea, and without SyncState * it would be actually
> disastrous. you should make the -all channel a group instead.
>
> i see nothing wrong with the Archive channel in particular, and i don't
> understand how messages can simply disappear on the slave without the
> deletions being propagated to the master. this is something the
> MaxMessages expiration feature would do, but the config you posted has
> no mention of it. maybe there is a forgotten instance somewhere in the
> background?
>
>
> _______________________________________________
> isync-devel mailing list
> isync-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/isync-devel
>
_______________________________________________
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Reply via email to