On Mon, Nov 4, 2013 at 6:00 PM, Oswald Buddenhagen <[email protected]> wrote: > On Mon, Nov 04, 2013 at 02:17:15PM -0600, Felipe Contreras wrote: >> On Mon, Nov 4, 2013 at 1:55 PM, Oswald Buddenhagen <[email protected]> wrote: >> > On Mon, Nov 04, 2013 at 12:36:11PM -0600, Felipe Contreras wrote: >> >> I'm giving this a try, and so far it does indeed work, but only for >> >> some folders. It seems to me that the folders that fail are the ones >> >> that have older messages. >> >> >> > can you describe that more precisely? >> > could it be that you are not auto-marking unread messages as non-recent >> > ("old")? mbsync preserves such messages. >> >> I don't understand what you mean. >> > there are three levels of "noticing" messages: "read", "seen" ("old", > seen them in the mail index), and "recent" ("new", don't know about > their existence). undownloaded unread messages are assumed to be recent, > because there is no reliable way to tell differently.
Yes, I'm not auto-marking them as "seen". I guess mutt does that, but I don't think the Gmail web interface has any notion of that concept. > it would be conceivable to add a mode where the local recency status is > ignored, so messages cannot be expired just because you opened the > mailbox. I don't know what expiring means. I just think there should be a way to specify the maximum amount of messages to sync. In fact, I would prefer it to be the maximum age, like in offlineimap, so I can say: sync only the last month. If a folder has a lot of traffic like LKML, and another has very low one I might be getting up to 6 months in one, and a couple of days in another with MaxMessages. >> I heave unread messages, yes tons of them some very old, why would >> that matter for MaxMessages? >> > the algorithm never expires recent messages. > >> Also, this is the first fetch, what do you mean by "preserve"? >> > unread undownloaded messages are assumed to be recent, so consistently > with the non-expiration they are also always downloaded. > > the assumption is that you wouldn't want to miss lots of messages just > because you haven't been reading mail for a while. I have a folder with 120,000 unread messages, if I try to first fetch with MaxMessages 100, I would get 120,000 messages. That's quite a delta from what I requested. Why can't MaxMessages mean the maximum amount of messages, period? > it would be conceivable to add modes with lower levels of safety, which > could be useful for "optional" mailboxes. option UnseenMessages: > - Fetch: the current behavior. makes sure you miss no message. > - Keep: keep already downloaded recent messages, but don't always fetch > old unread ones. that means that the initial fetch will be (mostly *) > hard-limited, but the box will grow if you regularly sync but don't > even look at your mail. if you don't sync for longer than it takes to > fill the window, there will be a "hole". Longer than it takes to fill the window? Which window? >> > what is the use case? >> >> As I have said before; I don't want to download tens of thousands of >> messages. >> > that's obvious. that's what MaxMessages is all about. MaxMessages is also about not having more than a certain amount stored. Which is something I don't particularly care about, but could live with it for the moment I guess. >> Suppose I have mailbox with 10000 messages. >> [...] >> And maybe even this: >> 1) First fetch CutMessages=1000, I get the last 1000 messages >> 2) CutMessages=2000, now I get the last 2000 messages >> 3) Subsequent fetches get the new messages after that, say over one >> month 1000 new messages more >> >> I have now 3000 messages locally. >> > i don't understand the point of that. it seems arbitrary to limit the > initial fetch to a smaller number of messages than you want to keep > in the long run. The amount of messages that I want to keep is irrelevant, storage is cheap, and I have a good mail indexer. The important resource is the network bandwidth. The point is not to fetch 10,000 messages in one go. Say I want to reply to a mail I got yesterday, I may do MaxMessages 100 just to get it, and later on I want to download more, maybe 1,000. Then 2,000, eventually I may get them all, but the important thing is that it doesn't happen in one go and I can reply to the mail from yesterday, today. >> Currently: >> 1) First fetch MaxMessages=1000, I get the last 1000 messages >> 2) Subsequent fetches get the new messages after that, say over one >> month 1000 new messages more >> >> I have 1000 messages locally. >> > yes. what's wrong with that? That I may want to search for older messages. Why delete them if I already downloaded them? Storage is cheap. Cheers. -- Felipe Contreras ------------------------------------------------------------------------------ November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk _______________________________________________ isync-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/isync-devel
