On Sun, Apr 01, 2018 at 05:02:38PM -0600, stef204 wrote: > Step 0) What I have done so far is to Pull from Master (remote) to Slave > (local) all of the emails. So I have them locally. > Please see Step 0 in my config posted below. > > Step 1) I now need to delete from the server ALL of these emails from the > Master--as of today; in order to create an extra 20 GB's of available storage > space. > > * Bulk deleting 100k email messages: > I do not think it is a good idea for me to try to use mbsync to delete these > on Master. But perhaps it is the best way? > > What I plan to do, unless someone here has a better idea. is to SSH > into server and just use "rm -f *" inside of "Inbox/cur" for the email > account (Master). I am not sure how mbsync will then "see" these > changes. It seems to depend on the value set for "Sync" inside config > file. > 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*.
> Step 2) Once all emails have been deleted from Master, as of tomorrow, start > again syncing with mbsync in such a way that a) no local emails pulled from > Master (in Step 0 above) but then deleted from server (Step1) ever get > removed (marked as deleted or even worse, expunged) from Slave (or local). > > Additionally, all new emails received on Master from tomorrow (after the > deletion in Step1) should again sync "normally" especially if I delete one > manually with a regular IMAP4 MUA (which would not be using the local cache > of emails since I have to read emails from various locations) and which would > need to be deleted in Slave (local). > > Config used for Step 0, then no idea for Step 1 (but will probably use a > different method unless suggested I still use mbsync for bul deletion) and > what I have tested for Step 2). I am really not sure the Step 2 config best > suita my objective.... > > Any help, feedback would be appreciated. > 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. ------------------------------------------------------------------------------ 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
