From: Sebastian Kaps <seb-dated-1058361745.7f8e08@toyland.sauerland.de>
Subject: Re: Setting up Gnus with IMAP
Date: Mon, 14 Jul 2003 15:29:18 +0200 [thread overview]
Message-ID: <m3vfu59qz5.fsf@toyland.sauerland.de> (raw)
In-Reply-To: <iluznjhw9r9.fsf@latte.josefsson.org>
// Simon Josefsson writes:
> Sebastian Kaps <seb-dated-1058345066.f5d54a@toyland.sauerland.de> writes:
>> // Kai Großjohann writes:
>>
>>> IMHO it doesn't make sense to specify so many values which are the
>>> default anyhow. For example, should the port be "143" or 143?
>>> Should the authenticator be "login" or login? Etc pp.
>>
>> Yes, you're right. But shouldn't the documentation be more clearly about
>> this issue?
> The documentation says the following. How can we improve it?
My version of the documentation seems a bit outdated. For nnimap-stream
it says:
,----
| `nnimap-stream'
| The type of stream used to connect to your server. By default,
| nnimap will detect and automatically use all of the below, with
| the exception of SSL. (SSL is being replaced by STARTTLS, which
| can be automatically detected, but it's not widely deployed yet).
|
| * "gssapi:" Connect with GSSAPI (usually kerberos 5). Require
| the `imtest' program.
|
| * "kerberos4:" Connect with kerberos 4. Require the `imtest'
| program.
|
| * "starttls:" Connect via the STARTTLS extension (similar to
| SSL). Require the external library `starttls.el' and program
| `starttls'.
|
| * "ssl:" Connect through SSL. Require OpenSSL (the program
| `openssl') or SSLeay (`s_client').
|
| * "network:" Plain, TCP/IP network connection.
|
| The `imtest' program is shipped with Cyrus IMAPD, nnimap support
| both `imtest' version 1.5.x and version 1.6.x.
|
| For SSL connections, the OpenSSL program is available from
| `http://www.openssl.org/'. OpenSSL was formerly known as SSLeay,
| and nnimap support it too - altough the most recent versions of
| SSLeay, 0.9.x, are known to have serious bugs making it useless.
| Earlier versions, especially 0.8.x, of SSLeay are known to work.
`----
Note that the possible values are quoted (and even contain colons). This
might be confusing.
> `nnimap-stream'
> The type of stream used to connect to your server. By default,
> nnimap will detect and automatically use all of the below, with
> the exception of TLS/SSL. (IMAP over TLS/SSL is being replaced by
> STARTTLS, which can be automatically detected, but it's not widely
> deployed yet.)
> Example server specification:
> (nnimap "mail.server.com"
> (nnimap-stream ssl))
> Please note that the value of `nnimap-stream' is a symbol!
> ...
This is much better. I think the example wipes out any possible doubt.
However - as an end user who is not very familar with lisp - the "...is
a symbol!" part doesn't help much. I'd have to look up the meaning of
'symbol' in the lisp documentation, which wouldn't be a problem but I
think it's unnecessary.
--
Ciao, Sebastian
next prev parent reply other threads:[~2003-07-14 13:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-13 21:41 Sebastian Kaps
[not found] ` <843ch9plcz.fsf@lucy.is.informatik.uni-duisburg.de>
[not found] ` <m365m55wbn.fsf@toyland.sauerland.de>
2003-07-14 12:52 ` Simon Josefsson
2003-07-14 13:29 ` Sebastian Kaps [this message]
2009-05-13 1:19 Setting up gnus " Marvin
2009-05-13 2:02 ` Marvin
2009-05-13 7:46 ` Gijs Hillenius
2009-05-13 12:01 ` Marvin
2009-05-13 12:51 ` Richard Riley
2009-05-14 5:32 ` Rob Weir
2009-05-14 7:06 ` Tassilo Horn
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=m3vfu59qz5.fsf@toyland.sauerland.de \
--to=seb-dated-1058361745.7f8e08@toyland.sauerland.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).