Re: Cyrus IMAP 2.4.14 released
On Tue, Mar 13, 2012 at 08:00:58AM +0200, Leena Heino wrote: > Unfortunately there does not seem to be way to force either 32bit or > 64bit fulldirhash. Oh man. I knew there was a reason why we don't run fulldirhash! That sucks. Leena - should we back this out and get 2.4.15 out fast (with a changes.html!) and make the fulldirhash always be 32 bit hashing by changing the perl that way instead? Tell you the truth, I'm super-tempted to just change the code to look in BOTH locations always if you have fulldirhash. Bron. Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: Cyrus IMAP 2.4.14 released
On 13.3.2012 3:59, Patrick Boutilier wrote:
> I just updated my replication server from 2.4.12 to 2.4.14 and then got
> nothing but "System I/O error" errors in the logs. I took a look at
> http://bugzilla.cyrusimap.org/show_bug.cgi?id=3381 and noticed this:
>
> You can convert your mail directory hashing scheme from 32bit
> fulldirhash to
> 64bit fulldirhash with following commands:
> % tools/rehash basic
> % tools/rehash full
>
>
> Unfortunately I have almost 5TB of mail spread out on 23 different mount
> points. All the letters in /imap/mail are individual mount points so
> rehashing would mean lots of moves across the mount points which won't
> be quick.
>
> Is there a way to force Cyrus to use the old 32bit way, other than just
> removing the patch?
Unfortunately there does not seem to be way to force either 32bit or
64bit fulldirhash.
You have to remove this patch from 2.4.14:
diff --git a/lib/util.c b/lib/util.c
index 8bcb00e..c96caa5 100644
--- a/lib/util.c
+++ b/lib/util.c
@@ -269,7 +269,7 @@ int dir_hash_c(const char *name, int full)
if (full) {
unsigned char *pt;
- unsigned int n;
+ unsigned long long int n;
enum {
DIR_X = 3,
DIR_Y = 5,
--
Leena Heino University of Tampere / Computer Centre
( liinu at uta.fi ) ( http://www.uta.fi/laitokset/tkk )
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: Cyrus IMAP 2.4.14 released
On 03/12/2012 09:22 AM, Jeroen van Meeuwen (Kolab Systems) wrote: We are pleased to announce the release of Cyrus IMAPd 2.4.14. This is a stable release in the 2.4.x series. The release mainly contains bug fixes, mostly small but significant. Please find an overview of all bugs resolved in this release at: http://www.cyrusimap.org/mediawiki/index.php/Bugs_Resolved_in_2.4.14 You can download via HTTP or FTP: http://cyrusimap.org/releases/cyrus-imapd-2.4.14.tar.gz ftp://ftp.cyrusimap.org/cyrus-imapd/cyrus-imapd-2.4.14.tar.gz Kind regards, Jeroen van Meeuwen Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ I just updated my replication server from 2.4.12 to 2.4.14 and then got nothing but "System I/O error" errors in the logs. I took a look at http://bugzilla.cyrusimap.org/show_bug.cgi?id=3381 and noticed this: You can convert your mail directory hashing scheme from 32bit fulldirhash to 64bit fulldirhash with following commands: % tools/rehash basic % tools/rehash full Unfortunately I have almost 5TB of mail spread out on 23 different mount points. All the letters in /imap/mail are individual mount points so rehashing would mean lots of moves across the mount points which won't be quick. Is there a way to force Cyrus to use the old 32bit way, other than just removing the patch? <> Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: Questions around moving from 2.2.12 to 2.4.12
So far I am happy with the migration ... works fine! Are there any obvious parameters to change or get rid of after such a big leap (2.2.x to 2.4.x) ? I hesitate to post all my conf-files as I have one for imapd/lmtpd/popd/timsieved/cyrus Stefan Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: Disable reverse DNS lookups
Le 12/03/2012 20:01, Bron Gondwana a écrit :
> Yes, it looks like a great idea. The problem I had with the patch is
> that it only does imapd and pop3d, but there are other daemons that do
> reverse lookups. I think I'd like to factor out the reverse lookup
> into one centralised function.
This would be a wonderful solution.
I liked very much how the cyrusdb-Functions are realised to acces
skiplist and other db backends, something like that for dns or network
in general would ne very nice.
Pascal
--
Pascal Gienger Jabber/XMPP/Mail: pascal.gien...@uni-konstanz.de
University of Konstanz, IT Services Department ("Rechenzentrum")
Building V, Room V404, Phone +49 7531 88 5048, Fax +49 7531 88 3739
G+: https://plus.google.com/114525323843315818983/
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: Disable reverse DNS lookups
On Mon, Mar 12, 2012 at 03:49:30PM -0300, Lucas Zinato Carraro wrote: > I found in maillist history this thread: > > http://lists.andrew.cmu.edu/pipermail/info-cyrus/2010-September/033392.html > > This patch is already implemented in newer cyrus versions ( 2.4.X )? I was looking at the bug for it just the other day... I think I was going to update it in fact. Yes, it looks like a great idea. The problem I had with the patch is that it only does imapd and pop3d, but there are other daemons that do reverse lookups. I think I'd like to factor out the reverse lookup into one centralised function. (actually, I'd like someone else to do it ;) ) Bron. Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Disable reverse DNS lookups
I found in maillist history this thread: http://lists.andrew.cmu.edu/pipermail/info-cyrus/2010-September/033392.html This patch is already implemented in newer cyrus versions ( 2.4.X )? Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: Cyrus IMAP 2.4.14 released
Hi, On Mon, 12 Mar 2012 22:01:48 +0900, Jeroen van Meeuwen (Kolab Systems) wrote: > On 2012-03-12 12:56, OBATA Akio wrote: >> doc/changes.html and doc/text/changes in released tarball are not >> updated to 2.4.14? >> (I don't know about other document files) >> > > Hi, > > You are right, these files have not been updated with 2.4.14 release > information - we're missing a piece in our release process. These docs > have not been updated for 2.4.13 either, now that I examine them a > little closer. I feel it is good for 2.4.13, because it contains "Changes to the Cyrus IMAP Server since 2.4.12". -- OBATA Akio / ob...@lins.jp Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: Cyrus IMAP 2.4.14 released
On 2012-03-12 12:56, OBATA Akio wrote: > doc/changes.html and doc/text/changes in released tarball are not > updated to 2.4.14? > (I don't know about other document files) > Hi, You are right, these files have not been updated with 2.4.14 release information - we're missing a piece in our release process. These docs have not been updated for 2.4.13 either, now that I examine them a little closer. The information normally contained within those pages is available though; - http://www.cyrusimap.org/mediawiki/index.php/Bugs_Resolved_in_2.4.14 - http://www.cyrusimap.org/mediawiki/index.php/Bugs_Resolved_in_2.4.13 Kind regards, Jeroen van Meeuwen -- Systems Architect, Kolab Systems AG e: vanmeeuwen at kolabsys.com m: +44 74 2516 3817 w: http://www.kolabsys.com pgp: 9342 BF08 Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: Cyrus IMAP 2.4.14 released
doc/changes.html and doc/text/changes in released tarball are not updated to 2.4.14? (I don't know about other document files) On Mon, 12 Mar 2012 21:22:37 +0900, Jeroen van Meeuwen (Kolab Systems) wrote: > We are pleased to announce the release of Cyrus IMAPd 2.4.14. > > This is a stable release in the 2.4.x series. The release mainly contains bug > fixes, mostly small but significant. > > Please find an overview of all bugs resolved in this release at: > > http://www.cyrusimap.org/mediawiki/index.php/Bugs_Resolved_in_2.4.14 > > You can download via HTTP or FTP: > > http://cyrusimap.org/releases/cyrus-imapd-2.4.14.tar.gz > > ftp://ftp.cyrusimap.org/cyrus-imapd/cyrus-imapd-2.4.14.tar.gz > > Kind regards, > > Jeroen van Meeuwen > -- OBATA Akio / ob...@lins.jp Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Cyrus IMAP 2.4.14 released
We are pleased to announce the release of Cyrus IMAPd 2.4.14. This is a stable release in the 2.4.x series. The release mainly contains bug fixes, mostly small but significant. Please find an overview of all bugs resolved in this release at: http://www.cyrusimap.org/mediawiki/index.php/Bugs_Resolved_in_2.4.14 You can download via HTTP or FTP: http://cyrusimap.org/releases/cyrus-imapd-2.4.14.tar.gz ftp://ftp.cyrusimap.org/cyrus-imapd/cyrus-imapd-2.4.14.tar.gz Kind regards, Jeroen van Meeuwen -- 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/
