From: Xavier Maillard <zedek@gnu-rox.org>
Cc: ding@gnus.org
Subject: Re: POP to IMAP
Date: Thu, 03 Jul 2003 17:24:38 +0200 [thread overview]
Message-ID: <plop87adbvmy4p.fsf@gnu-rox.org> (raw)
In-Reply-To: <sgdel1b5276.fsf@occarina.pna.cwi.nl> (Lute Kamstra's message of "Mon, 30 Jun 2003 11:45:01 +0200")
[-- Attachment #1: Type: text/plain, Size: 2436 bytes --]
On 30 jun 2003, Lute Kamstra spake thusly:
> Xavier Maillard <zedek@gnu-rox.org> writes:
>
> > As the subject line say, I am about to migrate all my data from
> > POP3 to IMAP mail protocol.
> >
> > Does anyone know if there are difficulties to achieve such a task ?
>
> I just migrated from POP to IMAP and I encountered three problems.
Oh it seems I should have read people ansxers before :(
In fact I have encountered problems here too.
> Firstly, if you use nnmail-split-fancy-with-parent and still have
> your old POP (nnfolder) mail groups lying around, Gnus recognizes if
> new mails refer to a mail you have in you old archive, but tries to
> split them into a mailbox on the IMAP server with the same name as
> the group the parent is in on the old backend. This is temporary,
> but can be a bit confusing at first.
It is not my case ;)
> Secondly, I had a few problems with moving my nnfolder mail archive
> to the IMAP server; approximately one in 500 messages could not be
> copied. I got several error messages. A few were caused by
> incorrect headers (which you can just delete by editing the message),
> but most errors were due to non ASCII characters in the message
> bodies. Especially, the \201 character seemed to cause trouble.
> What usually helped was first moving the message to the same nnfolder
> group is was already in and then trying to copy it to the IMAP
> server. If that didn't work, editing a message (e) and saving it
> (C-c C-c) worked for me as it removed the troublesome characters.
I have encountered the same problem here with a few messages too. The
trick used there was to edit each of 'em manually and remove/correct
the errorneous part.
> Thirdly, it took quite some time to move all my archived messages to
> the IMAP server. I had to go into every group (C-u RET), select all
> messages (M P b), and move (B m) them an IMAP group. With the number
> of mail groups I accumulated over the years, this took quit some
> time. I would be nice if there were an easier way to do this. Maybe
> there is, but I just don't know about it.
Thanx for the hint ;) I have a big group (3500 msg) here to move into the IMAP
server so may be of interest for me :)
zeDek
--
http://www.gnusfr.org -- French Gnus user site
Anti-war disclaimer:
"Bombing for peace is like fucking for virginity"
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
prev parent reply other threads:[~2003-07-03 15:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-27 9:25 Xavier Maillard
2003-06-30 9:45 ` Lute Kamstra
2003-07-01 13:33 ` Reiner Steib
2003-07-04 14:47 ` Lute Kamstra
2003-07-03 15:24 ` Xavier Maillard [this message]
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=plop87adbvmy4p.fsf@gnu-rox.org \
--to=zedek@gnu-rox.org \
--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).