From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: doc bug? IMAP info misleading
Date: 20 Sep 2000 11:41:33 +0200 [thread overview]
Message-ID: <vafg0mvienm.fsf@lucy.cs.uni-dortmund.de> (raw)
Simon (& all others),
I think the Gnus info file is misleading wrt IMAP setup, but I'm not
sure what to do about it. Excerpt from Info file:
/----
| `nnimap-stream'
| [...]
|
| * "ssl:" Connect through SSL. Require OpenSSL (the program
| `openssl') or SSLeay (`s_client').
\----
Users might think that (nnimap-stream "ssl:") is the right thing to
put into their .gnus file. But they should be using (nnimap-stream
ssl) instead!
How can the documentation be reformulated to make this clearer?
Also, the port number is often given as (nnimap-server-port "993")
where it should probably be (nnimap-server-port 993).
kai
--
I like BOTH kinds of music.
next reply other threads:[~2000-09-20 9:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-20 9:41 Kai Großjohann [this message]
2000-09-20 10:45 ` Simon Josefsson
2000-09-20 11:19 ` Simon Josefsson
2000-09-20 11:23 ` Kai Großjohann
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=vafg0mvienm.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.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).