Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <simon@josefsson.org>
Cc: ding@gnus.org
Subject: Re: nnimap/nnagent troubles
Date: 03 Sep 2000 16:21:50 +0200	[thread overview]
Message-ID: <iluzolpy2rl.fsf@barbar.josefsson.org> (raw)
In-Reply-To: <qww66odg142.fsf@sap.com>

Christoph Rohland <cr@sap.com> writes:

> Gnus should definitely give more output on error conditions! If the
> network connection fails, there is no way (known to me) to get the
> actual error (like "connection to <host>:<port> via {tcp|openssl}
> failed with error <errno>, <strerror>". So if something goes wrong the
> user is lost in the dark.

I agree, I often find myself debugging things to find the cause of an
error, when a error message should be sufficient.

>    a) why does the agent store all the server parameters in
>       agent/lib/servers? So any change to server parameters invalidates
>       the agent setup. The server name should be sufficient.

Good idea, I've added it to the todo-list.

>    I tried to use ssl as connection type, but somehow my
>    laptop did not use it despite the fact that I did set the
>    parameter in gnus-secondary-select-methods. 

Ah yes, the curse of changing select method without removing
references to the old server.

Since Gnus store the full server in various places (in every group
info, in agent etc) you need to unsubscribe groups, unregister the
server from the agent and THEN change server method in your .gnus. If
this isn't done, there will be inconsistent server specifications in
various parts of Gnus causing all sorts of strange problems.




  reply	other threads:[~2000-09-03 14:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-03 11:34 Christoph Rohland
2000-09-03 14:21 ` Simon Josefsson [this message]
2000-09-03 16:37   ` Kai Großjohann
2000-09-08 19:23     ` Simon Josefsson
2000-09-08 21:18       ` Kai Großjohann
2000-09-09  8:37       ` Christoph Rohland
2000-09-03 18:06   ` Christoph Rohland
2000-09-03 16:52 Sean Doran

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=iluzolpy2rl.fsf@barbar.josefsson.org \
    --to=simon@josefsson.org \
    --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).