Gnus development mailing list
 help / color / mirror / Atom feed
From: Soren Dayton <dayton@overx.com>
Cc: ding@gnus.org
Subject: Re: moving mail from nnml -> nnimap
Date: 19 Jun 2000 11:31:46 -0500	[thread overview]
Message-ID: <86ya411vkd.fsf@everest.overx.com> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Mon, 19 Jun 2000 16:44:00 +0200"

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="", Size: 1009 bytes --]

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> Soren Dayton <dayton@overx.com> writes:
> 
> > I have about 4 years worth of mail in nnml and I would like to move it
> > to nnimap, keeping the flags (!, *, R, etc), if possible.  is there
> > a good way to do it?
> 
> For each group nnml:foo do
>     create group nnimap:foo
>     enter group nnml:foo using `C-u RET', listing all messages
>     mark all articles using `M P a'
>     move all messages to nnimap:foo using `B m'
> end for
 
[snip]

> You could write little Lisp snippets to automate these tasks.

Yup.  Not actually that hard.  One more question:

what do people do about the change is group hierarchy seperator?
Exchange uses "foo/bar" where gnus uses "foo.bar".  I just have to do
the translation myself because Exchange is more promiscuous about
names than gnus?  Is that the solution?

I see that gnus doesn't support making groups with "/" in the names.
What have people done here?

Soren



  reply	other threads:[~2000-06-19 16:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-19 14:11 Soren Dayton
2000-06-19 14:44 ` Kai Großjohann
2000-06-19 16:31   ` Soren Dayton [this message]
2000-06-19 18:04     ` Simon Josefsson
2000-06-19 21:12       ` Soren Dayton
2000-06-20 12:10       ` Toby Speight
2000-06-19 18:10     ` Kai Großjohann

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=86ya411vkd.fsf@everest.overx.com \
    --to=dayton@overx.com \
    --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).