Re: Re: Reducing KODRETRY

Mats Dufberg <[email protected]>
Newsgroups gmane.mail.pine.general
Message-ID <[email protected]>
On Dec 22, 2006, 15:16 (-0800) Joseph Tam <[email protected]> wrote:

> > >I'd suggest using the 'mbx' format on the server; I did
> > >the switch and ever since, I can have 2 or even 3 pines
> > >accessing the same folders simultaneously. Of course, I
> > >don't know if you can change that.
> 
> (Adressing Thorsten) I'll take your word for it that it would solve the
> problem, but converting hundreds of my user mailbox formats just to solve
> this one problem is using a case of sledgehammer killing flies.  If I had
> to change formats, I would Maildir instead.

The most important mailbox to convert is the inbox. There is no problem to 
mix the two formats. Converting to mbx format relly improves performance. 
It is also quicker.


> > I have no idea what the format on the server is -- I use IMAP, and it works
> > fine with multiple clients simultaneously..  But I thought you were
> > using IMAP too, so I guess I don't quite see what's causing the timeout.

It depends on the server and server configuration. If you set a UW-IMAP 
up, then you should use MBX for best performance.


> I am using Unix mbox format.  That was my concern: if I lower KODRETRY,
> I would break something else.  I did remake libc-client.so and included it
> in my personal LD_LIBRARY_PATH, and it seems to work: it shortens the lock
> bailout time to something bearable.

Well, with MBX you can keep multiple pine sessions open.



Mats

-----------------------------------------------------------------
Mats Dufberg                                      [email protected]
Blaoarvsgraend 42                                  +46-8-38 48 59
SE-162 45 Vaellingby, Sweden                      +46-70-258 2588
_______________________________________________
Pine-info mailing list
[email protected]
http://mailman1.u.washington.edu/mailman/listinfo/pine-info
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.