Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: info-gnus-english@gnu.org
Subject: Re: Suppressing unavailable imap server by default
Date: Thu, 22 Sep 2016 10:25:26 +0800	[thread overview]
Message-ID: <87wpi4fz6x.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87fuotz7lh.fsf@gmx.de>

Michael Albinus <michael.albinus@gmx.de> writes:

> Hi,
>
> maybe it is a known technique, but even after RTFM I couldn't find it ...
>
> I have configured an imap server which is reachable only sometimes (when
> I have entered the company's lan). Connecting it via gnus takes always
> ~2 min, until there is a timeout, and the server is ignored ("denied" in
> the *Server* buffer).
>
> How could I change my configuration, that this timeout is reduced? Or
> that prior to connecting the server via imap there is a check, whether
> the server is reachable?
>
> Extra bonus if I could configure it such a way that I don't need to
> confirm that the server isn't reachable.
>
> Thanks, and best regards, Michael.

I think what people do is to make sure all the groups belonging to that
server are set at a fairly high level, and then, when starting Gnus and
checking for news, only check at a lower level. I have wrapper functions
that call (gnus 4) and (gnus-group-get-new-news 4), and set less
interesting servers at level 5.

What I think would be preferable would be if a server status of "closed"
persisted between Gnus restarts. Then you could just leave it closed,
and open it manually when you decide you want to check news.

Eric



  reply	other threads:[~2016-09-22  2:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-21 13:48 Michael Albinus
2016-09-22  2:25 ` Eric Abrahamsen [this message]
     [not found] <mailman.2746.1474467763.22741.info-gnus-english@gnu.org>
2016-09-22 12:19 ` Ted Zlatanov
2016-09-22 13:27   ` Michael Albinus
     [not found]   ` <mailman.2819.1474550834.22741.info-gnus-english@gnu.org>
2016-09-22 13:31     ` Ted Zlatanov
2016-10-21  9:56       ` Michael Albinus

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=87wpi4fz6x.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=info-gnus-english@gnu.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).