On Wed, Oct 10, 2012 at 12:39:57PM +0300, Ciprian Dorin Craciun wrote: > On Wed, Oct 10, 2012 at 10:43 AM, Oswald Buddenhagen <o...@kde.org> wrote: > > doesn't > > mbsync --pull-new --push > > do more or less what you want? > > I think I've tried that and I think it still tries to "stat" all > the emails... I'm 60% sure, I'll try it again. > hmpf. this sounds a bit like a bug. the mbsync -V output would tell.
> > you may also consider using MaxMessages unless you actually *need* all > > those mails on the client side. > > I would use it, but unfortunately it doesn't have quite the semantic I > need: > * from the documentation it seems that it both downloads the last > emails, but also deletes from my slave store all the other emails; > * I do need to download only the last emails, but I would like the > store to also keep all the "unwanted" emails; > so far that matches PullNew: only download new mails and don't do anything else. > As such maybe MaxMessages should have two values: > * how many emails to fetch from the past; > this is no useful criterion. how do you define "past"? seen? read? date? how does this relate to the propagation of changes (for you it's pretty much only the "read" and "flagged" flags, as you never delete anything)? > * how many emails to keep in the store; > (0 means infinity for both as is now;) > ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
