nnimap: temporarily disable a server?

nnimap: temporarily disable a server?

[Chris Shenton]

[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.

Re: nnimap: temporarily disable a server?

[Ted Zlatanov]

On Mon, 12 Jul 2004, chris@shenton.org wrote:

> 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 don't know the answer, but I have a "home setup" and a "work setup"
function, which push the right thing into the
gnus-secondary-select-methods to achieve the same end.  It would be
nice to put a 'disabled property in a server entry selectively, but I
would guess the amount of work is not trivial.

Ted