From: Bruce Stephens <bruce+usenet@cenderis.demon.co.uk>
Subject: Migrating IMAP (nnimap) servers?
Date: Wed, 30 Mar 2005 21:56:28 +0100 [thread overview]
Message-ID: <87sm2cyhs3.fsf@cenderis.demon.co.uk> (raw)
Suppose I read email using foreign nnimap groups to some server, and
that I know the server's going to be changed. What can I do about
that in order to improve my chances of not losing stuff? (Let's
suppose that if the administrators offer to move existing email, that
they can accurately move IMAP tags and things.)
The manual covers changing nntp servers, but I don't see any similar
advice on moving IMAP servers. Is that because gnus doesn't really
cache much, so it all just works?
(I guess one thing I'll do regardless is make copies of email in nnml
folders, just in case.)
next reply other threads:[~2005-03-30 20:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-30 20:56 Bruce Stephens [this message]
2005-03-30 22:03 ` Bruno Hertz
2005-03-31 10:09 ` Bruce Stephens
2005-03-31 14:15 ` Bruno Hertz
2005-04-04 21:04 ` Bruce Stephens
2005-04-04 22:35 ` Bruno Hertz
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=87sm2cyhs3.fsf@cenderis.demon.co.uk \
--to=bruce+usenet@cenderis.demon.co.uk \
/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).