Re: Cyrus 2.2.1-BETA Released

2003-07-31 Thread Rob Siemborski
On Fri, 1 Aug 2003, Jure Pecar wrote: > ... but either i'm stupid (must be the hour ..) or your cvs is seriously > messed up ... i just pulled the cyrus HEAD branch to find out it has no > masssievec, not even sievec! They are not visible through cvsweb, i tried > HEAD, MAIN, cyrus-release-2-2-1.

Re: Cyrus 2.2.1-BETA Released

2003-07-31 Thread Jure Pecar
On Wed, 30 Jul 2003 17:02:08 -0400 (EDT) Rob Siemborski <[EMAIL PROTECTED]> wrote: > You want to get the copy from CVS though, not the included one, otherwise > you'll lose all of your current sript activations (though not the scripts > themselves). > > -Rob Thanks for the tip ... ... but eith

Re: Cyrus 2.2.1-BETA Released

2003-07-30 Thread Rob Siemborski
On Wed, 30 Jul 2003, Igor Brezac wrote: > $cyrus-imapd-src/tools/masssievec > will do the trick. You want to get the copy from CVS though, not the included one, otherwise you'll lose all of your current sript activations (though not the scripts themselves). -Rob -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Re: Cyrus 2.2.1-BETA Released

2003-07-30 Thread Igor Brezac
On Wed, 30 Jul 2003, Jure Pecar wrote: > On Thu, 17 Jul 2003 11:20:20 -0400 (EDT) > Rob Siemborski <[EMAIL PROTECTED]> wrote: > > > Additionally, the > > sieve bytecode now is stored in network byte order and is therefore > > portable across architectures. > > What does this mean to us that run 2

Re: Cyrus 2.2.1-BETA Released

2003-07-30 Thread Ken Murchison
Quoting Jure Pecar <[EMAIL PROTECTED]>: > On Thu, 17 Jul 2003 11:20:20 -0400 (EDT) > Rob Siemborski <[EMAIL PROTECTED]> wrote: > > > Additionally, the > > sieve bytecode now is stored in network byte order and is therefore > > portable across architectures. > > What does this mean to us that ru

Re: Cyrus 2.2.1-BETA Released

2003-07-30 Thread Jure Pecar
On Thu, 17 Jul 2003 11:20:20 -0400 (EDT) Rob Siemborski <[EMAIL PROTECTED]> wrote: > Additionally, the > sieve bytecode now is stored in network byte order and is therefore > portable across architectures. What does this mean to us that run 2.2a in production? :) Is this backward compatible / w

Re: Cyrus 2.2.1-BETA Released

2003-07-18 Thread Rob Siemborski
On Fri, 18 Jul 2003, Joe Rhett wrote: > This is still on the 2_2 CVS branch, right? So if we are current with CVS > there's nothing new? Or do we need to pull a different branch? Yup, this is still the 2.2. branch. -Rob -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Rob

Re: Cyrus 2.2.1-BETA Released

2003-07-18 Thread Joe Rhett
This is still on the 2_2 CVS branch, right? So if we are current with CVS there's nothing new? Or do we need to pull a different branch? On Thu, Jul 17, 2003 at 11:20:20AM -0400, Rob Siemborski wrote: > I'm pleased to announce the release of Cyrus 2.2.1 on ftp.andrew.cmu.edu. > This is a BETA qu

Re: Cyrus 2.2.1-BETA Released

2003-07-17 Thread Ilya
Hi Rob. On FreeBSD box, I had to change to change cyrusdb_berkeley.c from : #include to #include which is probably not a big deal and i should be specifying path to db3 anyway. Also imtest failed to compile with error that INT_MAX is not defined, I looked around and noticed that imap also contai

Re: Cyrus 2.2.1-BETA Released

2003-07-17 Thread Rob Siemborski
On Thu, 17 Jul 2003, Ilya wrote: > On FreeBSD box, I had to change to change cyrusdb_berkeley.c from : > #include to #include which is > probably not a big deal and i should be specifying path to db3 anyway. There's an option you can pass to configure. > Also imtest failed to compile with erro

Cyrus 2.2.1-BETA Released

2003-07-17 Thread Rob Siemborski
I'm pleased to announce the release of Cyrus 2.2.1 on ftp.andrew.cmu.edu. This is a BETA quality release, as it contains significant new functionality, and a large number of fixes over 2.2.0-ALPHA. Feature additions include full r/w ANNOTATEMORE support, and use of annotations for administrative o