Re: Cyrus IMAPd 2.3.16 Released
On 13 Jan 2010, at 02:11, Simon Matter wrote: > My own real problem as RPM maintainer is that I'd like to stay with > logging to mail facility and not touching syslog config. Now with > older > releases, this was possible without much trouble because the logging > volume was moderate for not too heavy loaded servers. With some recent > developments this became worse and I'm wondering whether it was > intentional. My workaraound was to simply remove the culprits as > seen in > the patch because I didn't quickly find a better solution. I was > hoping to > use CYRUS_VERBOSE to control verbosity but that doesn't seem to work > outside of master. Does anyone have a better solution for the hacks > below? In other projects, I've added configuration for setlogmask(3). I think that would solve the underlying issue, here. As an aside, I think those debugging statements aren't appropriate, but that's not germane to the RPM maintainer issue, I don't think. :wes Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Cyrus IMAPd 2.3.16 Released
On 1/13/10 2:11 AM, Simon Matter wrote: > [ ... ] > My own real problem as RPM maintainer is that I'd like to stay with > logging to mail facility and not touching syslog config. > [ ... ] Chiming in here, specifically on this issue. I manually tweak the *.spec file to suit my local site requirements for each release, then rebuild. Would it be possible to introduce a couple configuration file directives that will allow us to tune these to our needs there? Thanks, Simon, for all the work you continue to do in putting these RPMs together -- it is greatly appreciated! Regards, Forrest Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Cyrus IMAPd 2.3.16 Released
> Bron Gondwana wrote: >> On Mon, Jan 04, 2010 at 09:11:10AM +0100, Simon Matter wrote: Or you can use a dummy backend. It's a backend which always says « OK » when you try to write in it, and always says « not in db » when you read in it. This backend was never committed into cyrus-imapd... Here is an up-to-date version. Then add this in imapd.conf : duplicate_db: dummy Ken, Bron : do you plan to include this backend into cyrus-imapd ? It's very handy when we don't want to use a database (here we often use dummy for annotations). >>> It looks really useful to me. Any chance this will go into upstream? >>> I'd >>> prefer to include it in my RPMs if I know it's also in upstream. >> >> It certainly will! There's a bit of 2.3 vs 2.4 uncertainty about where >> to put code. I think we've pretty much put 2.3 into maintainence mode. >> I'm telling everyone that we're releasing 2.4 in April on the theory >> that >> if you repeat something often enough it becomes true! > > Do we really need a dummy backend, or should we just rewrite the code so > that non-critical DBs can be specified as nil/none/null and just not > make the database calls? I think that may also fix the problem and implementation looks even easier than the dummy backend. My own real problem as RPM maintainer is that I'd like to stay with logging to mail facility and not touching syslog config. Now with older releases, this was possible without much trouble because the logging volume was moderate for not too heavy loaded servers. With some recent developments this became worse and I'm wondering whether it was intentional. My workaraound was to simply remove the culprits as seen in the patch because I didn't quickly find a better solution. I was hoping to use CYRUS_VERBOSE to control verbosity but that doesn't seem to work outside of master. Does anyone have a better solution for the hacks below? Regards, Simon --- cyrus-imapd-2.3.16/imap/global.c.orig 2009-10-13 17:10:36.0 +0200 +++ cyrus-imapd-2.3.16/imap/global.c2009-12-22 09:22:27.0 +0100 @@ -553,7 +553,7 @@ } /* try to open database */ -r = DENYDB->open(fname, 0, &db); +r = DENYDB->open(fname, CYRUSDB_CREATE, &db); if (r) { /* ignore non-existent DB, report all other errors */ if (errno != ENOENT) { @@ -566,7 +566,7 @@ const char *data = NULL; int datalen; - syslog(LOG_DEBUG, "fetching user_deny.db entry for '%s'", user); + /* syslog(LOG_DEBUG, "fetching user_deny.db entry for '%s'", user); */ do { r = DENYDB->fetch(db, user, strlen(user), &data, &datalen, NULL); } while (r == CYRUSDB_AGAIN); [si...@wurro cyrus-imapd-2.3.16-1.src]$ cat cyrus-imapd-2.3.12-statuscache_verbosity.patch --- cyrus-imapd-2.3.12/imap/index.c.orig2008-03-24 18:09:17.0 +0100 +++ cyrus-imapd-2.3.12/imap/index.c 2008-04-24 11:25:28.0 +0200 @@ -1573,13 +1573,13 @@ */ if (!r) { - syslog(LOG_DEBUG, "statuscache, '%s', '%s', '0x%02x', 'yes'", - mboxname, imapd_userid, statusitems); + /* syslog(LOG_DEBUG, "statuscache, '%s', '%s', '0x%02x', 'yes'", + mboxname, imapd_userid, statusitems); */ goto statusdone; } - syslog(LOG_DEBUG, "statuscache, '%s', '%s', '0x%02x', 'no'", - mboxname, imapd_userid, statusitems); + /* syslog(LOG_DEBUG, "statuscache, '%s', '%s', '0x%02x', 'no'", + mboxname, imapd_userid, statusitems); */ } /* Missing or invalid cache entry */ Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Cyrus IMAPd 2.3.16 Released
Bron Gondwana wrote: > On Mon, Jan 04, 2010 at 09:11:10AM +0100, Simon Matter wrote: >>> Or you can use a dummy backend. It's a backend which always says « OK >>> » when you try to write in it, and always says « not in db » when you >>> read in it. This backend was never committed into cyrus-imapd... Here >>> is an up-to-date version. >>> >>> Then add this in imapd.conf : >>> duplicate_db: dummy >>> >>> Ken, Bron : do you plan to include this backend into cyrus-imapd ? >>> It's very handy when we don't want to use a database (here we often >>> use dummy for annotations). >> It looks really useful to me. Any chance this will go into upstream? I'd >> prefer to include it in my RPMs if I know it's also in upstream. > > It certainly will! There's a bit of 2.3 vs 2.4 uncertainty about where > to put code. I think we've pretty much put 2.3 into maintainence mode. > I'm telling everyone that we're releasing 2.4 in April on the theory that > if you repeat something often enough it becomes true! Do we really need a dummy backend, or should we just rewrite the code so that non-critical DBs can be specified as nil/none/null and just not make the database calls? Also, in the case of disabling annotation_db, we shouldn't be advertising ANNOTATEMORE/METADATA in the IMAP capabilities. In the case of disabling duplicate_db, we shouldn't be allowing the Sieve Vacation extension, and we can't prevent mail loops caused by Sieve Redirect. -- Kenneth Murchison Systems Programmer Project Cyrus Developer/Maintainer Carnegie Mellon University Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Cyrus IMAPd 2.3.16 Released -- auto create patch available? [SOLVED]
On Mon, 2010-01-04 at 11:35 +0100, Simon Matter wrote: > > hi simon, > > > > thanks for your fantastic rpms :-) > > > > is there an autocreate patch that applies cleanly against this version? > > I've updated the patch from UoA for 2.3.16. It's in my rpms. > > Regards, > Simon Turns out that the ldap management tool was creating just the Inbox, therefore, when logging into imap, the autocreate procedure was not firing. Thanks M Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Cyrus IMAPd 2.3.16 Released -- auto create patch available?
On Mon, 2010-01-04 at 11:35 +0100, Simon Matter wrote: > > hi simon, > > > > thanks for your fantastic rpms :-) > > > > is there an autocreate patch that applies cleanly against this version? > > I've updated the patch from UoA for 2.3.16. It's in my rpms. > > Regards, > Simon Hi Simon, H ... I've just installed roundcube web mail and am running it against my cyrus with no joy -- i.e., create a new user, login to that user's account, and no boxes are being created. Relevant bits from imapd.conf: autocreateinboxfolders: Sent|Drafts|Deleted Items|Junk autocreatequota: 204800 autosubscribeinboxfolders: Sent|Drafts|Deleted Items|Junk createonpost: yes I am now noticing that these are subfolders of Inbox -- does this patch work when altnamespace: yes is set? Cheers M Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Cyrus IMAPd 2.3.16 Released
On Mon, Jan 04, 2010 at 09:11:10AM +0100, Simon Matter wrote: > > Or you can use a dummy backend. It's a backend which always says « OK > > » when you try to write in it, and always says « not in db » when you > > read in it. This backend was never committed into cyrus-imapd... Here > > is an up-to-date version. > > > > Then add this in imapd.conf : > > duplicate_db: dummy > > > > Ken, Bron : do you plan to include this backend into cyrus-imapd ? > > It's very handy when we don't want to use a database (here we often > > use dummy for annotations). > > It looks really useful to me. Any chance this will go into upstream? I'd > prefer to include it in my RPMs if I know it's also in upstream. It certainly will! There's a bit of 2.3 vs 2.4 uncertainty about where to put code. I think we've pretty much put 2.3 into maintainence mode. I'm telling everyone that we're releasing 2.4 in April on the theory that if you repeat something often enough it becomes true! Bron. Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Cyrus IMAPd 2.3.16 Released -- auto create patch available?
> hi simon, > > thanks for your fantastic rpms :-) > > is there an autocreate patch that applies cleanly against this version? I've updated the patch from UoA for 2.3.16. It's in my rpms. Regards, Simon Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Cyrus IMAPd 2.3.16 Released -- auto create patch available?
hi simon, thanks for your fantastic rpms :-) is there an autocreate patch that applies cleanly against this version? thanks m Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Cyrus IMAPd 2.3.16 Released
> Or you can use a dummy backend. It's a backend which always says « OK > » when you try to write in it, and always says « not in db » when you > read in it. This backend was never committed into cyrus-imapd... Here > is an up-to-date version. > > Then add this in imapd.conf : > duplicate_db: dummy > > Ken, Bron : do you plan to include this backend into cyrus-imapd ? > It's very handy when we don't want to use a database (here we often > use dummy for annotations). It looks really useful to me. Any chance this will go into upstream? I'd prefer to include it in my RPMs if I know it's also in upstream. Simon Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Cyrus IMAPd 2.3.16 Released
Or you can use a dummy backend. It's a backend which always says « OK » when you try to write in it, and always says « not in db » when you read in it. This backend was never committed into cyrus-imapd... Here is an up-to-date version. Then add this in imapd.conf : duplicate_db: dummy Ken, Bron : do you plan to include this backend into cyrus-imapd ? It's very handy when we don't want to use a database (here we often use dummy for annotations). -- Cyril Servant Le 22 décembre 2009 22:33, Simon Matter a écrit : >> Hi, >> >> I have update my Cyrus installation from 2.3.15 to 2.3.16. >> >> I know have this following error : >> >> IOERROR: opening /var/imap/user_deny.db: No such file or directory >> >> How can I correct this ? > > You could change you syslog to not log debug messages. > >> Modify imap configuration file ? > > No. > >> Create the user_deny.db, if yes how ? > > You could simply create an empty file ${configdir}/user_deny.db > But, then new messages will show up in syslog for every login about > reading the user_deny db. > > Because I can't easily change syslog in my RPMS I decided to do the > following: > 1) change the code so it will create the db if it doesn't exist. > 2) comment out the syslog message which simply tells that the db is being > read. > > I did the same with the statuscache db some time ago and decided to do it > again here :) > > I understand my "solution" has the drawback that it 1) creates the db even > if it's not used and 2) it may add some extra cycles because it tries to > read the empty db. Doesn't look perfect but works. > > Regards, > Simon > >> >> >> >> Le 21/12/2009 22:39, Ken Murchison a écrit : >>> Simon Matter wrote: >>> > I am pleased to announce the release of Cyrus IMAPd 2.3.16. This > release should be considered production quality. Major changes in the > release are the following: > > - Added 'user_deny.db' to be able to selectively deny users access to > Cyrus services. > While upgrading my rpms I wanted to see where the db is so I can handle it in the package. But I can't find it and even stracing didn't show that the file was searched for. Do we have to enable it at compile time or are there other options beside userdeny_db to configure it? Thanks for any hint. >>> Its in configdir, along with the rest of the dbs. Its not created by >>> default, since its not required for normal operation. >>> >>> Actually, its not the most efficient implementation right now, since it >>> does an open/read/close per login. I need to rework it so that it does >>> the open at service init time, leaves the db open for reading for the >>> each process reuse, and closes it at service shutdown time. This will >>> take a little work, because we plan on using a remote MySQL database at >>> CMU, so the actual read function will also have to reconnect if >>> necessary. >>> >>> >>> >> >> >> -- >> -- >> * E-Mail : mercier.frede...@iname.com >> * Site Web : http://lamusiqueceltique.sparfel.net/ >> -- >> >> >> Cyrus Home Page: http://cyrusimap.web.cmu.edu/ >> Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki >> List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html >> > > > > Cyrus Home Page: http://cyrusimap.web.cmu.edu/ > Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki > List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html diff -ruN cyrus-imapd-2.3.16/configure.in cyrus-imapd-2.3.16.new/configure.in --- cyrus-imapd-2.3.16/configure.in 2009-12-21 14:09:10.0 +0100 +++ cyrus-imapd-2.3.16.new/configure.in 2009-12-23 11:39:10.0 +0100 @@ -170,7 +170,7 @@ dnl function for doing each of the database backends dnl parameters: backend name, variable to set, withval -CYRUSDB_OBJS="cyrusdb_flat.o cyrusdb_skiplist.o cyrusdb_quotalegacy.o" +CYRUSDB_OBJS="cyrusdb_flat.o cyrusdb_skiplist.o cyrusdb_quotalegacy.o cyrusdb_dummy.o" dnl Berkeley DB Detection diff -ruN cyrus-imapd-2.3.16/lib/cyrusdb.c cyrus-imapd-2.3.16.new/lib/cyrusdb.c --- cyrus-imapd-2.3.16/lib/cyrusdb.c 2008-07-30 18:03:38.0 +0200 +++ cyrus-imapd-2.3.16.new/lib/cyrusdb.c 2009-12-23 11:36:28.0 +0100 @@ -75,6 +75,7 @@ #if defined HAVE_MYSQL || defined HAVE_PGSQL || defined HAVE_SQLITE &cyrusdb_sql, #endif +&cyrusdb_dummy, NULL }; void cyrusdb_init() diff -ruN cyrus-imapd-2.3.16/lib/cyrusdb_dummy.c cyrus-imapd-2.3.16.new/lib/cyrusdb_dummy.c --- cyrus-imapd-2.3.16/lib/cyrusdb_dummy.c 1970-01-01 01:00:00.0 +0100 +++ cyrus-imapd-2.3.16.new/lib/cyrusdb_dummy.c 2009-12-23 14:59:05.0 +0100 @@ -0,0 +1,221 @@ +/* cyrusdb_dummy.c -- cyrusdb dummy implementation + * + * Copyright (c) 1994-2008 Carnegie Mellon University. All rights reserved. + * + * Redistribution and use in source and binary forms, with or without
Re: Cyrus IMAPd 2.3.16 Released
> Hi, > > I have update my Cyrus installation from 2.3.15 to 2.3.16. > > I know have this following error : > > IOERROR: opening /var/imap/user_deny.db: No such file or directory > > How can I correct this ? You could change you syslog to not log debug messages. > Modify imap configuration file ? No. > Create the user_deny.db, if yes how ? You could simply create an empty file ${configdir}/user_deny.db But, then new messages will show up in syslog for every login about reading the user_deny db. Because I can't easily change syslog in my RPMS I decided to do the following: 1) change the code so it will create the db if it doesn't exist. 2) comment out the syslog message which simply tells that the db is being read. I did the same with the statuscache db some time ago and decided to do it again here :) I understand my "solution" has the drawback that it 1) creates the db even if it's not used and 2) it may add some extra cycles because it tries to read the empty db. Doesn't look perfect but works. Regards, Simon > > > > Le 21/12/2009 22:39, Ken Murchison a écrit : >> Simon Matter wrote: >> I am pleased to announce the release of Cyrus IMAPd 2.3.16. This release should be considered production quality. Major changes in the release are the following: - Added 'user_deny.db' to be able to selectively deny users access to Cyrus services. >>> While upgrading my rpms I wanted to see where the db is so I can handle >>> it >>> in the package. But I can't find it and even stracing didn't show that >>> the >>> file was searched for. Do we have to enable it at compile time or are >>> there other options beside userdeny_db to configure it? >>> Thanks for any hint. >>> >> Its in configdir, along with the rest of the dbs. Its not created by >> default, since its not required for normal operation. >> >> Actually, its not the most efficient implementation right now, since it >> does an open/read/close per login. I need to rework it so that it does >> the open at service init time, leaves the db open for reading for the >> each process reuse, and closes it at service shutdown time. This will >> take a little work, because we plan on using a remote MySQL database at >> CMU, so the actual read function will also have to reconnect if >> necessary. >> >> >> > > > -- > -- > * E-Mail : mercier.frede...@iname.com > * Site Web : http://lamusiqueceltique.sparfel.net/ > -- > > > Cyrus Home Page: http://cyrusimap.web.cmu.edu/ > Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki > List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html > Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Cyrus IMAPd 2.3.16 Released
Hi, I have update my Cyrus installation from 2.3.15 to 2.3.16. I know have this following error : IOERROR: opening /var/imap/user_deny.db: No such file or directory How can I correct this ? Modify imap configuration file ? Create the user_deny.db, if yes how ? Le 21/12/2009 22:39, Ken Murchison a écrit : > Simon Matter wrote: > >>> I am pleased to announce the release of Cyrus IMAPd 2.3.16. This >>> release should be considered production quality. Major changes in the >>> release are the following: >>> >>> - Added 'user_deny.db' to be able to selectively deny users access to >>> Cyrus services. >>> >> While upgrading my rpms I wanted to see where the db is so I can handle it >> in the package. But I can't find it and even stracing didn't show that the >> file was searched for. Do we have to enable it at compile time or are >> there other options beside userdeny_db to configure it? >> Thanks for any hint. >> > Its in configdir, along with the rest of the dbs. Its not created by > default, since its not required for normal operation. > > Actually, its not the most efficient implementation right now, since it > does an open/read/close per login. I need to rework it so that it does > the open at service init time, leaves the db open for reading for the > each process reuse, and closes it at service shutdown time. This will > take a little work, because we plan on using a remote MySQL database at > CMU, so the actual read function will also have to reconnect if necessary. > > > -- -- * E-Mail : mercier.frede...@iname.com * Site Web : http://lamusiqueceltique.sparfel.net/ -- Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Cyrus IMAPd 2.3.16 Released
Simon Matter wrote: >> I am pleased to announce the release of Cyrus IMAPd 2.3.16. This >> release should be considered production quality. Major changes in the >> release are the following: >> >> - Added 'user_deny.db' to be able to selectively deny users access to >>Cyrus services. > > While upgrading my rpms I wanted to see where the db is so I can handle it > in the package. But I can't find it and even stracing didn't show that the > file was searched for. Do we have to enable it at compile time or are > there other options beside userdeny_db to configure it? > Thanks for any hint. Its in configdir, along with the rest of the dbs. Its not created by default, since its not required for normal operation. Actually, its not the most efficient implementation right now, since it does an open/read/close per login. I need to rework it so that it does the open at service init time, leaves the db open for reading for the each process reuse, and closes it at service shutdown time. This will take a little work, because we plan on using a remote MySQL database at CMU, so the actual read function will also have to reconnect if necessary. -- Kenneth Murchison Systems Programmer Project Cyrus Developer/Maintainer Carnegie Mellon University Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Cyrus IMAPd 2.3.16 Released
> I am pleased to announce the release of Cyrus IMAPd 2.3.16. This > release should be considered production quality. Major changes in the > release are the following: > > - Added 'user_deny.db' to be able to selectively deny users access to >Cyrus services. While upgrading my rpms I wanted to see where the db is so I can handle it in the package. But I can't find it and even stracing didn't show that the file was searched for. Do we have to enable it at compile time or are there other options beside userdeny_db to configure it? Thanks for any hint. Simon > - Added 'popuseimapflags' option which enables setting and >obeying IMAP flags in the POP server. > - Added optimized method of handling an empty maildrop in pop3d. >(based on work of Cyril Servant ) > - Added 'annotation_definitions' option for specifying >external (third-party) annotations. (courtesy of Thomas >Viehmann ) > - Added COMPRESSion to replication protocol. (courtesy of Bron Gondwana >) > > For full details, please see doc/changes.html and > doc/install-upgrade.html which are included in the distribution. > > URLs for this release: > ftp://ftp.andrew.cmu.edu/pub/cyrus/cyrus-imapd-2.3.16.tar.gz > or > http://ftp.andrew.cmu.edu/pub/cyrus/cyrus-imapd-2.3.16.tar.gz > > > Questions and comments can be directed to > info-cyrus@lists.andrew.cmu.edu (public list), or > cyrus-b...@andrew.cmu.edu. > > Happy Holidays! > > -- > Kenneth Murchison > Systems Programmer > Project Cyrus Developer/Maintainer > Carnegie Mellon University > > > > > > > > > > > > > > > > Cyrus Home Page: http://cyrusimap.web.cmu.edu/ > Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki > List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html > Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Cyrus IMAPd 2.3.16 Released
I am pleased to announce the release of Cyrus IMAPd 2.3.16. This release should be considered production quality. Major changes in the release are the following: - Added 'user_deny.db' to be able to selectively deny users access to Cyrus services. - Added 'popuseimapflags' option which enables setting and obeying IMAP flags in the POP server. - Added optimized method of handling an empty maildrop in pop3d. (based on work of Cyril Servant ) - Added 'annotation_definitions' option for specifying external (third-party) annotations. (courtesy of Thomas Viehmann ) - Added COMPRESSion to replication protocol. (courtesy of Bron Gondwana ) For full details, please see doc/changes.html and doc/install-upgrade.html which are included in the distribution. URLs for this release: ftp://ftp.andrew.cmu.edu/pub/cyrus/cyrus-imapd-2.3.16.tar.gz or http://ftp.andrew.cmu.edu/pub/cyrus/cyrus-imapd-2.3.16.tar.gz Questions and comments can be directed to info-cyrus@lists.andrew.cmu.edu (public list), or cyrus-b...@andrew.cmu.edu. Happy Holidays! -- Kenneth Murchison Systems Programmer Project Cyrus Developer/Maintainer Carnegie Mellon University Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html