Re: (important) cyrus-imapd 2.4.16 released
Hi, Jeroen van Meeuwen schrieb (19.04.2012 12:00 Uhr): I'm forwarding this message posted to the announcement mailing list originally, to let you know any upgrades should target 2.4.16 as opposed to 2.4.15. We are pleased to announce the release of Cyrus IMAPd 2.4.16. This is a stable release in the 2.4.x series. http://www.cyrusimap.org/mediawiki/index.php/Downloads#IMAP_Server claims 2.4.14 is the latest release: The latest stable/current release of the IMAP server is 2.4.14 The release process should include updating the wiki. There is not CHANGES page in the wiki, is there? Marc Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: (important) cyrus-imapd 2.4.16 released
On 05/10/2012 11:45 AM, Marc Patermann wrote: Hi, Jeroen van Meeuwen schrieb (19.04.2012 12:00 Uhr): I'm forwarding this message posted to the announcement mailing list originally, to let you know any upgrades should target 2.4.16 as opposed to 2.4.15. We are pleased to announce the release of Cyrus IMAPd 2.4.16. This is a stable release in the 2.4.x series. http://www.cyrusimap.org/mediawiki/index.php/Downloads#IMAP_Server claims 2.4.14 is the latest release: The latest stable/current release of the IMAP server is 2.4.14 Fixed. The release process should include updating the wiki. Or moving that out of the wiki, but yes, whatever is the least amount of effort for the release engineer but still conveys all the correct information to folks downloading it. There is not CHANGES page in the wiki, is there? Do you mean for changes to the wiki site, or for changes to Cyrus? Both exist. http://www.cyrusimap.org/mediawiki/index.php/Special:RecentChanges will show you recent changes to the wiki. Each release of Cyrus contains a change summary like the following: http://www.cyrusimap.org/docs/cyrus-imapd/2.4.16/changes.php It was recently discussed that we need to improve upon the Cyrus ChangeLog. That will be coming. Thanks, Dave Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: (important) cyrus-imapd 2.4.16 released
On Thu, May 10, 2012 at 05:45:24PM +0200, Marc Patermann wrote: Hi, Jeroen van Meeuwen schrieb (19.04.2012 12:00 Uhr): I'm forwarding this message posted to the announcement mailing list originally, to let you know any upgrades should target 2.4.16 as opposed to 2.4.15. We are pleased to announce the release of Cyrus IMAPd 2.4.16. This is a stable release in the 2.4.x series. http://www.cyrusimap.org/mediawiki/index.php/Downloads#IMAP_Server claims 2.4.14 is the latest release: The latest stable/current release of the IMAP server is 2.4.14 The release process should include updating the wiki. It did last time I checked. Jeroen? http://www.cyrusimap.org/mediawiki/index.php/Release_Processes_and_Tasks Says update the Latest_Updates page on the wiki Bron. Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: (important) cyrus-imapd 2.4.16 released
Bron, sorry, somehow I forgot about this mail! --On 19. April 2012 20:04:04 +0200 Bron Gondwana br...@fastmail.fm wrote: I think I've read all the available information regarding the issue, but I'm still confused. We're still running 2.3.x for production, but I have a test system with a copy of the production data. We use fulldirhash. When I installed 2.4.14, I encountered the hashing issue. So now I ran the rehash script after updating to 2.4.16: $ time /usr/lib/cyrus-imapd/rehash -v -F /etc/imapd.conf you are using /var/lib/imap/sieve as your sieve directory. i will also hash partitions. converting configuration directory /var/lib/imap... mkdir /var/lib/imap/lock: done user quota done sieve /var/lib/imap/sieve... rename /var/lib/imap/sieve/global to /var/lib/imap/sieve/V/global: done done partition /var/spool/imap... done partition /var/spool/imap2... done partition /var/spool/imap3... done partition /var/spool/imap4... done partition /var/spool/imap5... done partition /var/spool/imap6... done real0m7.232s user0m5.639s sys 0m0.227s Just seven seconds? And I don't see much actual rehashing, except for the global sieve directory. What am I missing? Are your directories already hashed correctly? It doesn't move anything it doesn't have to! Well, that's the question, I suppose. I'm thinking that I may have misunderstood the issue. The production server running 2.3.14 is a 32-bit RHEL 3 system. The VM I'm using for 2.4 is a 64-bit RHEL 5 system. Its Perl binary uses 32-bit ints. I thought previously that I would have to rehash the 2.3 spool for that to work, but now I start to think that I don't, because the hashing algorithm hasn't actually changed, and the Perl part has been fixed. The only problem would have been trying to use the broken Perl code in 2.4.14. Is that correct? Thanks, Sebastian -- .:.Sebastian Hagedorn - RZKR-R1 (Gebäude 52), Zimmer 18.:. .:.Regionales Rechenzentrum (RRZK).:. .:.Universität zu Köln / Cologne University - ✆ +49-221-478-5587.:. p7s7E00mq1tyj.p7s Description: S/MIME cryptographic signature Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: (important) cyrus-imapd 2.4.16 released
On Thu, Apr 26, 2012 at 04:12:38PM +0200, Sebastian Hagedorn wrote: Bron, sorry, somehow I forgot about this mail! --On 19. April 2012 20:04:04 +0200 Bron Gondwana br...@fastmail.fm wrote: I think I've read all the available information regarding the issue, but I'm still confused. We're still running 2.3.x for production, but I have a test system with a copy of the production data. We use fulldirhash. When I installed 2.4.14, I encountered the hashing issue. So now I ran the rehash script after updating to 2.4.16: $ time /usr/lib/cyrus-imapd/rehash -v -F /etc/imapd.conf you are using /var/lib/imap/sieve as your sieve directory. i will also hash partitions. converting configuration directory /var/lib/imap... mkdir /var/lib/imap/lock: done user quota done sieve /var/lib/imap/sieve... rename /var/lib/imap/sieve/global to /var/lib/imap/sieve/V/global: done done partition /var/spool/imap... done partition /var/spool/imap2... done partition /var/spool/imap3... done partition /var/spool/imap4... done partition /var/spool/imap5... done partition /var/spool/imap6... done real0m7.232s user0m5.639s sys 0m0.227s Just seven seconds? And I don't see much actual rehashing, except for the global sieve directory. What am I missing? Are your directories already hashed correctly? It doesn't move anything it doesn't have to! Well, that's the question, I suppose. I'm thinking that I may have misunderstood the issue. The production server running 2.3.14 is a 32-bit RHEL 3 system. The VM I'm using for 2.4 is a 64-bit RHEL 5 system. Its Perl binary uses 32-bit ints. I thought previously that I would have to rehash the 2.3 spool for that to work, but now I start to think that I don't, because the hashing algorithm hasn't actually changed, and the Perl part has been fixed. The only problem would have been trying to use the broken Perl code in 2.4.14. Is that correct? Yeah, could be. The hashing algorithm in 2.4.14 was changed to 64 bit too I think. Easiest is to test that mbpath from 2.4.16 returns the same paths as your files on disk! Bron. Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: (important) cyrus-imapd 2.4.16 released
On Thu, 2012-04-19 at 11:00 +0100, Jeroen van Meeuwen wrote: Hi there, I'm forwarding this message posted to the announcement mailing list originally, to let you know any upgrades should target 2.4.16 as opposed to 2.4.15. We are pleased to announce the release of Cyrus IMAPd 2.4.16. [1] https://bugzilla.cyrusimap.org/show_bug.cgi?id=3651 The bug contains the comment: Can we please confirm/deny this only breaks systems with fulldirhash: 1 configured? Is the answer to that question Yes; sites that do not specify fulldirhash or have a fulldirhash: 0 in their imapd.conf are not affected and do not need to rehash. The correct rehash procedure is to execute - /usr/lib/cyrus-imapd/rehash -v -F /etc/imapd.conf [at least on my boxes rehash does not have a manual page; and rehash --help or rehash -? just errors] signature.asc Description: This is a digitally signed message part Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: (important) cyrus-imapd 2.4.16 released
On Thu, 2012-04-19 at 11:00 +0100, Jeroen van Meeuwen wrote: Hi there, I'm forwarding this message posted to the announcement mailing list originally, to let you know any upgrades should target 2.4.16 as opposed to 2.4.15. We are pleased to announce the release of Cyrus IMAPd 2.4.16. [1] https://bugzilla.cyrusimap.org/show_bug.cgi?id=3651 The bug contains the comment: Can we please confirm/deny this only breaks systems with fulldirhash: 1 configured? Is the answer to that question Yes; sites that do not specify fulldirhash or have a fulldirhash: 0 in their imapd.conf are not affected and do not need to rehash. I think that's correct. At least we have hashimapspool: true as default in our RPMs and fulldirhash is disabled by default and there are no problems AFAIK. Regards, Simon Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: (important) cyrus-imapd 2.4.16 released
On Wed, Apr 25, 2012 at 07:45:27PM +0200, Simon Matter wrote: On Thu, 2012-04-19 at 11:00 +0100, Jeroen van Meeuwen wrote: Hi there, I'm forwarding this message posted to the announcement mailing list originally, to let you know any upgrades should target 2.4.16 as opposed to 2.4.15. We are pleased to announce the release of Cyrus IMAPd 2.4.16. [1] https://bugzilla.cyrusimap.org/show_bug.cgi?id=3651 The bug contains the comment: Can we please confirm/deny this only breaks systems with fulldirhash: 1 configured? Is the answer to that question Yes; sites that do not specify fulldirhash or have a fulldirhash: 0 in their imapd.conf are not affected and do not need to rehash. I think that's correct. At least we have hashimapspool: true as default in our RPMs and fulldirhash is disabled by default and there are no problems AFAIK. Yes, that's correct - without fulldirhash you should be fine. Bron. Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
(important) cyrus-imapd 2.4.16 released
Hi there, I'm forwarding this message posted to the announcement mailing list originally, to let you know any upgrades should target 2.4.16 as opposed to 2.4.15. We are pleased to announce the release of Cyrus IMAPd 2.4.16. This is a stable release in the 2.4.x series. It contains exactly one bugfix in tools/rehash, which was rewritten after 2.4.14 introduced a critical fault for deployments that have the fulldirhash option enabled. Release 2.4.15 was released to resolve this issue, among others, but the tool as released with 2.4.15 contained Perl syntax errors. We recommend ALL sites that deploy Cyrus IMAP with the fulldirhash option enabled to update to 2.4.16. Please see bug #3651[1] for a full history of this bug. A special thanks goes out to Carlos Velasco for catching and reporting this issue first. We apologize for any inconvenience caused. You can download via HTTP or FTP: http://cyrusimap.org/releases/cyrus-imapd-2.4.16.tar.gz ftp://ftp.cyrusimap.org/cyrus-imapd/cyrus-imapd-2.4.16.tar.gz On behalf of the Cyrus team, Kind regards, Jeroen van Meeuwen [1] https://bugzilla.cyrusimap.org/show_bug.cgi?id=3651 -- Systems Architect, Kolab Systems AG e: vanmeeuwen at kolabsys.com m: +44 74 2516 3817 w: http://www.kolabsys.com pgp: 9342 BF08 signature.asc Description: This is a digitally signed message part. Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: (important) cyrus-imapd 2.4.16 released
On Thu, 19 Apr 2012 21:19:32 +0900, Dennis Davis d.h.da...@bath.ac.uk wrote: Got the following error when compiling this on OpenBSD5.0: util.c: In function 'dir_hash_c': util.c:284: error: 'UINT32_MAX' undeclared (first use in this function) util.c:284: error: (Each undeclared identifier is reported only once util.c:284: error: for each function it appears in.) *** Error code 1 Quickly fixed by applying the following patch: --- lib/util.c.orig Thu Apr 19 10:39:51 2012 +++ lib/util.c Thu Apr 19 12:56:31 2012 @@ -62,6 +62,10 @@ #include sys/socket.h #include errno.h +#ifdef __OpenBSD__ +#include stdint.h +#endif /* __OpenBSD__ */ + #include exitcodes.h #include util.h #include xmalloc.h Although I'm sure this isn't the preferred way to do it :-( or use BIT32_MAX (defined in lib/util.h) instead of UNIT32_MAX? -- OBATA Akio / ob...@lins.jp Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: (important) cyrus-imapd 2.4.16 released
Hi,
On Thu, 19 Apr 2012 13:19:32 +0100 (BST)
Dennis Davis d.h.da...@bath.ac.uk said:
D.H.Davis Got the following error when compiling this on OpenBSD5.0:
D.H.Davis util.c: In function 'dir_hash_c':
D.H.Davis util.c:284: error: 'UINT32_MAX' undeclared (first use in this
function)
D.H.Davis util.c:284: error: (Each undeclared identifier is reported only once
D.H.Davis util.c:284: error: for each function it appears in.)
D.H.Davis *** Error code 1
D.H.Davis Quickly fixed by applying the following patch:
D.H.Davis --- lib/util.c.orig Thu Apr 19 10:39:51 2012
D.H.Davis +++ lib/util.c Thu Apr 19 12:56:31 2012
D.H.Davis @@ -62,6 +62,10 @@
D.H.Davis #include sys/socket.h
D.H.Davis #include errno.h
D.H.Davis
D.H.Davis +#ifdef __OpenBSD__
D.H.Davis +#include stdint.h
D.H.Davis +#endif /* __OpenBSD__ */
D.H.Davis +
D.H.Davis #include exitcodes.h
D.H.Davis #include util.h
D.H.Davis #include xmalloc.h
I met this issue on FreeBSD, too. The patch should be following:
Index: lib/util.c
diff -u -p lib/util.c.orig lib/util.c
--- lib/util.c.orig 2012-04-18 20:28:37.0 +0900
+++ lib/util.c 2012-04-18 22:29:24.521844579 +0900
@@ -55,6 +55,9 @@
#include syslog.h
#include sys/types.h
#include sys/stat.h
+#ifdef HAVE_STDINT_H
+#include stdint.h
+#endif
#ifdef HAVE_UNISTD_H
#include unistd.h
#endif
Sincerely,
--
Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan
u...@mahoroba.org ume@{,jp.}FreeBSD.org
http://www.imasy.org/~ume/
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: (important) cyrus-imapd 2.4.16 released
On Thu, Apr 19, 2012 at 01:19:32PM +0100, Dennis Davis wrote: On Thu, 19 Apr 2012, Jeroen van Meeuwen wrote: From: Jeroen van Meeuwen vanmeeu...@kolabsys.com To: cyrus-de...@lists.andrew.cmu.edu, info-cyrus@lists.andrew.cmu.edu Date: Thu, 19 Apr 2012 11:00:01 Subject: (important) cyrus-imapd 2.4.16 released ... We are pleased to announce the release of Cyrus IMAPd 2.4.16. This is a stable release in the 2.4.x series. ... Got the following error when compiling this on OpenBSD5.0: util.c: In function 'dir_hash_c': util.c:284: error: 'UINT32_MAX' undeclared (first use in this function) util.c:284: error: (Each undeclared identifier is reported only once util.c:284: error: for each function it appears in.) *** Error code 1 Quickly fixed by applying the following patch: --- lib/util.c.orig Thu Apr 19 10:39:51 2012 +++ lib/util.c Thu Apr 19 12:56:31 2012 @@ -62,6 +62,10 @@ #include sys/socket.h #include errno.h +#ifdef __OpenBSD__ +#include stdint.h +#endif /* __OpenBSD__ */ + #include exitcodes.h #include util.h #include xmalloc.h Although I'm sure this isn't the preferred way to do it :-( stdint is used unprotected in other places in the code, so just including it without the __OpenBSD__ would be fine. Bron ( patching the code now ) Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: (important) cyrus-imapd 2.4.16 released
On Thu, Apr 19, 2012 at 09:49:15PM +0900, OBATA Akio wrote: On Thu, 19 Apr 2012 21:19:32 +0900, Dennis Davis d.h.da...@bath.ac.uk wrote: +#include stdint.h or use BIT32_MAX (defined in lib/util.h) instead of UNIT32_MAX? I'm planning to get rid of all the BIT32 nonsense. Bron. Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: (important) cyrus-imapd 2.4.16 released
--On 19. April 2012 11:00:01 +0100 Jeroen van Meeuwen vanmeeu...@kolabsys.com wrote: It contains exactly one bugfix in tools/rehash, which was rewritten after 2.4.14 introduced a critical fault for deployments that have the fulldirhash option enabled. Release 2.4.15 was released to resolve this issue, among others, but the tool as released with 2.4.15 contained Perl syntax errors. We recommend ALL sites that deploy Cyrus IMAP with the fulldirhash option enabled to update to 2.4.16. Please see bug #3651[1] for a full history of this bug. A special thanks goes out to Carlos Velasco for catching and reporting this issue first. I think I've read all the available information regarding the issue, but I'm still confused. We're still running 2.3.x for production, but I have a test system with a copy of the production data. We use fulldirhash. When I installed 2.4.14, I encountered the hashing issue. So now I ran the rehash script after updating to 2.4.16: $ time /usr/lib/cyrus-imapd/rehash -v -F /etc/imapd.conf you are using /var/lib/imap/sieve as your sieve directory. i will also hash partitions. converting configuration directory /var/lib/imap... mkdir /var/lib/imap/lock: done user quota done sieve /var/lib/imap/sieve... rename /var/lib/imap/sieve/global to /var/lib/imap/sieve/V/global: done done partition /var/spool/imap... done partition /var/spool/imap2... done partition /var/spool/imap3... done partition /var/spool/imap4... done partition /var/spool/imap5... done partition /var/spool/imap6... done real0m7.232s user0m5.639s sys 0m0.227s Just seven seconds? And I don't see much actual rehashing, except for the global sieve directory. What am I missing? -- .:.Sebastian Hagedorn - RZKR-R1 (Gebäude 52), Zimmer 18.:. .:.Regionales Rechenzentrum (RRZK).:. .:.Universität zu Köln / Cologne University - ✆ +49-221-478-5587.:. p7szVRUcinW6T.p7s Description: S/MIME cryptographic signature Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: (important) cyrus-imapd 2.4.16 released
On Thu, Apr 19, 2012 at 06:03:20PM +0200, Sebastian Hagedorn wrote: --On 19. April 2012 11:00:01 +0100 Jeroen van Meeuwen vanmeeu...@kolabsys.com wrote: It contains exactly one bugfix in tools/rehash, which was rewritten after 2.4.14 introduced a critical fault for deployments that have the fulldirhash option enabled. Release 2.4.15 was released to resolve this issue, among others, but the tool as released with 2.4.15 contained Perl syntax errors. We recommend ALL sites that deploy Cyrus IMAP with the fulldirhash option enabled to update to 2.4.16. Please see bug #3651[1] for a full history of this bug. A special thanks goes out to Carlos Velasco for catching and reporting this issue first. I think I've read all the available information regarding the issue, but I'm still confused. We're still running 2.3.x for production, but I have a test system with a copy of the production data. We use fulldirhash. When I installed 2.4.14, I encountered the hashing issue. So now I ran the rehash script after updating to 2.4.16: $ time /usr/lib/cyrus-imapd/rehash -v -F /etc/imapd.conf you are using /var/lib/imap/sieve as your sieve directory. i will also hash partitions. converting configuration directory /var/lib/imap... mkdir /var/lib/imap/lock: done user quota done sieve /var/lib/imap/sieve... rename /var/lib/imap/sieve/global to /var/lib/imap/sieve/V/global: done done partition /var/spool/imap... done partition /var/spool/imap2... done partition /var/spool/imap3... done partition /var/spool/imap4... done partition /var/spool/imap5... done partition /var/spool/imap6... done real 0m7.232s user 0m5.639s sys 0m0.227s Just seven seconds? And I don't see much actual rehashing, except for the global sieve directory. What am I missing? Are your directories already hashed correctly? It doesn't move anything it doesn't have to! Bron. Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
