Re: failover scenario's for replication

2006-08-29 Thread Paul Dekkers
Hi, Bron Gondwana wrote: On Mon, Aug 28, 2006 at 02:23:22PM -0400, Wesley Craig wrote: On 26 Aug 2006, at 16:09, Paul Dekkers wrote: Right now, it looks tricky to me to enable replication after failover, or the replicated machine itself if you're not sure that the replica is

Re: Another sync-client issue

2006-08-29 Thread David Carter
On Sun, 27 Aug 2006, Bron Gondwana wrote: This is just a copy-and-pasteo that I noticed while looking for the other issue in the sync code tonight. I think the fix is pretty self evident since exactly the same comment exists elsewhere with the correct error code after it and the value that's

Re: sync_client bails out after 3 MAILBOXES need upgrading to USER in one run

2006-08-29 Thread David Carter
On Sun, 27 Aug 2006, Bron Gondwana wrote: I've attached my trivial solution (against CVS of last week some time), but I'm thinking a better (as in, less wasteful) solution might be to not return an error at all for a failed mailbox, but instead keep walking the entire tree, and then generate

Re: sync_client stalls the rest of cyrus while 'no route to host'

2006-08-29 Thread David Carter
On Sun, 27 Aug 2006, Bron Gondwana wrote: To tell you the truth, I'm seriously considering writing a replacement to sync_client that does a bunch of different things including multiple replicas, maintaining log files, etc. All of this drops out pretty easily from a pattern which produces a

Re: sieve doesn't work

2006-08-29 Thread Martin G.H. Minkler
Phil Pennock schrieb: If you're only supporting PLAIN and LOGIN then without TLS you need a minimum of 0. sasl_minimum_layer: 1 sieve_sasl_minimum_layer: 0 After reloading and even restarting cyrus with the changes to the sieveshell die line and the imapd.conf in place as suggested, I

Re: hardware recommendations for MURDER?

2006-08-29 Thread Marten Lehmann
Hello, I have the same considerations for an upcoming cyrus murder setup. I would like to continue to use RHEL on HP ProLiant hardware as most of our services are running on it and it works perfectly. While I understand that MUPDATE and the frontends will be idling around most of the time (I

'inline' in sieve/bc_emit.c

2006-08-29 Thread Paul Boven
Hi everyone, The file sieve/bc_emit.c contains an inline function declaration in line 48 (version cyrus-imap-2.2.13): inline int write_int (int fd, int x) { int y=htonl(x); return (write(fd, y, sizeof(int))); } I would like to suggest turning this into a 'static inline', for

Re: Berkeley DB upgrade - 2nd try

2006-08-29 Thread Paul Boven
Hi everyone, Paul Boven wrote: If I build cyrus against the old version (4.1.25), it runs great. If I build it against 4.4.20, it doesn't want to start. Even though I've changed tlscache_db and duplicate_db to 'skiplist' in the imapd.conf and removed those db-files from the system, so it

imaps[6644]: PROTERR: end of file reached

2006-08-29 Thread Davin Flatten
Hello- I have recently set up a cyrus murder with three backends running Cyrus Imapd 2.2.12 using Cyrus SASL 2.1.22 running on Debian Linux. Everything seems to be working fine but I am getting quite a few of these error messages in our imapd.log file on the master/frontend server.

RE: sync_client stalls the rest of cyrus while 'no route to host'

2006-08-29 Thread David S. Madole
From David Carter on Tuesday, August 29, 2006 4:52 AM: On Sun, 27 Aug 2006, Bron Gondwana wrote: To tell you the truth, I'm seriously considering writing a replacement to sync_client that does a bunch of different things including multiple replicas, maintaining log files, etc. All

something strange with sieve

2006-08-29 Thread VALOIS, Pascal
has someone ever sieve working two or three times, and then not, like if the rule was deactivated ? i set the rules with ingo (from the horde framework), and when i mail to the box, the filter works. but then after two or three tests, it doesn't work anymore. when i check the rules, i see that

Re: sync_client bails out after 3 MAILBOXES need upgrading to USER in one run

2006-08-29 Thread Wesley Craig
On 29 Aug 2006, at 04:35, David Carter wrote: My original code (which we are still running: I'm not in any hurry to upgrade to 2.3) sorts mailbox actions by user. If a single mailbox action associated with a user fails the rest are discarded and a USER event is generated. If the USER event

Re: sync_client stalls the rest of cyrus while 'no route to host'

2006-08-29 Thread Wesley Craig
On 28 Aug 2006, at 20:33, Bron Gondwana wrote: What else do you have that will kill it? 4) xfer onto a replicating backend causes sync_client to exit 8) renaming users causes sync_client to exit In both of these, size and other load matters. We agree on the design-flaws

deliver.db conversion to skiplist

2006-08-29 Thread Shelley Waltz
I have read many threads regarding issues with deliver.db being in Berkeley DB format. I am running cyrus-imapd-2.2.3-4 on Redhat AS3. I have not had any issues with deliver.db until last week. I have about 200 accounts with most at 250MB, some at 500MB and a few at 1GB. The issue started with

Re: failover scenario's for replication

2006-08-29 Thread Wesley Craig
On 29 Aug 2006, at 04:11, Paul Dekkers wrote: I haven't tried this; but does it hurt defining sync_server, imapd and friends processes in the replicas cyrus.conf and by that have it identical as the master? If you tell the replica where mupdate is, sync_server behaves incorrectly. I'd also

RE: sync_client bails out after 3 MAILBOXES need upgrading to USER in one run

2006-08-29 Thread Ken Murchison
The main reason things changed is sypport for shared mailboxes. I can't elaborate now because I'm driving. -- Kenneth Murchison Systems Programmer Project Cyrus Developer/Maintainer Carnegie Mellon University -Original Message- From: Wesley Craig [EMAIL PROTECTED] To: David Carter

Re: deliver.db conversion to skiplist

2006-08-29 Thread Rafael Alcalde
Use db_recover Shelley Waltz wrote: I have read many threads regarding issues with deliver.db being in Berkeley DB format. I am running cyrus-imapd-2.2.3-4 on Redhat AS3. I have not had any issues with deliver.db until last week. I have about 200 accounts with most at 250MB, some at

Re: deliver.db conversion to skiplist

2006-08-29 Thread Shelley Waltz
my distro (cyrus-imapd-2.2.3-4) does not appear to have db_recover? Rafael Alcalde said: Use db_recover Shelley Waltz wrote: I have read many threads regarding issues with deliver.db being in Berkeley DB format. I am running cyrus-imapd-2.2.3-4 on Redhat AS3. I have not had any

Re: deliver.db conversion to skiplist

2006-08-29 Thread Wesley Craig
On 29 Aug 2006, at 11:22, Shelley Waltz wrote: My question is - should I convert the deliver.db to skiplist? If I simply move it elsewhere and change the imapd.conf to use a deliver.db in skiplist and restart, what is lost? Surely this huge db contains information necessary and useful to

Mailbox does not exist

2006-08-29 Thread Bart Van Loon
Hi all, I am new to this list but didn't to search the archives, so I hope this question is not disturbing anyone. I have a brand new fetchmail procmail cyrus-imapd setup on a FreeBSD 6.0-RELEASE (amd64) machine. all is working very well, except for delivery of mails into specific user

Re: Mailbox does not exist

2006-08-29 Thread former03 | Baltasar Cevc
Hi Bart, user.bbbart.Lists.gphoto.devel (\HasNoChildren) [...] alex # echo | /usr/local/cyrus/bin/deliver -m user.bbbart.Lists.gphoto.devel +user.bbbart.Lists.gphoto.devel: Mailbox does not exist alex # logout [EMAIL PROTECTED] ~ $ echo | /usr/local/cyrus/bin/deliver -m Lists.gphoto.devel

Re: Mailbox does not exist

2006-08-29 Thread Cristian Mitrana
* Bart Van Loon wrote [Tuesday, August 29, 2006 07:57:30 PM +0200] Hi all, I am new to this list but didn't to search the archives, so I hope this question is not disturbing anyone. [...] alex # echo | /usr/local/cyrus/bin/deliver -m user.bbbart.Lists.gphoto.devel

Re: Berkeley DB upgrade - 2nd try

2006-08-29 Thread Andrew Morgan
On Tue, 29 Aug 2006, Paul Boven wrote: Progress made since: I've tried to build a Cyrus without any Berkeley by specifying '--without-bdb' - for that, I had to comment out a fixed '#include db.h' in lib/auth_pts.h. But that only resulted in this error message when starting up: Fatal error:

Re: sync_client stalls the rest of cyrus while 'no route to host'

2006-08-29 Thread Bron Gondwana
On Tue, 29 Aug 2006 09:51:49 +0100 (BST), David Carter [EMAIL PROTECTED] said: On Sun, 27 Aug 2006, Bron Gondwana wrote: To tell you the truth, I'm seriously considering writing a replacement to sync_client that does a bunch of different things including multiple replicas, maintaining

Re: sync_client stalls the rest of cyrus while 'no route to host'

2006-08-29 Thread Wesley Craig
On 29 Aug 2006, at 18:38, Bron Gondwana wrote: I fail to see the difference between this and a single big log file where each replica keeps track of where it's up to in the log file and then seeks to that spot, reads up to say 10,000 lines and processes that, then stores the new location so