On Fri, Nov 14, 2025 at 06:20:52AM +0100, Peter P. wrote: > Hi list, > > reviving an older thread here, I am still looking for a solution to the > problem of my employer wanting to move all email in my account older than X > years from all folders and host it on a separate webservice[1], thus > making it inaccessible to me from isync/mutt/notmuch etc. > The employer is trying to save storage and server ressources this way > and this questionable move is unavoidable for me. > > Denial Tamling has suggested using tools from the mblaze package to filter > mail older than a certain date, with Oswald pointing out a pitfall when > moving these messages, which I don't yet understand: > > * Oswald Buddenhagen via isync-devel <[email protected]> > [2025-07-18 09:02]: > > On Thu, Jul 17, 2025 at 10:33:36PM +0200, Daniel Tameling wrote: > > > mv $(mlist ./INBOX | mpick -t 'from =~ "@github"') ./github/cur > > > > > this will preserve the ,U=nnn infixes of the files, which is a very bad > > idea. > > Is there a correct way to move all mail from all folders older than X to > some other folder? > > I am wondering if mblaze/mlist is nevertheless the best way I can > anticipate the forced archival.
I'd guess that using mrefile(1) should do it the correct way. > If I would manage to hereby extract all old email from all far-side > folders I would then need to store it to a near-side folder that is not > synced back to the far side. How could I nevertheless keep that > near-side folder in sync across multiple computers? By using another IMAP server - which is probably against some rules about corporate stuff. > Is there any other way to work around this imminent problem? As long as you are not deleting anything from the archive, as emails are just text and files, any method to sync text and files should do. _______________________________________________ isync-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/isync-devel
