Re: Migrating from Dovecot to Cyrus
Oooh... I have a bunch of code which speaks replication protocol that does that which we used for the Pobox => FastMail migration. I'll see if I can dig it out and publish it. There's a setting to make Cyrus use Dovecot-compatible UIDLs. Bron. On Fri, 28 Apr 2017, at 00:01, Matt Campbell wrote: > Hello: > > What is the recommended way to migrate mailboxes from Dovecot to Cyrus, > ideally preserving IMAP UIDs and POP3 UIDLs? This seems like it should > be a FAQ, but I haven't been able to find a good answer. > > Thanks, > Matt > > Cyrus Home Page: http://www.cyrusimap.org/ > List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ > To Unsubscribe: > https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus -- Bron Gondwana br...@fastmail.fm Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: Migrating from Dovecot to Cyrus
I have used imapsync to migrate clients mail to my servers running cyrus. I am not sure if the UIDs are preserved but I have not had any problems with clients. That being said they are usually changing there credentials and setting up a new account with the move so some issues that would show up with a conversion of the mailstore could be hidden. On 04/27/2017 10:01 AM, Matt Campbell wrote: Hello: What is the recommended way to migrate mailboxes from Dovecot to Cyrus, ideally preserving IMAP UIDs and POP3 UIDLs? This seems like it should be a FAQ, but I haven't been able to find a good answer. Thanks, Matt Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus -- Alvin Starr || voice: (905)513-7688 Netvel Inc. || Cell: (416)806-0133 al...@netvel.net || Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Migrating from Dovecot to Cyrus
Hello: What is the recommended way to migrate mailboxes from Dovecot to Cyrus, ideally preserving IMAP UIDs and POP3 UIDLs? This seems like it should be a FAQ, but I haven't been able to find a good answer. Thanks, Matt Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: migrating from dovecot to cyrus
I always say Cyrus is the best open IMAP server that I have ever used. It implements openldap to ease most of my system setup problems. You may consider using imapsync to re-match the imap mail flags and re-subscribe the mail folders. Patrick - Original Message - From: "Marten Lehmann" <[EMAIL PROTECTED]> Cc: Sent: Tuesday, June 27, 2006 8:49 PM Subject: Re: migrating from dovecot to cyrus Hello, Just out of curiosity, what kind of performance problems at what load do you have. It was claimed that dovecot is really fast and we plan to evaluate it in the near future for some projects so any hints where to dig are welcome. the difference is, that cyrus handles a lot of things while the mail is being delivered, which saves a lot of time. We had to split the incoming mailserver (smtp) and the pop3/imap server because one server couldn't handle the load any longer. Example delivery with exim+dovecot: To check the quota, exim has to count all messages (files) in all directories in the maildir (very timeconsuming with NFS mounted maildirs). Then the message is delivered to maildir/tmp and moved to maildir/new (another two NFS operations). When a user is connecting to IMAP now, dovecot has to look through all directories within the maildir of files or gone, new ones appeared and build the cache and index accordingly. This is done locally on the disk, so it is a bit faster, but it is time consuming on big maildirs anyway. Now dovecot can start serving the new message. Example delivery with exim+cyrus: Exim sends to message to cyrus via unix socket or tcp socket. The rest is done locally on the cyrus backend server: Checking for quota Updating indizes Possibly notifying an existing imap-connection about the new message So the delivery is very fast, because cyrus doesn't have to look through all messages to check the quota: It can be looked up in the index. When the user is connecting to IMAP, the index is already prepared, cyrus doesn't have to look for changes in the maildir at this stage so it can serve the new message immediately. In small setups with everything on one server, exim (or any other mta) + dovecot should work fine, while cyrus is maybe a bit more complicated to setup. But with bigger setups (or expected growth in the future) cyrus and its option of cyrus murder should scale better. Regards Marten Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: migrating from dovecot to cyrus
Hello, Just out of curiosity, what kind of performance problems at what load do you have. It was claimed that dovecot is really fast and we plan to evaluate it in the near future for some projects so any hints where to dig are welcome. the difference is, that cyrus handles a lot of things while the mail is being delivered, which saves a lot of time. We had to split the incoming mailserver (smtp) and the pop3/imap server because one server couldn't handle the load any longer. Example delivery with exim+dovecot: To check the quota, exim has to count all messages (files) in all directories in the maildir (very timeconsuming with NFS mounted maildirs). Then the message is delivered to maildir/tmp and moved to maildir/new (another two NFS operations). When a user is connecting to IMAP now, dovecot has to look through all directories within the maildir of files or gone, new ones appeared and build the cache and index accordingly. This is done locally on the disk, so it is a bit faster, but it is time consuming on big maildirs anyway. Now dovecot can start serving the new message. Example delivery with exim+cyrus: Exim sends to message to cyrus via unix socket or tcp socket. The rest is done locally on the cyrus backend server: Checking for quota Updating indizes Possibly notifying an existing imap-connection about the new message So the delivery is very fast, because cyrus doesn't have to look through all messages to check the quota: It can be looked up in the index. When the user is connecting to IMAP, the index is already prepared, cyrus doesn't have to look for changes in the maildir at this stage so it can serve the new message immediately. In small setups with everything on one server, exim (or any other mta) + dovecot should work fine, while cyrus is maybe a bit more complicated to setup. But with bigger setups (or expected growth in the future) cyrus and its option of cyrus murder should scale better. Regards Marten Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: migrating from dovecot to cyrus
On Tue, 2006-06-27 at 14:49 +0200, Marten Lehmann wrote: > Hello, > > > Just out of curiosity, what kind of performance problems at what load do > > you have. It was claimed that dovecot is really fast and we plan to > > evaluate it in the near future for some projects so any hints where to > > dig are welcome. > > the difference is, that cyrus handles a lot of things while the mail is > being delivered, which saves a lot of time. We had to split the incoming > mailserver (smtp) and the pop3/imap server because one server couldn't > handle the load any longer. > > Example delivery with exim+dovecot: > To check the quota, exim has to count all messages (files) in all > directories in the maildir (very timeconsuming with NFS mounted maildirs). > Then the message is delivered to maildir/tmp and moved to maildir/new > (another two NFS operations). > When a user is connecting to IMAP now, dovecot has to look through all > directories within the maildir of files or gone, new ones appeared and > build the cache and index accordingly. This is done locally on the disk, > so it is a bit faster, but it is time consuming on big maildirs anyway. > Now dovecot can start serving the new message. > > Example delivery with exim+cyrus: > Exim sends to message to cyrus via unix socket or tcp socket. The rest > is done locally on the cyrus backend server: > Checking for quota > Updating indizes > Possibly notifying an existing imap-connection about the new message > So the delivery is very fast, because cyrus doesn't have to look through > all messages to check the quota: It can be looked up in the index. > When the user is connecting to IMAP, the index is already prepared, > cyrus doesn't have to look for changes in the maildir at this stage so > it can serve the new message immediately. > > In small setups with everything on one server, exim (or any other mta) + > dovecot should work fine, while cyrus is maybe a bit more complicated to > setup. But with bigger setups (or expected growth in the future) cyrus > and its option of cyrus murder should scale better. > > Regards > Marten Although the comparison below includes a commercial imap server, it does give a good comparison between Cyrus and other open source imap servers. http://www.isode.com/whitepapers/mbox-benchmark.html Murray Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: migrating from dovecot to cyrus
Zitat von Marten Lehmann <[EMAIL PROTECTED]>: Hello, I'm about to migrate an pop3/imap server from dovecot to cyrus. I'm planning to use the cyrus murder cluster in the long run, but the setup is a complex. And since the migration from dovecot to cyrus shall be done very soon because of performance problems in the current setup, I guess I can start faster with the standarc cyrus. Just out of curiosity, what kind of performance problems at what load do you have. It was claimed that dovecot is really fast and we plan to evaluate it in the near future for some projects so any hints where to dig are welcome. Regards Andreas Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: migrating from dovecot to cyrus
The biggest show stopper (apart from the hard work...) is the loss of the "Seen" flag. use imapsync to re-match imap flag and subscribe the imap folder. Patrick - Original Message - From: "Ciprian Vizitiu" <[EMAIL PROTECTED]> To: Sent: Tuesday, June 27, 2006 4:32 PM Subject: RE: migrating from dovecot to cyrus > What would be an recommended way to move maildirs (one file per > message) to the cyrus storage for several thousand maildirs? FYI: cyrus doesn't use maildir format... ... True. But if you're really desperate and since the messages in maildir(s) are all separated files (not one big mbox) all you have to do is: 1. Stop maildir delivery 2. Create the same folder structure in /var/spool/whatever (probably by altering the mailbox list file via text export/import) 3. Copy all the message files from maildir (while giving them a name in the line of the ones used by Cyrus) 4. reconstruct. The biggest show stopper (apart from the hard work...) is the loss of the "Seen" flag. Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
RE: migrating from dovecot to cyrus
> > What would be an recommended way to move maildirs (one file per > > message) to the cyrus storage for several thousand maildirs? > > FYI: cyrus doesn't use maildir format... ... True. But if you're really desperate and since the messages in maildir(s) are all separated files (not one big mbox) all you have to do is: 1. Stop maildir delivery 2. Create the same folder structure in /var/spool/whatever (probably by altering the mailbox list file via text export/import) 3. Copy all the message files from maildir (while giving them a name in the line of the ones used by Cyrus) 4. reconstruct. The biggest show stopper (apart from the hard work...) is the loss of the "Seen" flag. Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: migrating from dovecot to cyrus
Marten Lehmann wrote: Hello, I'm about to migrate an pop3/imap server from dovecot to cyrus. I'm planning to use the cyrus murder cluster in the long run, but the setup is a complex. And since the migration from dovecot to cyrus shall be done very soon because of performance problems in the current setup, I guess I can start faster with the standarc cyrus. Is it possible to migrate from cyrus to cyrus murder later or do I have to setup a cyrus-murder completely separate so I cannot reuse parts of the standard cyrus setup? What would be an recommended way to move maildirs (one file per message) to the cyrus storage for several thousand maildirs? FYI: cyrus doesn't use maildir format... -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Rudy Gevaert [EMAIL PROTECTED] tel:+32 9 264 4734 Directie ICT, afd. Infrastructuur Direction ICT, Infrastructure dept. Groep Systemen Systems group Universiteit Gent Ghent University Krijgslaan 281, gebouw S9, 9000 Gent, Belgie www.UGent.be -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: migrating from dovecot to cyrus
On Mon, 26 Jun 2006, Marten Lehmann wrote: Hello, I'm about to migrate an pop3/imap server from dovecot to cyrus. I'm planning to use the cyrus murder cluster in the long run, but the setup is a complex. And since the migration from dovecot to cyrus shall be done very soon because of performance problems in the current setup, I guess I can start faster with the standarc cyrus. Is it possible to migrate from cyrus to cyrus murder later or do I have to setup a cyrus-murder completely separate so I cannot reuse parts of the standard cyrus setup? You can start with a single cyrus server and turn it into cyrus murder easily later. We just did that "migration" a week ago here, and it was totally painless. As with everything, I'd suggest doing it in a test environment first. Basically, all we did was bring up an empty murder master and 2 frontends, then we reconfigured the backend server to use murder and restarted it. Poof! :) Andy Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: migrating from dovecot to cyrus
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Marten Lehmann wrote: > What would be an recommended way to move maildirs (one file per message) > to the cyrus storage for several thousand maildirs? There was a recent thread about migration on this list; I believe the consensus was to use a tool called 'imapsync'. I've used it to move a lot of messages around before, it worked really well. - -- Chris Hilts [EMAIL PROTECTED] Say it with flowers -- Send them a triffid! -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (MingW32) iD8DBQFEoA7E98ixrK2vMtARAhL/AJoCszThwhwRv7KwdtOAF59BQeg+6wCfX6X/ kzJNlhlUzKKB/NUBctcpacY= =uUsG -END PGP SIGNATURE- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
migrating from dovecot to cyrus
Hello, I'm about to migrate an pop3/imap server from dovecot to cyrus. I'm planning to use the cyrus murder cluster in the long run, but the setup is a complex. And since the migration from dovecot to cyrus shall be done very soon because of performance problems in the current setup, I guess I can start faster with the standarc cyrus. Is it possible to migrate from cyrus to cyrus murder later or do I have to setup a cyrus-murder completely separate so I cannot reuse parts of the standard cyrus setup? What would be an recommended way to move maildirs (one file per message) to the cyrus storage for several thousand maildirs? Regards Marten Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
