From: Daniel Pittman <daniel@rimspace.net>
Subject: Re: NNML => NNIMAP migration (and IMAP server recommendations. :)
Date: 08 Mar 2001 13:09:59 +1100 [thread overview]
Message-ID: <87elw96mfc.fsf@inanna.rimspace.net> (raw)
In-Reply-To: <dzcbsrdu3fr.fsf@pandora.inf.elte.hu> (NAGY Andras's message of "07 Mar 2001 14:14:00 +0100")
On 07 Mar 2001, NAGY Andras wrote:
> On Wed, 07 Mar 2001, at 04:35, Daniel Pittman <daniel@rimspace.net>
> wrote:
>
>> After using 'B c' (for testing) to spool 2,200 articles into IMAP, I
>> am more than a little afraid of the time it will take to do this
>> migration in Gnus. My estimate is ~ 48 hours, maybe more.
>>
>> So, any suggestions for dealing with that issue?
>
> You could use Mutt (the version that supports IMAP) to do mass
> transfers. It's MH backend can deal with Gnus' nnml format, and has
> the best performance (compared to Gnus and Pine) when it comes to
> _really_ large mailboxes.
>
> But eeek, Gnus stores flags in newsrc, and Mutt expects them in the
> message's Status: header. Which makes it unsuitable for you, I think.
> :(
True. My current plan is to write some Lisp to implement
'gnus-server-migrate-group(s)' that will do the work in Lisp without the
fluff that entering and leaving a summary buffer has.
With luck, fingers crossed, I can manage this, at least on a per-group
basis.
If that fails, though, I might have a look at the Mutt thing, together
with a hack to fill out a header on each message containing the flags...
Daniel
--
You must be the change you wish to see in the world.
-- Gandhi
prev parent reply other threads:[~2001-03-08 2:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-07 3:35 Daniel Pittman
2001-03-07 10:00 ` Simon Josefsson
2001-03-07 13:14 ` NAGY Andras
2001-03-08 2:09 ` Daniel Pittman [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=87elw96mfc.fsf@inanna.rimspace.net \
--to=daniel@rimspace.net \
/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).