MUA and client-side limits w.r.t. IMAP

MUA and client-side limits w.r.t. IMAP

[Eric Wong]

TL;DR: is 50K messages a reasonable IMAP folder size?

So far, the IMAP daemon code shares quite a bit of data and
logic with the NNTP code.  NNTP article numbers are reusable as
IMAP UIDs; and for small inboxes, newsgroups can be an IMAP
folder.  But that only works for small inboxes...

One major difference between IMAP and NNTP is every NNTP client
I've looked at (even going back to the 90s) has default limits
on the number of messages it can fetch for a newsgroup.

I'm not sure if any IMAP client has NNTP-like limits by default.
Instead, they'll attempt to fetch headers for every single
message in that IMAP folder.

Bigger public-inboxes have 300-400K of messages per epoch.  I
don't think most MUAs will be happy with even that, not to
mention monster multi-epoch inboxes like LKML.

So I'm thinking 10K-60K is more reasonable these days, at least
on the hardware I have and TokyoCabinet header caching in mutt.
10K is a pretty small window for lists like LKML; and 50K only
takes a few seconds for my old Centrino laptop over IMAP.

All messages can still be exposed via extra folders with numbers
tacked on:

* default, same as newsgroup name, messages "expire"
inbox.comp.version-control.git           =>    most recent 50K messages

* messages never expire from these IMAP folders:
inbox.comp.version-control.git.400000    =>    350,001..400K
inbox.comp.version-control.git.350000    =>    300,001..350K
inbox.comp.version-control.git.300000    =>    250,001..300K
...

I don't want to expose a configuration knob, here; since
users can get thrown off and have to resync if the admin
changes the window size.

I don't know about MUAs other than mutt; but is 50K a reasonable
folder size?

Also, IMAP search may be able to cross into the older ranges,
not sure, yet...

Re: MUA and client-side limits w.r.t. IMAP

[Eric Wong]

Eric Wong <e@yhbt.net> wrote:
> * default, same as newsgroup name, messages "expire"
> inbox.comp.version-control.git           =>    most recent 50K messages

I think that's best left an empty parent folder, since having
the most recent X messages means the client will have to
refetch/resync that entire 50K again when a new
numerically-suffixed mailbox is needed to hold older messages.

> * messages never expire from these IMAP folders:
> inbox.comp.version-control.git.400000    =>    350,001..400K
> inbox.comp.version-control.git.350000    =>    300,001..350K
> inbox.comp.version-control.git.300000    =>    250,001..300K
> ...

Now, I'm thinking more along the lines of:

inbox.comp.version-control.git.7    =>    350,001..400K
inbox.comp.version-control.git.6    =>    300,001..350K
inbox.comp.version-control.git.5    =>    250,001..300K
inbox.comp.version-control.git.4    =>    200,001..250K
inbox.comp.version-control.git.3    =>    150,001..200K
inbox.comp.version-control.git.2    =>    100,001..150K
inbox.comp.version-control.git.1    =>     50,001..100K
inbox.comp.version-control.git.0    =>          1..50K

Since bigger numbers are harder-to-read and memorize.
But LKML is currently up to 72...