Re: setting up replication
Johannes, Johannes Rußek wrote: i'm trying to replicate an existing imap servers over to a new one, this is basically fedora core 6 to rhel5. i've set up the replication as per the howto and it appears to basically work. however, when sync_client reaches the point of creating a mailbox, i get the following error in the log: sync_client[30485]: CREATE received BAD response: Unexpected extra arguments to Create Do you have the same mailbox partitions set up in imapd.conf on the master and the slave? Regards, Dave. David Mayo Networks/Systems Administrator University of Bath Computing Services, UK 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: ANNOTATEMORE = METADATA and rfc 5464
On Tue, Nov 17, 2009 at 06:37:13PM -0500, Ken Murchison wrote: Bron Gondwana wrote: On Tue, Nov 17, 2009 at 04:17:51PM -0500, Ken Murchison wrote: Bron Gondwana wrote: On Tue, Nov 17, 2009 at 09:03:11AM -0500, Ken Murchison wrote: What is your new format proposal? I'll see :) Not sure yet - but mainly not sizeof(unsigned long)! If we make a wholesale change to the database, perhaps this might be something we put in the 2.4 branch. It already has some partial/complete extensions like QRESYNC, LIST-EXTENDED, URLAUTH=BINARY and COMPRESS (which I backported to 2.3). I was also thinking that although the charset changes have been fully tested at Fastmail that it too might be a candidate for 2.4. Yeah, fair enough! I did commit them to CVS, but it's easy enough to back them out and commit to a branch instead. Do we have a roadmap for what else people want on the 2.4 branch? I'd be happy to put a bit more effort into polishing up those features that are there so we can ship a 2.4 soonish. Say by April next year, which gives us 6 months to prepare. My original vision for 2.4 was to be compliant with the LEMONADE v2 profile. Sounds like a good plan :) At this point is can morph into anything we want. Some of the 2.4 features required changes that I felt were too in depth to put into a relatively stable 2.3. I'm pretty close to having the time to dive back into the 2.4 code. The first thing that needs to be done is to merge all of the new 2.3 stuff into 2.4. Sure. I'm happy to put the more unstable stuff (even including the charset changes) into 2.4. I just want to have some idea that they won't get stuck waiting for some lemonade scented towlettes forever. If we commit to something like 2.4 will ship with whatever features we have ready in April 2010 then we have a decent timeline to figure out what we'll actually have time to support, and focus on getting that stable. In particular, that's a good time for all the format changes to land all at once, and potentially new defaults for a bunch of config values that have occured over the years. In particular things like collation order for the mailboxes.db should just be fixed. Dump and restore your DB and do it this way! In general I'd like to simplify configuration where possible even at the expense of backwards compatibility. We could have a config_version: 2.4 key which needs to be changed over major version differences, and keep configs compatible within the major versions. (2.x that is) 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: ANNOTATEMORE = METADATA and rfc 5464
Hi Bron, thanks for looking into the annotation/metadata stuff. So I'm thinking: create a new metadata.db, require a conversion on upgrade from annotations.db. I had a look, and none of our servers had ANY annotations until I added a /comment to my INBOX for testing. Just to be sure: do you plan to change the current annotatemore-code so that it will access the new database and an old client still using annotatemore will still work? Does anybody out there use annotations much? Does anybody know any code that would be broken by changing the way annotations are done? Given that there is code to convert the old annotations.db to metadata.db I don't see any problems for us. Our backup code will probably need some tweaking, but when the new db format is more sane than the current mess I don't see any problems with that. Kind regards, Gerd -- Address (better: trap) for people I really don't want to get mail from: jo...@cactusamerica.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
moving a cyrus folder and reconstruct?
hi all, i've been migrating from smartermail to cyrus using imapsync that has worked, yet, i end up with an Inbox child of Inbox. i'd like to goto the file system and just move the folders around and delete the 2nd Inbox, however, cyrus barfs. is there a way to move the mail folders using a script? many thanks mcq 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: setting up replication
On Tuesday 17 November 2009 @ 13:11, Patrick Boutilier wrote: On 11/17/2009 01:34 PM, Johannes Rußek wrote: Nope, i'm not. is this necessary? it's 2.3.9 on the master and 2.3.7 on the replica. if that's the problem i will take care of that first. They are both 2.3.x so that shouldn't be a problem. However those versions are relatively old. 2.3.15 is the latest in the 2.3 series. I just setup replication a couple of weeks ago and haven't seen any of those errors. I believe there were major changes in the sync protocol between 2.3.7 2.3.9, enough to probably make them incompatible. Although, I would also recommend running 2.3.15 over anything older. -Brian 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: moving a cyrus folder and reconstruct?
On Wed, 18 Nov 2009 15:49:50 +0100, mayak-cq ma...@australsat.com wrote: hi all, hello :) i've been migrating from smartermail to cyrus using imapsync that has worked, yet, i end up with an Inbox child of Inbox. i'd like to goto the file system and just move the folders around and delete the 2nd Inbox, however, cyrus barfs. is there a way to move the mail folders using a script? when I have to move mailboxes, I do the following : http://wiki.linuxwall.info/doku.php/en:ressources:dossiers:cyrus:migrate_maiboxes hope it helps, julien many thanks mcq 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: setting up replication
Hi Brian, thanks for the recommendation, but you have to note that this is RHEL cyrus, which means there are a lot of backports in it.. As usual, RH version is not the same as upstream version. Also with RH you are pretty much bound to what you get :) I'll get both machines to RHEL's 2.3.9 first, then try replication again. Thanks everybody, Johannes Am Mittwoch, den 18.11.2009, 10:43 -0500 schrieb Brian Awood: On Tuesday 17 November 2009 @ 13:11, Patrick Boutilier wrote: On 11/17/2009 01:34 PM, Johannes Rußek wrote: Nope, i'm not. is this necessary? it's 2.3.9 on the master and 2.3.7 on the replica. if that's the problem i will take care of that first. They are both 2.3.x so that shouldn't be a problem. However those versions are relatively old. 2.3.15 is the latest in the 2.3 series. I just setup replication a couple of weeks ago and haven't seen any of those errors. I believe there were major changes in the sync protocol between 2.3.7 2.3.9, enough to probably make them incompatible. Although, I would also recommend running 2.3.15 over anything older. -Brian 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 -- Best Regards, Johannes Rußek Linux/UNIX Administration win.rar GmbH Schumannstr. 17 10117 Berlin Germany www.win-rar.com(website) rus...@win-rar.com (e-mail) +49 30 28886758 (tel Zentrale) +49 30 28884514 (fax) win.rar GmbH Berlin |HR B-Nr. 109885 B Management: Öncül Kaya, Burak Canboy |Amtsgericht |Charlottenburg 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: setting up replication
On 11/18/2009 01:15 PM, Johannes Rußek wrote: Hi Brian, thanks for the recommendation, but you have to note that this is RHEL cyrus, which means there are a lot of backports in it.. Usually security fixes though. As usual, RH version is not the same as upstream version. Also with RH you are pretty much bound to what you get :) You could try this source RPM: http://www.invoca.ch/pub/packages/cyrus-imapd/cyrus-imapd-2.3.15-4.src.rpm I'll get both machines to RHEL's 2.3.9 first, then try replication again. Thanks everybody, Johannes Am Mittwoch, den 18.11.2009, 10:43 -0500 schrieb Brian Awood: On Tuesday 17 November 2009 @ 13:11, Patrick Boutilier wrote: On 11/17/2009 01:34 PM, Johannes Rußek wrote: Nope, i'm not. is this necessary? it's 2.3.9 on the master and 2.3.7 on the replica. if that's the problem i will take care of that first. They are both 2.3.x so that shouldn't be a problem. However those versions are relatively old. 2.3.15 is the latest in the 2.3 series. I just setup replication a couple of weeks ago and haven't seen any of those errors. I believe there were major changes in the sync protocol between 2.3.7 2.3.9, enough to probably make them incompatible. Although, I would also recommend running 2.3.15 over anything older. -Brian 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
