From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: From: "Fco. J. Ballesteros" Date: Fri, 1 Oct 2004 16:56:49 +0200 To: 9fans@cse.psu.edu Subject: Re: [9fans] acme mail "feature" In-Reply-To: <14096ba5db5eb3013ad32ee1a3efa237@coraid.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-tuszynatokixmbcdoyskfogvgf" Topicbox-Message-UUID: eb78c2ee-eacd-11e9-9e20-41e7f4b1d025 This is a multi-part message in MIME format. --upas-tuszynatokixmbcdoyskfogvgf Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit I think upas/fs wont read messages before it's needed when using imap. At least, I remember changing it do work that way (Hmm, I think it required also a change in acme Mail, but I'm not sure). It's loooong since I used that feature for the last time, so I'm not sure about what's upas/fs doing. Also, IIRC, you have to read all the messages if you're using pop instead of imap. Once the message is here, reading it into ram is not a serious problem unless you keep many many messages or very big ones. --upas-tuszynatokixmbcdoyskfogvgf Content-Type: message/rfc822 Content-Disposition: inline X-Leches: 0 Received: from mail.cse.psu.edu ([130.203.4.6]) by aquamar; Fri Oct 1 16:52:12 MDT 2004 Received: from psuvax1.cse.psu.edu (localhost [127.0.0.1]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 20CBC183D3 for ; Fri, 1 Oct 2004 10:52:11 -0400 (EDT) X-Original-To: 9fans@cse.psu.edu Delivered-To: 9fans@cse.psu.edu Received: from localhost (localhost [127.0.0.1]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 7B1F1183C6 for <9fans@cse.psu.edu>; Fri, 1 Oct 2004 10:51:39 -0400 (EDT) Received: from mail.cse.psu.edu ([127.0.0.1]) by localhost (psuvax1 [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 17826-01-57 for <9fans@cse.psu.edu>; Fri, 1 Oct 2004 10:51:38 -0400 (EDT) Received: from coraid.com (ns1.coraid.com [65.14.39.133]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 3034C183DF for <9fans@cse.psu.edu>; Fri, 1 Oct 2004 10:51:38 -0400 (EDT) Message-ID: <14096ba5db5eb3013ad32ee1a3efa237@coraid.com> To: 9fans@cse.psu.edu Subject: Re: [9fans] acme mail "feature" From: Brantley Coile Date: Fri, 1 Oct 2004 10:49:02 -0400 In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at cse.psu.edu X-BeenThere: 9fans@cse.psu.edu X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: 9fans-bounces+nemo=lsub.org@cse.psu.edu Errors-To: 9fans-bounces+nemo=lsub.org@cse.psu.edu > but the thing that most needs fixing (for my usage pattern anyway) is > the way that upas/fs reads the entire mailbox into RAM. i get around > this by periodically archiving my mailbox, deleting all but the most > recent 6 month's worth of messages, but i'd prefer not to do this. I agree. I have a user who accesses his mail box from pop and keeps all the mail on the server. He has run up pretty large mail boxes in the past. > > all that said, i think the combination of acme mail and upas/fs > is excellent, and i wouldn't use anything else! Here, here!! --upas-tuszynatokixmbcdoyskfogvgf--