From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,BAYES_00 shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id 8BD921F55B; Thu, 4 Jun 2020 08:57:23 +0000 (UTC) Date: Thu, 4 Jun 2020 08:57:23 +0000 From: Eric Wong To: meta@public-inbox.org Subject: Re: MUA and client-side limits w.r.t. IMAP Message-ID: <20200604085723.GA11779@dcvr> References: <20200519090000.GA24273@dcvr> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20200519090000.GA24273@dcvr> List-Id: Eric Wong 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...