From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: moving mailboxes between imap accounts
Date: Thu, 26 Sep 2013 11:15:22 +0200 [thread overview]
Message-ID: <upzctxh854gl.fsf@dod.no> (raw)
In-Reply-To: <m238osdmim.fsf@ecocode.net>
>>>>> Erik Colson <eco@ecocode.net>:
> I have a lot of mailboxes which I want to move from one imap account to
> another. The only way I found was to enter each single group and then
> gnus-summary-move-article them to a new group (which Gnus will create
> happily). Doing this for every single group will take ages!
> So the question: Can this be done faster ?
I used imapsync to transfer my cyrus imapd email to dovecot back in
2008. The downside back then, was that the Gnus tick marks weren't
transferred:
http://comments.gmane.org/gmane.emacs.gnus.general/67326
My experences from the migration process:
http://permalink.gmane.org/gmane.mail.imap.dovecot/32706
However, both nnimap and imapsync may have improved since then. nnimap
in that it uses less custom marks (I think...?), and imapsync in that it
can transfer non-standard marks (hopefully).
next prev parent reply other threads:[~2013-09-26 9:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-26 8:18 Erik Colson
2013-09-26 9:15 ` Steinar Bang [this message]
2013-09-26 9:44 ` Rainer M Krug
2013-09-27 2:53 ` Dave Goldberg
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=upzctxh854gl.fsf@dod.no \
--to=sb@dod.no \
--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).