Re: cone's beginner: some questions

Sam Varshavchik <[email protected]>
Newsgroups gmane.mail.cone
Message-ID <[email protected]>
Elisa Manara writes:

> Sam Varshavchik writes:
> 
>> Nope.  By definition, the number of messages in a top-level folder always 
>> gets updated.  If the server can't quickly count the number of messages in a 
>> folder then you'll just have to keep the number of top-level folders at a 
>> minimum.
> 
> I have about 15 top-level folders, and they are local mbox files, filled by 
> procmail. Cone locks when it performs open() and read() on these local 
> folders, so often.

The only way to count the number of messages in an mbox file is to read it 
in its entirety.

>                    Maybe I did not undertand so good the difference between 
> top-level and "normal" folders. Certainly top-level folders get always 
> updated, this is what I want: I ness to know which folder has received new 
> emails.

Well, that's what you got.  It is well known that large mbox folders have a 
severe performance penalty.  The only difference between top level folders 
and regular folders is that the top level folders are immediately 
accessible, and that their status is frequently updated.

>         Anyway, how handles Cone "normal" folders? I just tried to append 
> some mail to an existing folder but strace shows me only stat() calls (i.e. 
> no open() and read() for updating), in fact I don't see any changes as 
> regards to the folder content (number of messages, number of unread 
> messages). In short, how can I configure Cone to keep my folders always 
> updated, without locking so often?

mbox folders require locking.

You should switch to maildirs.
signature.asc (application/pgp-signature, 189 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD4DBQBAuz6Vx9p3GYHlUOIRAoV2AJURUErWnNr57EeK/b+EjUGfNWOFAJ95NYRW
g88q9+S1KtNeRRFURW4yxQ==
=OhyW
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.