Re: Skiplist / best practice for 2.1 branch

2002-11-18 Thread Henrique de Moraes Holschuh
On Mon, 18 Nov 2002, Patrick Boutilier wrote: > Henrique de Moraes Holschuh wrote: > >For Linux: > > 1. Heavily tested and debugged AND patched BerkeleyDB 3.2, stay away from > > 4.x for now. > > I tried those stability patches and they didn't help. The only thing They are NOT supposed to h

Re: Skiplist / best practice for 2.1 branch

2002-11-18 Thread Henrique de Moraes Holschuh
On Mon, 18 Nov 2002, Lawrence Greenfield wrote: > Some of them (the lock timeout/wait is what I have in mind) will make the > system perform not as well. I'd have to profile it to know more, and I am quite short on time to do that right now. Maybe the fastmail.fm crew has any comments on this is

RE: Skiplist / best practice for 2.1 branch

2002-11-18 Thread ???
First of all, I used skiplist for mailboxes.db with imap-2.1.9 for better performance. But, I found sometimes the db gone to be corrupted, so I had to make a daily backup. As the author wrote in the skiplist code, there would be some bug. I think care must be taken to use skiplist so far. > ---

Re: Thoughts on the age-old cyradm thingie

2002-11-18 Thread Jay Levitt
Thanks! That's very helpful, especially given the notes from Henrique about patches - sounds like I don't want to be running a stock imapd on Linux. Still, it'd be good to fix this in the source distribution as well. After thinking about it, I suspect adding --perl-prefix to configure is probabl

Re: Skiplist / best practice for 2.1 branch

2002-11-18 Thread Paul M Fleming
I've just finished doing some benchmarking and general server abusing using ZD Labs IMAP test tool (http://www.etestinglabs.com/benchmarks/svrtools/email/t1intro.asp) and lmtpd performance makes sense. Each inbound message goes through lmtpd which does duplicate suppression (by default) meaning eac

Re: Skiplist / best practice for 2.1 branch

2002-11-18 Thread Rob Siemborski
On Mon, 18 Nov 2002, Patrick Boutilier wrote: > I tried those stability patches and they didn't help. The only thing > that stopped lmtp from hanging was switching from db3_nosync to > skiplist. What are the advantages of using db3_nosync over skiplist? db3_nosync uses the Berkeley DB backend, wh

Re: Skiplist / best practice for 2.1 branch

2002-11-18 Thread Patrick Boutilier
Henrique de Moraes Holschuh wrote: For Linux: 1. Heavily tested and debugged AND patched BerkeleyDB 3.2, stay away from 4.x for now. (i.e. use the ones from RedHat or Debian, not upstream). 2. Linux stability patches for Cyrus (see the Debian Cyrus package :-) Cyrus upstream

Re: Skiplist / best practice for 2.1 branch

2002-11-18 Thread Lawrence Greenfield
--On Monday, November 18, 2002 8:57 PM -0200 Henrique de Moraes Holschuh <[EMAIL PROTECTED]> wrote: Linux-specific that they have would negative consequences if applied to a source tree used for a Solaris or *BSD build?? With Linux being No negative consequences that I know of. But increased

Re: locking problems with 2.1.9

2002-11-18 Thread +archive . info-cyrus
--On Friday, November 8, 2002 7:49 PM -0500 Peter Krotkov <[EMAIL PROTECTED]> wrote: | Prior to a code fix to address the problems you observed, do you think it | would be unreasonable to configure master so that imaps is not offered? | We could revert to running stunnel for ssl support and then

Re: Skiplist / best practice for 2.1 branch

2002-11-18 Thread Jules Agee
Jonathan Marsden wrote: On 18 Nov 2002, Jules Agee writes: I think a lot of people would recommend you stay away from RH 8.0 for production servers. Not that I know of any particular problems... it's just that there's a lot of bleeding-edge stuff that hasn't proved itself as far as I'm concerned.

Re: Skiplist / best practice for 2.1 branch

2002-11-18 Thread Henrique de Moraes Holschuh
On Tue, 19 Nov 2002, Sebastian Hagedorn wrote: > -- Henrique de Moraes Holschuh <[EMAIL PROTECTED]> is rumored to have mumbled > on Montag, 18. November 2002 19:20 Uhr -0200 regarding Re: Skiplist / best > practice for 2.1 branch: > > > 4. Journaling filesystem (xfs, ext3, Reiser), in a 2.4.20p

Re: Skiplist / best practice for 2.1 branch

2002-11-18 Thread Jonathan Marsden
On 18 Nov 2002, Jules Agee writes: > Jonathan Marsden wrote: >> Are you recommending that RH 8.0 users running Cyrus should >> downgrade their BDB libraries to a 3.x RPM set ... > I think a lot of people would recommend you stay away from RH 8.0 > for production servers. Not that I know of any

Re: Skiplist / best practice for 2.1 branch

2002-11-18 Thread Sebastian Hagedorn
-- Henrique de Moraes Holschuh <[EMAIL PROTECTED]> is rumored to have mumbled on Montag, 18. November 2002 19:20 Uhr -0200 regarding Re: Skiplist / best practice for 2.1 branch: 4. Journaling filesystem (xfs, ext3, Reiser), in a 2.4.20pre kernel. Why do you suggest using 2.4.20pre? Is there

Re: Skiplist / best practice for 2.1 branch

2002-11-18 Thread Jules Agee
Jonathan Marsden wrote: Are you recommending that RH 8.0 users running Cyrus should downgrade their BDB libraries to a 3.x RPM set for db3 (perhaps as supplied for RH 7.3)? Wouldn't that tend to have adverse consequences for other software (Sendmail comes to mind) which expects them and which mig

Re: Skiplist / best practice for 2.1 branch

2002-11-18 Thread Galen Johnson
Henrique de Moraes Holschuh wrote: On Mon, 18 Nov 2002, Jonathan Marsden wrote: On 18 Nov 2002, Henrique de Moraes Holschuh writes: 1. Heavily tested and debugged AND patched BerkeleyDB 3.2, stay away from 4.x for now. (i.e. use the ones from RedHat or Debian, not upstream). R

Re: Skiplist / best practice for 2.1 branch

2002-11-18 Thread Henrique de Moraes Holschuh
On Mon, 18 Nov 2002, Jonathan Marsden wrote: > On 18 Nov 2002, Henrique de Moraes Holschuh writes: > > 1. Heavily tested and debugged AND patched BerkeleyDB 3.2, stay away > >from 4.x for now. (i.e. use the ones from RedHat or Debian, not > >upstream). > > Red Hat now supplies 4.0.14, for

Re: Skiplist / best practice for 2.1 branch

2002-11-18 Thread Jonathan Marsden
On 18 Nov 2002, Henrique de Moraes Holschuh writes: > For Linux: > 1. Heavily tested and debugged AND patched BerkeleyDB 3.2, stay away >from 4.x for now. (i.e. use the ones from RedHat or Debian, not >upstream). Red Hat now supplies 4.0.14, for example the db4-4.0.14-14.i386.rpm in Red

Re: Skiplist / best practice for 2.1 branch

2002-11-18 Thread Henrique de Moraes Holschuh
On Mon, 18 Nov 2002, Tim Pushor wrote: > >>duplicate? mboxlist? seen? subs? tls? > >db3_nosync, skiplist, skiplist, flat, db3_nosync For Linux: 1. Heavily tested and debugged AND patched BerkeleyDB 3.2, stay away from 4.x for now. (i.e. use the ones from RedHat or Debian, not upstream)

Re: Skiplist / best practice for 2.1 branch

2002-11-18 Thread Patrick Boutilier
Tim, RedHat 7.2 with BDB 4.0.14 Tim Pushor wrote: Patrick, What version of Berkeley (Sleepycat) DB were you using? What OS? Thanks, Tim Patrick Boutilier wrote: duplicate? mboxlist? seen? subs? tls? db3_nosync, skiplist, skiplist, flat, db3_nosync I had nothing but trouble using

Re: Skiplist / best practice for 2.1 branch

2002-11-18 Thread Tim Pushor
Patrick, What version of Berkeley (Sleepycat) DB were you using? What OS? Thanks, Tim Patrick Boutilier wrote: duplicate? mboxlist? seen? subs? tls? db3_nosync, skiplist, skiplist, flat, db3_nosync I had nothing but trouble using db3_nosync for duplicate so I would suggest using skiplis

Re: Skiplist / best practice for 2.1 branch

2002-11-18 Thread Rob Siemborski
On Mon, 18 Nov 2002, Tim Pushor wrote: > >db3_nosync, skiplist, skiplist, flat, db3_nosync > > > If this truly is a 'best practice', should it be added to the > documentation? or to a FAQ? Some people have claimed problems with berkeley DB in general, but from a theoretical standpoint the above s

Re: Skiplist / best practice for 2.1 branch

2002-11-18 Thread Tim Pushor
Rob Siemborski wrote: On Mon, 18 Nov 2002, Tim Pushor wrote: I have done some research on the skiplist algorithm, but am wondering about the cyrus implementation. Is it stable? I didn't know anyone else was implementing a persistant skiplist. Our implementation is stable (and I thought

Re: Skiplist / best practice for 2.1 branch

2002-11-18 Thread Patrick Boutilier
Rob Siemborski wrote: This is in the mailing list about 8 times, but.. duplicate? mboxlist? seen? subs? tls? db3_nosync, skiplist, skiplist, flat, db3_nosync I had nothing but trouble using db3_nosync for duplicate so I would suggest using skiplist as well for duplicate. -Rob

Re: Skiplist / best practice for 2.1 branch

2002-11-18 Thread Rob Siemborski
On Mon, 18 Nov 2002, Tim Pushor wrote: > I have done some research on the skiplist algorithm, but am wondering > about the cyrus implementation. Is it stable? I didn't know anyone else was implementing a persistant skiplist. Our implementation is stable (and I thought "proprietary"). > What is

DB problem during recovery.

2002-11-18 Thread Voutsinas Nikos
Hello all, I am using cyrus-imapd-2.1.10 and Berkeley DB 4.1.24 for duplicate delivery and tls cache. During database initialization I am always get the following errors: master[22732]: [ID 965400 local6.notice] process started ctl_cyrusdb[22733]: [ID 702911 local6.notice] recovering cyrus data

Re: Please help! Probs with cyrus-imapd 2.1.9 and db3 - DBERROR db3: Unable to allocate memory

2002-11-18 Thread Carsten Hoeger
On Mon, Nov 18, Marc Sebastian Pelzer wrote: > > You need the attached patch for the bdb3. > > I apply the patch and 'make clean' && re-compile db3, SASL and imapd but > it doesnt work for me: > > Nov 18 17:08:55 prime master: setrlimit: Unable to set file descriptors > limit to 2147483647: Oper

Skiplist / best practice for 2.1 branch

2002-11-18 Thread Tim Pushor
All, Hello, and I must first apologize because I know that what I am asking has been covered before, but I am having a difficult time finding information in the archives. I am still running the 1.6 branch on all of my production servers, and want to bring everything up to 2.1. I have resisted

problem with Cyrus 2.1.9 on tru64unix

2002-11-18 Thread Marco
Hi all, we have installed and setup cyrus-imap server 2.1.9 with cyrus-sasl 2.1.7 on a compaq ES45 with tru64unix, we have used berkeley db 4.0.14 the problem is that sometimes the master freeze, the socket on port 143 is open but the master doesn't answer and we get a connection time-out, in the l

Re: Please help! Probs with cyrus-imapd 2.1.9 and db3 - DBERROR db3: Unable to allocate memory

2002-11-18 Thread Marc Sebastian Pelzer
On Mon, 18 Nov 2002 14:20:51 +0100 Carsten Hoeger <[EMAIL PROTECTED]> wrote: Hi, thanks to Carsten for the quick answer. > > i successfully compiled cyrus-imapd 2.1.9 with SASL 2.1.9 and > > Berkeley DB 3.1.17 on a Sun Sparc 10 with SuSE 7.3 and 128MB RAM and > > get the following errors in /var

Best way to backup cyrus system

2002-11-18 Thread php
Dear all, I would like to know the best way of backup/restore cyrus system. What are the steps required? Are there "online backup" methods available? What are the files required to backup and how can I restore it on the same machine/ another machine? Many thanks! Boris --

housekeeping of *.db

2002-11-18 Thread php
Dear all, I found numberous error of "DBERROR: " at my /var/log/messages. It keeps the wrong location of *.db and I would like to do housekeeping on it. Is there any method? Many thanks! Boris --- PLEASE READ: The inf

Re: Problems configuring cyrus imap (./configure)

2002-11-18 Thread Rob Siemborski
--with-auth=unix The error message was just recently made more clear. -Rob On 18 Nov 2002, Jakob Breivik Grimstveit wrote: > I can't get a successful .configure of the cyrus imap, it keeps > complaining about Kerberos DES libraries, which I don't want to use. > > Tried > ./configure --dis

Re: DBERROR: error listing log files: Permission denied

2002-11-18 Thread Rob Siemborski
How are you invoking ctl_cyrusdb in cyrus.conf? On Mon, 18 Nov 2002, Christian Schulte wrote: > Rob Siemborski wrote: > > >On Mon, 18 Nov 2002, Christian Schulte wrote: > > > > > > > >>After doing cvs update on my perfectly running 2.2 installation these > >>messages appear in the logs which did

Problems configuring cyrus imap (./configure)

2002-11-18 Thread Jakob Breivik Grimstveit
I can't get a successful .configure of the cyrus imap, it keeps complaining about Kerberos DES libraries, which I don't want to use. Tried ./configure --disable-krb4 ./configure --without-krb4 ./configure --with-krb4=no They all return with the same fscking message: chec

Re: DBERROR: error listing log files: Permission denied

2002-11-18 Thread Christian Schulte
Rob Siemborski wrote: On Mon, 18 Nov 2002, Christian Schulte wrote: After doing cvs update on my perfectly running 2.2 installation these messages appear in the logs which did not happen before I did the update! Is that anything serious ? Can it be ignored ? What changed that this suddenly ha

Re: DBERROR: error listing log files: Permission denied

2002-11-18 Thread Christian Schulte
Ken Murchison wrote: Christian Schulte wrote: After doing cvs update on my perfectly running 2.2 installation these messages appear in the logs which did not happen before I did the update! Is that anything serious ? Can it be ignored ? What changed that this suddenly happens ? Nov 18 12:53:3

Re: DBERROR: error listing log files: Permission denied

2002-11-18 Thread Rob Siemborski
On Mon, 18 Nov 2002, Christian Schulte wrote: > After doing cvs update on my perfectly running 2.2 installation these > messages appear in the logs which did not happen before I did the > update! Is that anything serious ? Can it be ignored ? What changed that > this suddenly happens ? [snip] The

Re: DBERROR: error listing log files: Permission denied

2002-11-18 Thread Ken Murchison
Christian Schulte wrote: > > After doing cvs update on my perfectly running 2.2 installation these > messages appear in the logs which did not happen before I did the > update! Is that anything serious ? Can it be ignored ? What changed that > this suddenly happens ? > > Nov 18 12:53:36 mail ct

Re: Please help! Probs with cyrus-imapd 2.1.9 and db3 - DBERROR db3: Unable to allocate memory

2002-11-18 Thread Carsten Hoeger
On Mon, Nov 18, Marc Sebastian Pelzer wrote: > i successfully compiled cyrus-imapd 2.1.9 with SASL 2.1.9 and Berkeley > DB 3.1.17 on a Sun Sparc 10 with SuSE 7.3 and 128MB RAM and get the > following errors in /var/log/messages after starting the > '/usr/cyrus/bin/master' process and try to test i

Re: Default ACL for new user mailbox

2002-11-18 Thread marc . bigler
Hi, Well if I read the imapd.conf man page again it states the following: defaultacl: anyone lrs The Access Control List (ACL) placed on a newly-created (non-user) mailbox that does not have a parent mailbox. What I can see here which disturbs me is the "...(non-user) mailbox...

Please help! Probs with cyrus-imapd 2.1.9 and db3 - DBERROR db3: Unable to allocate memory

2002-11-18 Thread Marc Sebastian Pelzer
Hello, i successfully compiled cyrus-imapd 2.1.9 with SASL 2.1.9 and Berkeley DB 3.1.17 on a Sun Sparc 10 with SuSE 7.3 and 128MB RAM and get the following errors in /var/log/messages after starting the '/usr/cyrus/bin/master' process and try to test it via 'telnet prime 143'. Telnet opens the con

DBERROR: error listing log files: Permission denied

2002-11-18 Thread Christian Schulte
After doing cvs update on my perfectly running 2.2 installation these messages appear in the logs which did not happen before I did the update! Is that anything serious ? Can it be ignored ? What changed that this suddenly happens ? Nov 18 12:53:36 mail ctl_cyrusdb[7462]: [ID 854764 local6.err

Re: Default ACL for new user mailbox

2002-11-18 Thread mdam
Heyho, > Is it somehow possible to set a default ACL which a new mailbox will > inherit when I create it with cyradm ? What I would like to do is give > automatically full permissions to all new mailboxes to the cyrus > administrator. Or maybe there is another way to do that ? Read ' man 5 imapd.

Re: Preserving flags, and their global nature

2002-11-18 Thread Ian McDonald
Unfortunately for me, I think that my client (the Mail::IMAPClient perl module) only supports LOGIN. - Original Message - From: "Rob Siemborski" <[EMAIL PROTECTED]> To: "Ian McDonald" <[EMAIL PROTECTED]> Sent: Friday, November 15, 2002 7:45 PM Subject: Re: Preserving flags, and their globa

Re: Thoughts on the age-old cyradm thingie

2002-11-18 Thread Luca Olivetti
Jay Levitt wrote: I'm new to Cyrus imapd - and, for that matter, to autoconf, perl, Linux, younameit. Building cyrus-imapd-2.1.10 on Mandrake 9.0, I ran into a http://perso.wanadoo.es/olivetti/cyrus/ -- Luca Olivetti Wetron Automatización S.A. http://www.wetron.es/ Tel. +34 93 5883004 F

Default ACL for new user mailbox

2002-11-18 Thread marc . bigler
Hello, Is it somehow possible to set a default ACL which a new mailbox will inherit when I create it with cyradm ? What I would like to do is give automatically full permissions to all new mailboxes to the cyrus administrator. Or maybe there is another way to do that ? Regards Marc