Re: handling very large mailboxes
- To: mutt-users@xxxxxxxx
- Subject: Re: handling very large mailboxes
- From: James <jtp@xxxxxxxxx>
- Date: Sun, 31 May 2009 10:24:07 -0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:from:date:x-google-sender-auth:message-id:subject:to :content-type:content-transfer-encoding; bh=F3tyRP1xWV1EQgBQf7XJSmJhbK4SGmITaeRXrieC/kI=; b=W3lFCFpoU8ERbHwEDMKDpNtQnKPTBs0PeKKpcjQ2/8RcoOquQfqpmySYiHrvIwNkPh Wj99DfTG+HdNCZ4deDRiESNZvdk9fDO3TF6X51aGIrokAyyelaSOhmsmnyK43aDuXO07 AQ0NRGt2ItnZS0PiByVauVn+jVj5MQtv7bBgc=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type :content-transfer-encoding; b=Aphz9F7zONbWz2rDo7S31TIY5+UrLpp67H9J31p6OEm1IlcF4bh1MBjR7HhYXmuT0P u1LCL/QnCe6riMiRuuYWauamJUIsg1B6TRHpFVfBMTamrQlNb9qQR0NTReQx8K7fpOw8 z4vsob3GL4DVF7jAbvEEd85OruODQ9MvZP4To=
- In-reply-to: <20090531141527.GD8209@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- List-post: <mailto:mutt-users@mutt.org>
- List-unsubscribe: send mail to majordomo@mutt.org, body only "unsubscribe mutt-users"
- References: <e107b4ff0905310651w24858feam1950461f5af564b7@xxxxxxxxxxxxxx> <20090531141527.GD8209@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Sender: owner-mutt-users@xxxxxxxx
On Sun, May 31, 2009 at 10:15 AM, Rocco Rutte <pdmef@xxxxxxx> wrote:
> Hi,
>
> * James wrote:
>
>> I use procmail + mutt and am running into a problem that is limiting
>> my usage of mutt. Currently procmail sorts some very high volume
>> mailing lists into specific folders (mbox format). I'm using mutt as
>> an IMAP client and when I add these mailboxes to my .muttrc file, mutt
>> sometimes takes 5 to 10 minutes to fully load and sort all the
>> messages.
>
> Did you turn on header caching? Are you sure this isn't a network
> problem? What version of mutt? What is large, btw?
I definitely have header caching. I'm fairly certain I have body
caching as well.
The network is definitely not a problem...v1.5.16.
By large I'm talking about, uhhh, ~7000 emails. More or less.
>> Worse, when the timer expires and mutt begins checking mailboxes for
>> new messages, the client freezes until the check is done.
>
> How long does that take? Mutt doesn't do anything in this case except
> asking the IMAP server for mailbox status. Maybe the server needs a long
> time to answer for huge folders? If yes, then mutt can't do anything
> about it. You need to raise $mail_check then to make it check less
> often.
So you're saying that after mutt initially starts, downloads all the
emails and the initial sorting is done, It'll only check every
$mail_check period to see if there are new messages *without*
re-downloading the entire content of the mailboxes?
>> Is there a way to "thread" or "background" the mail checking process
>> in mutt so that I don't have to deal with this problem?
>
> No, not really, sorry.
>
> Rocco
>