From: "Fco. J. Ballesteros" <nemo@lsub.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] acme mail "feature"
Date: Fri, 1 Oct 2004 16:56:49 +0200 [thread overview]
Message-ID: <bbe20a8236404c974b9c3d4895a02874@plan9.escet.urjc.es> (raw)
In-Reply-To: <14096ba5db5eb3013ad32ee1a3efa237@coraid.com>
[-- Attachment #1: Type: text/plain, Size: 517 bytes --]
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.
[-- Attachment #2: Type: message/rfc822, Size: 2645 bytes --]
From: Brantley Coile <brantley@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] acme mail "feature"
Date: Fri, 1 Oct 2004 10:49:02 -0400
Message-ID: <14096ba5db5eb3013ad32ee1a3efa237@coraid.com>
> 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!!
next prev parent reply other threads:[~2004-10-01 14:56 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-01 14:03 Sam
2004-10-01 13:19 ` rog
2004-10-01 13:56 ` andrey mirtchovski
2004-10-01 14:45 ` rog
2004-10-01 14:42 ` Fco. J. Ballesteros
2004-10-01 14:51 ` Axel Belinfante
2004-10-01 14:58 ` Fco. J. Ballesteros
2004-10-01 15:18 ` boyd, rounin
2004-10-01 16:27 ` C H Forsyth
2004-10-02 22:28 ` Skip Tavakkolian
2004-10-02 22:55 ` George Michaelson
2004-10-02 23:22 ` andrey mirtchovski
2004-10-01 14:54 ` rog
2004-10-01 16:59 ` Richard Miller
2004-10-01 15:01 ` Russ Cox
2004-10-01 14:49 ` Brantley Coile
2004-10-01 14:56 ` Axel Belinfante
2004-10-01 14:56 ` Fco. J. Ballesteros [this message]
2004-10-01 14:59 ` Brantley Coile
2004-10-01 15:07 ` Fco. J. Ballesteros
2004-10-01 15:16 ` rog
2004-10-01 15:24 ` boyd, rounin
2004-10-04 12:33 Caerwyn B Jones
2004-10-04 12:39 ` Russ Cox
2004-10-04 14:13 Caerwyn B Jones
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bbe20a8236404c974b9c3d4895a02874@plan9.escet.urjc.es \
--to=nemo@lsub.org \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).