Gnus development mailing list
 help / color / mirror / Atom feed
From: rand@meridian-enviro.com (Douglas K. Rand)
Cc: ding@gnus.org
Subject: Re: Migrating to IMAP for real?  As a native method, anyway.
Date: 23 Feb 2001 11:16:33 -0600	[thread overview]
Message-ID: <87n1bdiaku.fsf@delta.meridian-enviro.com> (raw)
In-Reply-To: <vafu25nsser.fsf@lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "21 Feb 2001 21:16:44 +0100")

** Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> on 21 Feb 2001 21:16:44 +0100
** in [Migrating to IMAP for real?  As a native method, anyway.] writes:

Kai> I will be migrating to IMAP sometime in the not so distant future, and
Kai> I thought maybe I should try to make nnimap my primary select method.

Kai> Does anybody have experience with using nnimap as the native server?

Kai> And what would be the least painful way to migrate from me having:

Kai> (setq gnus-select-method '(nntp "foo"))
Kai> (setq gnus-secondary-select-methods
      '((nnimap "" (nnimap-address "bar"))
        (nnml "")))

Kai> to me having this:

Kai> (setq gnus-select-method '(nnimap "" (nnimap-address "bar")))
Kai> (setq gnus-secondary-select-methods
      '((nnml "")
        (nntp "" (nntp-address "foo"))))

Kai> I'd like to keep all marks, if possible.  But of course, I only want
Kai> to do this if there won't be tons of problems.

I am by no means an exprt on Gnus stuff, but I like it anyway.

An approach that I've been using for a few weeks is to basically have
gnus-select-method do nothing, and have everything in
gnus-secondary-select-methods. This has saved me some hassle in
switching things around as the groups are always fully qualified.

(setq gnus-select-method
      '(nnfolder "~/Mail/empty/"
		 (nnfolder-get-new-mail nil)
		 (nnfolder-inhibit-expiry t)))

(setq gnus-secondary-select-methods
      '((nnml "rand")
	(nnimap "Agena"
		(nnimap-address "agena")
		(nnimap-list-pattern ("INBOX" "mail/*")))
	(nntp "news.uswest.net")
	(nntp "news.freshmeat.net")))

I picked the nnfolder because it seemed the easiest to have do nothing
at all.




  parent reply	other threads:[~2001-02-23 17:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-21 20:16 Kai Großjohann
2001-02-21 20:28 ` Michael Alan Dorman
2001-02-21 20:38   ` ShengHuo ZHU
2001-02-21 21:21     ` Kai Großjohann
2001-02-21 21:19   ` Kai Großjohann
2001-02-22 13:53 ` Christoph Rohland
2001-02-22 14:21   ` Paul Jarc
2001-02-23 17:16 ` Douglas K. Rand [this message]
2001-02-26  9:41 ` Christoph Rohland

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=87n1bdiaku.fsf@delta.meridian-enviro.com \
    --to=rand@meridian-enviro.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).