Re: Problem using reconstruct

sfull. Best Regards Nicola Ranaldo --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: Problem using reconstruct

lidity number, some of my users (an entire university) have thousands of messages and, sorry, most of them use pop3, so a uidvalidity change will result in a redownload of all messages. IMHO the code to deal with different version of cyrus index file should be sharable, in libcyrus. Best Regard

Problem using reconstruct

ackup. Can you help me? Nicola Ranaldo --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Migrating from tru64 to linux

is avoided. So I'm looking for other solution. Did you have a similiar problem? thank you Nicola Ranaldo --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: reconstruct broken in cyrus-imapd-2.1.15 (2.2.3 too!)

The same problem is in 2.2.3 and is not fixed.. how is it possible?? bye Nicola Ranaldo - Original Message - From: "Rob Siemborski" <[EMAIL PROTECTED]> To: "Carsten Hoeger" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Wednesday,

Re: Problems with cyrus-imapd 2.1.11 under Solaris 8

I think master would check exit value of its childs and decrement the number of ready_workers. Regards Nicola Ranaldo > When some pop3d dies with signal (i.e. SIGTERM), all incoming > connections to corresponding address:port are hangs. For example, if I > have pop3d running on 19

Re: PostgreSQL backend: a waste of time?

ll my sendmail maps (Yes! also virtusertable!). And all these fields are trigger protected in the RDBMS solution. This gives more flexibility and integration in my informative service. I think I am not alone in this! Best Regards Nicola Ranaldo

Re: PostgreSQL backend: a waste of time?

>concurrent connection easily. I do not know if PostgreSQL may scale up to these numbers! we need someone experienced in this. Another solution may be to open a connection only when you need it and close it asap. Regards Nicola Ranaldo

Re: PostgreSQL backend: a waste of time?

erience with huge number of users or slow server ? Bye Nicola Ranaldo > IIRC someone implemented such a daemon and patched cyrus to use it. This > daemon's backend was a text-file but the "protocol" is there. > > a drawing

Re: PostgreSQL backend: a waste of time?

o restart cyrus! I know how to patch this in master.c but in case of fatal error, it will bring up a huge number of sequential forks until PostgreSQL is available again. So other changes will be necessary, but i think that's not up to me. Nicola Ranaldo > I have the same point of view,

Re: PostgreSQL backend: a waste of time?

I use PostgreSQL because it's very stable on True64 (!), and there is an historic consolidation of transactions and referential integrity. These make MySQL immature for my purpose! Howewer at first look it seems porting C code from PostgreSQL to MySQL is very easy :) Nicola Ranaldo > Hy

PostgreSQL backend: a waste of time?

out 5 time faster then with BerkeleyDB4. If the cyrus community is interested in this little piece of code (i don't know due to presence of skiplist backend) we can start a thread now! Best Regards Nicola Ranaldo System Manager C.D.S. Federico II University Neaples - Italy