On Mon, Apr 02, 2018 at 05:27:31AM -0600, stef204 wrote:
> 02.04.2018, 03:54, "Oswald Buddenhagen" <oswald.buddenha...@gmx.de>:
> > these would be just deletions from the perspective of mbsync, which it
> > would propagate to the slave. unless you exclude propagation of
> > deletions in that direction *permanently*.
>
> I am curious as to how to actually do that, I do not see the option on the
> man pages.
>
> I see: Sync {None|[Pull] [Push] [New] [ReNew] [Delete] [Flags]|All}
> But no way to turn OFF the "Delete".
>
other than overriding the default, this option is *additive*, so you
"turn off" the irrelevant parts by simply omitting them.
you probably want Sync PullNew Push.
> > i would recommend moving (== copy + delete source) the archive on
> > the slave to a separate folder (which is simply not synced), and
> > then just letting mbsync propagate the deletions of the obsolete
> > mails to the master.
>
> You are suggesting to not use the method SSH into server and use "rm
> -f" in Inbox/cur but to move the existing local archive to a new local
> folder and just keep it there for reference (no further syncing.)
>
correct.
> Then create a new slave (empty) and use mbsync to Sync, using "Sync
> All" (the default) to propagate the changes (thus the huge deletion on
> server?)
>
no. just use
Patterns !Archive *
in the config you already have.
------------------------------------------------------------------------------
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
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel
