no quick syncs
d.t.k at gmx.de
Mon Apr 11 23:54:44 BST 2011
Excerpts from Sebastian Spaeth's message of Mon Apr 11 18:41:51 +0200 2011:
> On Mon, 11 Apr 2011 10:33:21 +0200, dtk <d.t.k at gmx.de> wrote:
> > 'daemon mode' right now, but quick syncs don't work.
> > in my config, and the autorefresh setting works as expected, the IMAP server
> > being checked for new mail every 300 seconds. But if I receive new mail in
> > between, it isn't detected until the next 'major' check.
> That is bad.
> I certainly get new mail with it (not daemon mode
hmm, by daemon mode you too mean specifying autorefresh so offlineimap doesn't
exit after the first sync? In that case I don't think I understand how
quicksyncs behave in your case.
> I set my quick setting to -1 in .offlineimaprc..., I would
> never get new mail otherwise.
why is that? doesn't -1 make all syncs quick ones? k, maybe not if not in daemon
> Is that IMAP<->IMAP? Or IMAP<->Maildir ?
> We would need to debug offlineimap/folder/IMAP.py:quickchanged() which
> determines whether to skip a check. There are currently no debug outputs
> in that function...
k, actually I misread the documentation :/ I'm sorry :( I thought
# You can tell offlineimap to do a number of quicker synchronizations
# between full updates.
meant actually *between* full syncs, where when full syncs would take place was
configured via autorefresh. I expected configuring
autorefresh = 5
quick = 10
would full sync to take place every 5 * 60 = 300 seconds, with quick syncs being
triggered every 300 / 10 = 30 seconds. Stupid me *duh*
Only when debugging sync() (thanks for the hint, Sebastian), I realized that
quick specifies how many quick syncs are performed before another full sync is
done, syncs independent of type still _only_ being done every <autorefresh>
autorefresh = 0.5
quick = 10
nets me 1 full sync, 10 quick syncs after 30 seconds each, before after 5.5
minutes another full sync is performed. FTR -.-
sorry for the false alarm :/
More information about the OfflineIMAP-project