From: Andreas Muck <ml@chapulin.de>
Subject: Re: second(ary) imap server
Date: 11 Mar 2001 00:07:49 +0100 [thread overview]
Message-ID: <m38zmdfcje.fsf@mantuzo.chapulin.de> (raw)
In-Reply-To: <vafsnklxmxb.fsf@lucy.cs.uni-dortmund.de>
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
>On 10 Mar 2001, Andreas Muck wrote:
>
>> I just added a second nnimap select method, but I'd like gnus NOT to
>> contact this server until I tell it to check for new mail.
>
>If it's a seconday server, then you might be out of luck. I think
>Gnus always contacts secondary servers to ask them for new groups.
Yes, I guess you're right.
>But the first thing to try is to frob the levels. The variable
>gnus-activate-level says that groups with this level (or a smaller
>number) are activated on startup. If you `S l' all groups from a
>server to a (numerically) higher value, then Gnus will not try to
>check these groups.
I did this - set gnus-activate-level to 3 and the group to 5. The
group was not activated at startup, but Gnus still contacted the
server.
>If Gnus contacts the server anyway, then you might have to take it out
>of gnus-secondary-select-methods and to create a foreign server from
>the server buffer.
But this did the trick (combined with gnus-activate-level). Cool!
Looks like gnus-group-get-new-news respects gnus-activate-level too,
cos it didn't contact the server even when I hit "g".
That's just what I wanted!
Thank you :)
Andi
next prev parent reply other threads:[~2001-03-10 23:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-10 22:24 Andreas Muck
2001-03-10 22:46 ` Kai Großjohann
2001-03-10 23:07 ` Andreas Muck [this message]
2001-03-10 23:34 ` Kai Großjohann
2001-03-11 19:11 ` Andreas Oeldenberger
2001-03-11 19:48 ` Kai Großjohann
2001-03-11 23:14 ` Andreas Oeldenberger
2001-03-12 20:29 ` Kai Großjohann
2001-03-12 21:41 ` Andreas Oeldenberger
2001-03-14 10:22 ` Kai Großjohann
2001-03-16 12:48 ` Andreas Muck
2001-03-16 16:28 ` Kai Großjohann
2001-03-16 17:10 ` Andreas Muck
2001-03-16 17:27 ` Toby Speight
2001-03-16 17:46 ` Andreas Muck
2001-03-16 19:03 ` David S. Goldberg
2001-03-16 22:21 ` Toby Speight
2001-03-16 21:42 ` Kai Großjohann
2001-03-16 12:34 ` Andreas Muck
2001-03-16 16:26 ` Kai Großjohann
2001-03-16 12:26 ` Andreas Muck
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=m38zmdfcje.fsf@mantuzo.chapulin.de \
--to=ml@chapulin.de \
/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).