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 16:15:19 +0200	[thread overview]
Message-ID: <m364z7dhqg.fsf@caruso.quasi.local> (raw)
In-Reply-To: <87d5tg9leg.fsf@cenderis.demon.co.uk>

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

> "Bruno Hertz" <spammer.go.home@gmail.com> writes:
>
> [...]
>
>> 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.
>
> That sounds hopeful.
>
>> What I'm not sure about is what to do with possibly cached articles.
>> Maybe somebody else can tell more?
>
> I've not used those (with imap, anyway).  I'd guess that there'd be an
> issue with those---presumably it uses some kind of numbering, and
> presumably that's the server-specific article number.

Actually, thinking about it, you don't even need to 'switch', since your
mail servers are (presumably) part of your secondary select methods.

I.e. you could just add the new server there, subscribe to your folders
when it's online and see what it gives. If the old server is down by then,
Gnus will put it offline anyway, and you could remove it from your
secondary selects then or maybe even kill the subscribed folders one
by one and then kill resp. remove the server. So yes, I'm pretty sure
it should be no problem, especially when the migration is done
properly on the server side.

Finally, if you're concerned about loosing mail on the server side,
you could pull it before migration yourself to either maildir format
(fetchmail, procmail - don't know what happens with the flags in this
case though) or even to another imap server of your choice (mailutil
from uw-mailutils).

Regards, Bruno.


  reply	other threads:[~2005-03-31 14:15 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
2005-03-31 10:09   ` Bruce Stephens
2005-03-31 14:15     ` Bruno Hertz [this message]
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=m364z7dhqg.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).