Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: "Bruno Hertz" <spammer.go.home@gmail.com>
Subject: Re: Migrating IMAP (nnimap) servers?
Date: Thu, 31 Mar 2005 00:03:04 +0200	[thread overview]
Message-ID: <m3oed0dc6f.fsf@caruso.quasi.local> (raw)
In-Reply-To: <87sm2cyhs3.fsf@cenderis.demon.co.uk>

Bruce Stephens <bruce+usenet@cenderis.demon.co.uk> writes:

> 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.)

I'm not totally sure, so additional comments are welcome, but afaik all
the marks Gnus maintains locally for news are stored as imap flags on
the server, like read, seen, ticked and even dormant (might depend on
your Gnus version, though). So just switching servers should go alright
without further actions in this regard, if the flags are migrated, too.

What I'm not sure about is what to do with possibly cached articles.
Maybe somebody else can tell more?

Regards, Bruno.


  reply	other threads:[~2005-03-30 22:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-30 20:56 Bruce Stephens
2005-03-30 22:03 ` Bruno Hertz [this message]
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=m3oed0dc6f.fsf@caruso.quasi.local \
    --to=spammer.go.home@gmail.com \
    /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).