RE: Patches used at FastMail.FM
Have you checked into adding the patches in Bug 2805? (they eliminate some compiler warnings) https://bugzilla.andrew.cmu.edu/show_bug.cgi?id=2805 -Original Message- From: [EMAIL PROTECTED] [mailto:info-cyrus- [EMAIL PROTECTED] On Behalf Of Ken Murchison Sent: Tuesday, January 09, 2007 12:49 PM To: Bron Gondwana Cc: Info Cyrus Subject: Re: Patches used at FastMail.FM Bron Gondwana wrote: It's been a while since I posted our list of patches, and there have been a couple of changes since then. I'm generating the site from a script and a bunch of patch description files now, so I should be able to keep it up to date. Feel free to use any of these patches, and Ken - feel free to include anything that looks good into upstream! Some of these patches are quite specific to our site, but many of the are more generally useful as well. After a quick discussion with Jeff, I just committed the following patches to CVS. Others may follow for a later 2.3 release or rolled into 2.4. Disable anyone ACL cyr_dbtool - utility for manipulating databases Cyrus expire - keep going Custom is_digit implementation Allow plaintext auth for sync_client (not committed, but can be accomplished with '-p' option) Randomise connection timeout Replication sync_client - only connect once Replication - batch messages in a folder (batch size is controlled by sync_batch_size option) Replication - Check lastuid in seen database -- 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
Re: Patches used at FastMail.FM
http://cyrus.brong.fastmail.fm/cyrus-plainsync-2.3.3.diff Why not just run 'sync_server -p 2' ? I believe that I added the 'p' option to all services for just this reason. -- 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: Patches used at FastMail.FM
Bron Gondwana wrote: It's been a while since I posted our list of patches, and there have been a couple of changes since then. I'm generating the site from a script and a bunch of patch description files now, so I should be able to keep it up to date. Feel free to use any of these patches, and Ken - feel free to include anything that looks good into upstream! Some of these patches are quite specific to our site, but many of the are more generally useful as well. After a quick discussion with Jeff, I just committed the following patches to CVS. Others may follow for a later 2.3 release or rolled into 2.4. Disable anyone ACL cyr_dbtool - utility for manipulating databases Cyrus expire - keep going Custom is_digit implementation Allow plaintext auth for sync_client (not committed, but can be accomplished with '-p' option) Randomise connection timeout Replication sync_client - only connect once Replication - batch messages in a folder (batch size is controlled by sync_batch_size option) Replication - Check lastuid in seen database -- 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: Patches used at FastMail.FM
Bron Gondwana wrote: On Tue, 09 Jan 2007 08:52:21 -0500, Ken Murchison [EMAIL PROTECTED] said: http://cyrus.brong.fastmail.fm/cyrus-plainsync-2.3.3.diff Why not just run 'sync_server -p 2' ? I believe that I added the 'p' option to all services for just this reason. It didn't work in my testing for some reason. I'm happy to try it out again, I tested this morning before I responded (so as not to put my foot in my mouth) and it worked as expected. I think that the -p option only appeared right before 2.3.7, so it may not have been available when you wrote your patch. -- 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: Patches used at FastMail.FM
On Tue, 09 Jan 2007 12:49:25 -0500, Ken Murchison [EMAIL PROTECTED] said:
Bron Gondwana wrote:
It's been a while since I posted our list of patches, and there have been
a couple of changes since then.
I'm generating the site from a script and a bunch of patch description files
now, so I should be able to keep it up to date.
Feel free to use any of these patches, and Ken - feel free to include
anything that looks good into upstream! Some of these patches are quite
specific to our site, but many of the are more generally useful as well.
After a quick discussion with Jeff, I just committed the following
patches to CVS. Others may follow for a later 2.3 release or rolled
into 2.4.
[...]
Wow, makes me wish I'd got sorted and split out the patch that you accepted
about half of already so I could ask why the other half didn't go in. I've
attached the entire patch now. I'm leaving on vacation in a couple of hours
so my wife would kill me if I spent any longer on this now...
This is the one that stops cyr_expire performing so many index opens and
closes by checking if the cyrus_expunge file exists first. You appear to
have accepted the code that does that, but not the code for the additional
option (-a) which skips reading the annotations database. I haven't
actually done a performance comparison, so I can't guarantee that it is
a big performance win, but the strace I did showed about 4 db lookups per
folder (because it walked back up the tree). We don't use annotations at
all, at least not for the purpose of controlling expiry, so it's somewhat
of a performance saving.
Anyway, thanks heaps for looking at those patches and taking so many of them.
It's always good to reduce our distance from upstream. We are still
going to be patching cyrus a little bit (you'll notice that I didn't include
cyrus-fastmailsecrects.diff on the website!) - at least until we find some
other way to add our s00per-s33krit encrypted header to messages which
allows us to know which user (or which user's sieve script) generated a
message without leaking their identity to any third party.
Regards,
Bron.
--
Bron Gondwana
[EMAIL PROTECTED]
diff -ur --new-file cyrus-imapd-cvs.orig/imap/cyr_expire.c
cyrus-imapd-cvs/imap/cyr_expire.c
--- cyrus-imapd-cvs.orig/imap/cyr_expire.c 2005-12-15 08:21:16.0
-0500
+++ cyrus-imapd-cvs/imap/cyr_expire.c 2006-10-11 04:26:12.0 -0400
@@ -73,7 +73,7 @@
void usage(void)
{
fprintf(stderr,
- cyr_expire [-C altconfig] -E days [-X expunge-days] [-v]\n);
+ cyr_expire [-C altconfig] -E days [-X expunge-days] [-a]
[-v]\n);
exit(-1);
}
@@ -86,6 +86,7 @@
unsigned long messages;
unsigned long deleted;
int verbose;
+int skip_annotate;
};
/*
@@ -143,26 +144,32 @@
* since mailboxes inherit /vendor/cmu/cyrus-imapd/expire,
* we need to iterate all the way up to (server entry)
*/
-while (1) {
- r = annotatemore_lookup(buf, /vendor/cmu/cyrus-imapd/expire, ,
- attrib);
-
- if (r ||/* error */
- attrib.value || /* found an entry */
- !buf[0] || /* done recursing */
- !strcmp(buf+domainlen, user)) { /* server entry doesn't apply
- to personal mailboxes */
- break;
- }
-
- p = strrchr(buf, '.'); /* find parent mailbox */
-
- if (p (p - buf domainlen)) /* don't split subdomain */
- *p = '\0';
- else if (!buf[domainlen]) /* server entry */
- buf[0] = '\0';
- else/* domain entry */
- buf[domainlen] = '\0';
+if (erock-skip_annotate) {
+ /* we don't want to check for annotations, so we didn't find any */
+ attrib.value = 0;
+}
+else {
+while (1) {
+ r = annotatemore_lookup(buf, /vendor/cmu/cyrus-imapd/expire, ,
+ attrib);
+
+ if (r ||/* error */
+ attrib.value || /* found an entry */
+ !buf[0] || /* done recursing */
+ !strcmp(buf+domainlen, user)) { /* server entry doesn't
apply
+ to personal mailboxes */
+ break;
+ }
+
+ p = strrchr(buf, '.'); /* find parent mailbox
*/
+
+ if (p (p - buf domainlen)) /* don't split
subdomain */
+ *p = '\0';
+ else if (!buf[domainlen]) /* server entry */
+ buf[0] = '\0';
+ else/* domain entry */
+ buf[domainlen] = '\0';
+}
}
if (!r
Re: Patches used at FastMail.FM
On Tue, 9 Jan 2007, Ken Murchison wrote: Disable anyone ACL the usual reason for allowing the anyone ACL is to allow for + addressing to work. is there another way to do this? in most cases I think that a global 'allow + addressing' config option is really more appropriate then having to configure things on a per-folder basis, possibly with a 'no, don't allow + addressing to this folder' override. David Lang 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: Patches used at FastMail.FM
the usual reason for allowing the anyone ACL is to allow for + addressing to work. is there another way to do this? The admin user can still set the anyone acl, it's just non-admin users can't change/set it. The way we do this to allow + addressing is when we create the users top level folder, we set the anyone p acl on it, and any new folders created after that by the user automatically inherit it. Rob 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: Patches used at FastMail.FM
On Wed, 10 Jan 2007, Rob Mueller wrote: the usual reason for allowing the anyone ACL is to allow for + addressing to work. is there another way to do this? The admin user can still set the anyone acl, it's just non-admin users can't change/set it. The way we do this to allow + addressing is when we create the users top level folder, we set the anyone p acl on it, and any new folders created after that by the user automatically inherit it. but this is in conflict with the the idea that in a large installation of people who don't know each other the 'anyone' permission doesn't make sense. what is really desired for + addressing is to say that messages that arrive via the lmtp interface are allowed to write to all folders (not just the inbox folders) without allowing other users on the system to write arbatrary data to other people's folders via the IMAP interface. at least if it's arriving via the lmtp interface you have reason to believe that it's been (somewhat) validated by your MTA. David Lang 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: Patches used at FastMail.FM
but this is in conflict with the the idea that in a large installation of people who don't know each other the 'anyone' permission doesn't make sense. what is really desired for + addressing is to say that messages that arrive via the lmtp interface are allowed to write to all folders (not just the inbox folders) without allowing other users on the system to write arbatrary data to other people's folders via the IMAP interface. at least if it's arriving via the lmtp interface you have reason to believe that it's been (somewhat) validated by your MTA. That's really what the p permission is all about: p - post (send mail to submission address for mailbox, not enforced by IMAP4 itself) So setting anyone p means that email via LMTP can be put into any persons folder by the delivery agent, but that folder isn't visible or accessible via any IMAP commands. At least that how I believe it works, and what we've observed. Maybe Ken can clarify? Rob 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: Patches used at FastMail.FM
On Wed, 10 Jan 2007, Rob Mueller wrote: but this is in conflict with the the idea that in a large installation of people who don't know each other the 'anyone' permission doesn't make sense. what is really desired for + addressing is to say that messages that arrive via the lmtp interface are allowed to write to all folders (not just the inbox folders) without allowing other users on the system to write arbatrary data to other people's folders via the IMAP interface. at least if it's arriving via the lmtp interface you have reason to believe that it's been (somewhat) validated by your MTA. That's really what the p permission is all about: p - post (send mail to submission address for mailbox, not enforced by IMAP4 itself) So setting anyone p means that email via LMTP can be put into any persons folder by the delivery agent, but that folder isn't visible or accessible via any IMAP commands. At least that how I believe it works, and what we've observed. Maybe Ken can clarify? Ok, I thought that 'post' pre-dated lmtp and was the IMAP function to write a message into the folder. i.e. a program like imapsync would need the 'p' permission to write the messages, (but would need other permissions to check for messages, set flags, etc) I'll play around with things a bit while waiting for clarification. David Lang 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: Patches used at FastMail.FM
Ok, I thought that 'post' pre-dated lmtp and was the IMAP function to write a message into the folder. i.e. a program like imapsync would need the 'p' permission to write the messages, (but would need other permissions to check for messages, set flags, etc) I think the only way to add a message to a folder via IMAP is APPEND or COPY, which is what the i right controls. i - insert (perform APPEND, COPY into mailbox) Rob 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: Patches used at FastMail.FM
Rob Mueller wrote: but this is in conflict with the the idea that in a large installation of people who don't know each other the 'anyone' permission doesn't make sense. what is really desired for + addressing is to say that messages that arrive via the lmtp interface are allowed to write to all folders (not just the inbox folders) without allowing other users on the system to write arbatrary data to other people's folders via the IMAP interface. at least if it's arriving via the lmtp interface you have reason to believe that it's been (somewhat) validated by your MTA. That's really what the p permission is all about: p - post (send mail to submission address for mailbox, not enforced by IMAP4 itself) So setting anyone p means that email via LMTP can be put into any persons folder by the delivery agent, but that folder isn't visible or accessible via any IMAP commands. At least that how I believe it works, and what we've observed. Maybe Ken can clarify? Correct. 'p' is only used by lmtpd and nntpd, not by imapd or pop3d. -- 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: Patches used at FastMail.FM
Rob Mueller wrote: Ok, I thought that 'post' pre-dated lmtp and was the IMAP function to write a message into the folder. i.e. a program like imapsync would need the 'p' permission to write the messages, (but would need other permissions to check for messages, set flags, etc) I think the only way to add a message to a folder via IMAP is APPEND or COPY, which is what the i right controls. i - insert (perform APPEND, COPY into mailbox) Correct again. -- 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: Patches used at FastMail.FM
Bron Gondwana wrote: It's been a while since I posted our list of patches, and there have been a couple of changes since then. I'm generating the site from a script and a bunch of patch description files now, so I should be able to keep it up to date. Feel free to use any of these patches, and Ken - feel free to include anything that looks good into upstream! Some of these patches are quite specific to our site, but many of the are more generally useful as well. I'm in the process of re-building against the new HEAD (previously the 2.3 branch) because we want some of the fixes that have gone in. It would be nice if there was another 2.3 release that checkpointed some of those in time (*hint*, *hint*) but we're doing OK tracking CVS. Jeff and I have already discussed pushing out a 2.3 release soon -- as soon as we iron out all of the wrinkles in our 2.3 deployment on campus. We found a few small buglets in the IMAP proxy code that we didn't expect. Either nobody else has a 2.3 Murder running, or they didn't notice the random (infrequent) core dumps. -- 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: Patches used at FastMail.FM
Simon Matter wrote: It's been a while since I posted our list of patches, and there have been a couple of changes since then. I'm generating the site from a script and a bunch of patch description files now, so I should be able to keep it up to date. Feel free to use any of these patches, and Ken - feel free to include anything that looks good into upstream! Some of these patches are quite specific to our site, but many of the are more generally useful as well. I'm also interested to hear whether there are any plans to include some of those patches into upstream. I say this because I'd like to include some of them into my rpm packages but I would be happier if they were included in upstream so we don't get compatibility issues in the future. Al lot of them look reasonable, but I'd rather not hold up another 2.3 release while I study them. -- 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: Patches used at FastMail.FM
* Ken Murchison [EMAIL PROTECTED] [20070108 08:34]: Jeff and I have already discussed pushing out a 2.3 release soon -- as soon as we iron out all of the wrinkles in our 2.3 deployment on campus. We found a few small buglets in the IMAP proxy code that we didn't expect. Either nobody else has a 2.3 Murder running, or they didn't notice the random (infrequent) core dumps. /me waves. I just turned up a 2.3.7 based murder and *have* noticed those core dumps. Please let me know if I can provide you with any pertinent information. Ben signature.asc Description: Digital signature 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: Patches used at FastMail.FM
Ben Poliakoff wrote: * Ken Murchison [EMAIL PROTECTED] [20070108 08:34]: Jeff and I have already discussed pushing out a 2.3 release soon -- as soon as we iron out all of the wrinkles in our 2.3 deployment on campus. We found a few small buglets in the IMAP proxy code that we didn't expect. Either nobody else has a 2.3 Murder running, or they didn't notice the random (infrequent) core dumps. /me waves. I just turned up a 2.3.7 based murder and *have* noticed those core dumps. Please let me know if I can provide you with any pertinent information. The bugs that we found have been fixed in CVS. I'm guessing that most of your cores are occurring in FD_SET() in protgroup_select() in lib/prot.c or in backend_timeout() in imap/backend.c -- 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: Patches used at FastMail.FM
Hi, on 08.01.2007 17:23 Ken Murchison said the following: Jeff and I have already discussed pushing out a 2.3 release soon -- as soon as we iron out all of the wrinkles in our 2.3 deployment on campus. We found a few small buglets in the IMAP proxy code that we didn't expect. Either nobody else has a 2.3 Murder running, or they didn't notice the random (infrequent) core dumps. I setup a unified muder with Cyrus IMAP 2.3.7 for a customer with 500 accounts and 1 mailboxes. It's still in testing, all the accounts have not been migrated yet, but I haven't notice any annoying or blocking coredump. I too wonder who runs Cyrus IMAP 2.3 Murder, because hardly anybody ever answers my questions here and I have to reply to myself ;) Regards, -- Farzad FARID [EMAIL PROTECTED] Architecte Open Source / Pragmatic Source http://www.pragmatic-source.com/ 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: Patches used at FastMail.FM
On Mon, 8 Jan 2007, Farzad FARID wrote: Hi, on 08.01.2007 17:23 Ken Murchison said the following: Jeff and I have already discussed pushing out a 2.3 release soon -- as soon as we iron out all of the wrinkles in our 2.3 deployment on campus. We found a few small buglets in the IMAP proxy code that we didn't expect. Either nobody else has a 2.3 Murder running, or they didn't notice the random (infrequent) core dumps. I setup a unified muder with Cyrus IMAP 2.3.7 for a customer with 500 accounts and 1 mailboxes. It's still in testing, all the accounts have not been migrated yet, but I haven't notice any annoying or blocking coredump. I too wonder who runs Cyrus IMAP 2.3 Murder, because hardly anybody ever answers my questions here and I have to reply to myself ;) I've been staying with v2.2.13 Murder until I see the release name change from Beta to Stable. :) Andy 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: Patches used at FastMail.FM
On 08 Jan 2007, at 11:23, Ken Murchison wrote: We found a few small buglets in the IMAP proxy code that we didn't expect. Either nobody else has a 2.3 Murder running, or they didn't notice the random (infrequent) core dumps. We're (UMich) continuing to run 2.3 replicated backends with 2.2 frontend and mupdate master. We're planning to port our 2.2 proxy mupdate change to 2.3 in the coming months. :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: Patches used at FastMail.FM
On Mon, 08 Jan 2007 11:23:50 -0500, Ken Murchison [EMAIL PROTECTED] said: Bron Gondwana wrote: It's been a while since I posted our list of patches, and there have been a couple of changes since then. I'm generating the site from a script and a bunch of patch description files now, so I should be able to keep it up to date. Feel free to use any of these patches, and Ken - feel free to include anything that looks good into upstream! Some of these patches are quite specific to our site, but many of the are more generally useful as well. I'm in the process of re-building against the new HEAD (previously the 2.3 branch) because we want some of the fixes that have gone in. It would be nice if there was another 2.3 release that checkpointed some of those in time (*hint*, *hint*) but we're doing OK tracking CVS. Jeff and I have already discussed pushing out a 2.3 release soon -- as soon as we iron out all of the wrinkles in our 2.3 deployment on campus. We found a few small buglets in the IMAP proxy code that we didn't expect. Either nobody else has a 2.3 Murder running, or they didn't notice the random (infrequent) core dumps. There's only one that I'd really want to push for inclusion soon, and that's: http://cyrus.brong.fastmail.fm/cyrus-sync-connectonce-2.3.7.diff it's not absolutely the shortest diff, but it should only take 10-15 minutes to review since it does very little. This makes replication master startup a lot less painful if your replica is down. The other diff that's very small and we quite like is: http://cyrus.brong.fastmail.fm/cyrus-reusetimeout-2.3.6.diff Which reduces the IO hit on an IMAP server if all its connections get dropped at once due to network issues by spreading out the disconnect timeouts - but that's less of a priority. The first one was necessary to make replication even usable in our environment (master IMAP servers hanging at (re)start sucks). Bron. -- Bron Gondwana [EMAIL PROTECTED] 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: Patches used at FastMail.FM
Jeff and I have already discussed pushing out a 2.3 release soon -- as soon as we iron out all of the wrinkles in our 2.3 deployment on campus. We found a few small buglets in the IMAP proxy code that we didn't expect. Either nobody else has a 2.3 Murder running, or they didn't notice the random (infrequent) core dumps. I'd also consider these bug fixes that should be included to make replication stable and useable for all users, even with large folders: http://cyrus.brong.fastmail.fm/cyrus-syncrecent-cvs.diff http://cyrus.brong.fastmail.fm/cyrus-sync-upload-batch-2.3.7.diff Rob 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: Patches used at FastMail.FM
It's been a while since I posted our list of patches, and there have been a couple of changes since then. I'm generating the site from a script and a bunch of patch description files now, so I should be able to keep it up to date. Feel free to use any of these patches, and Ken - feel free to include anything that looks good into upstream! Some of these patches are quite specific to our site, but many of the are more generally useful as well. I'm also interested to hear whether there are any plans to include some of those patches into upstream. I say this because I'd like to include some of them into my rpm packages but I would be happier if they were included in upstream so we don't get compatibility issues in the future. 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
