Gnus development mailing list
 help / color / mirror / Atom feed
From: Chris Shenton <chris@shenton.org>
Subject: nnimap: temporarily disable a server?
Date: Mon, 12 Jul 2004 17:14:13 -0400	[thread overview]
Message-ID: <86658t0vyy.fsf@PECTOPAH.shenton.org> (raw)

[Gnus from CVS late last week, behavior seen in all old versions too]

In my Gnus at work, I've defined two IMAP servers: the work one
(NewHorse), and my home server (PECTOPAH):

(setq
 gnus-secondary-select-methods
 '(
   (nnml "")				;pop, files
   (nnimap "NewHorse"
	   (nnimap-address "newhorse.example.com")
	   (nnimap-stream ssl)		; sniff exchange for probe.
	   )
   (nnimap "PECTOPAH"
	   (nnimap-address "shenton.org") ;2004-01-22 only IMAPS gets thru
	   (nnimap-stream ssl)
	   )
   )
 )

Most of the time at work, I don't want it to connect to my house --
connection and scanning for new mail takes too much time.  So I
prevent it from connecting by not listing the home server's password
in the .authinfo file.  When Gnus tries to connect to it (per the
select methods above) it asks for my password; I hit ^G and answer
"yes, treat it as offline" (what does it do if I say "no"?).

The *Server* buffer then looks like:

     {nnml:archive} (opened)
     {nnimap:PECTOPAH} (denied)
     {nnimap:NewHorse} (opened) (agent)
     {nnml:} (opened)

Is there a way of configuring the server select-methods such that it
simply doesn't try to connect to one server or another? Ideally, it
would not connect, but the *Server* buffer would know about it and
allow me to "open" it (with appropriate login info of course).

I can't find anything in the Gnus *info* on IMAP that sounds like
this.  Got any clues? Thanks.



             reply	other threads:[~2004-07-12 21:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-12 21:14 Chris Shenton [this message]
2004-07-16 16:51 ` Ted Zlatanov

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=86658t0vyy.fsf@PECTOPAH.shenton.org \
    --to=chris@shenton.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).