From: Daniel Pittman <daniel@rimspace.net>
To: ding@gnus.org
Subject: Re: Questions about nnimap and cyrus->dovecot migration
Date: Sun, 07 Sep 2008 12:18:01 +1000 [thread overview]
Message-ID: <8763p8puli.fsf@rimspace.net> (raw)
In-Reply-To: <87r67x48ow.fsf@dod.no>
Steinar Bang <sb@dod.no> writes:
> Does anyone here have any experience about migrating their IMAP
> folders from a cyrus to a dovecot server, and any views on the
> utilities mentioned here?
>
> http://wiki.dovecot.org/Migration/Cyrus
>
> In particular: how well will will the nnimap specific flags survive
> the transition?
Technically, imapsync was mentioned there, which I have used and found
to be uniformly excellent. It preserves all IMAP attributes by virtue
of working at the IMAP level, which is very effective, and handles
failure / interruption effectively.
Regards,
Daniel
next prev parent reply other threads:[~2008-09-07 2:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-06 15:04 Steinar Bang
2008-09-07 2:18 ` Daniel Pittman [this message]
2008-09-07 6:57 ` Steinar Bang
2008-09-07 7:09 ` Daniel Pittman
2008-09-07 10:27 ` Steinar Bang
2008-09-12 21:17 ` Steinar Bang
2008-09-13 3:26 ` Daniel Pittman
2008-09-13 13:25 ` Steinar Bang
2008-09-18 17:23 ` Steinar Bang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8763p8puli.fsf@rimspace.net \
--to=daniel@rimspace.net \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).