From: ludo@gnu.org (Ludovic Courtès)
To: ding@gnus.org
Subject: Re: [PATCH] sieve-manage: use auth-source
Date: Wed, 13 Oct 2010 17:34:31 +0200 [thread overview]
Message-ID: <8762x6m7i0.fsf@gnu.org> (raw)
In-Reply-To: <sa362x6tan8.fsf@cigue.easter-eggs.fr>
Hello,
Julien Danjou <julien@danjou.info> writes:
> On Wed, Oct 13 2010, Ludovic Courtès wrote:
[...]
>> Connecting to that server on port 2000 shows this:
>>
>> Connected to imap.example.com.
>> Escape character is '^]'.
>> "IMPLEMENTATION" "dovecot"
>> "SASL" ""
>
> This is not valid. The server is saying there's no way to SASL method to
> authenticate with.
Ooh, it’s actually more subtle than this: the PLAIN authentication
method becomes available once a TLS session has been negotiated:
--8<---------------cut here---------------start------------->8---
$ gnutls-cli --starttls -p 2000 imap.example.com
Resolving 'imap.example.com'...
- Simple Client Mode:
"IMPLEMENTATION" "dovecot"
"SASL" ""
"SIEVE" "comparator-i;ascii-numeric fileinto reject vacation imapflags notify include envelope body relational regex subaddress copy"
"STARTTLS"
"RENAME"
OK "mail server - Dovecot ready."
STARTTLS
OK "Begin TLS negotiation now."
*** Starting TLS handshake
- Ephemeral Diffie-Hellman parameters
- Using prime: 1024 bits
- Secret key: 1021 bits
- Peer's public key: 1023 bits
- Certificate type: X.509
- Got a certificate list of 1 certificates.
- Certificate[0] info:
- subject `...’
- The hostname in the certificate matches 'imap.example.com'.
- Peer's certificate issuer is unknown
- Peer's certificate is NOT trusted
- Version: TLS1.0
- Key Exchange: DHE-RSA
- Cipher: AES-128-CBC
- MAC: SHA1
- Compression: NULL
"IMPLEMENTATION" "dovecot"
"SASL" "PLAIN"
"SIEVE" "comparator-i;ascii-numeric fileinto reject vacation imapflags notify include envelope body relational regex subaddress copy"
"RENAME"
OK "TLS negotiation successful."
--8<---------------cut here---------------end--------------->8---
Apparently ‘manage-sieve’ in Gnus git supports starttls, so I’ll give it
a try.
Thanks,
Ludo’.
next prev parent reply other threads:[~2010-10-13 15:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-05 16:16 Julien Danjou
2010-10-05 17:18 ` Lars Magne Ingebrigtsen
2010-10-05 17:28 ` Ted Zlatanov
2010-10-08 15:40 ` Ted Zlatanov
2010-10-08 16:01 ` Julien Danjou
2010-10-13 14:39 ` Ludovic Courtès
2010-10-13 14:44 ` Julien Danjou
2010-10-13 15:34 ` Ludovic Courtès [this message]
2010-10-13 15:51 ` Julien Danjou
2010-10-13 18:26 ` Lars Magne Ingebrigtsen
2010-10-13 18:35 ` Julien Danjou
2010-10-13 18:52 ` Lars Magne Ingebrigtsen
2010-10-14 9:54 ` Julien Danjou
2010-10-14 18:58 ` Lars Magne Ingebrigtsen
2010-10-14 19:09 ` Julien Danjou
2010-10-14 19:11 ` Lars Magne Ingebrigtsen
2010-10-14 19:24 ` Julien Danjou
2010-10-14 19:29 ` Lars Magne Ingebrigtsen
2010-11-21 14:22 ` sieve-manage & starttls Ludovic Courtès
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=8762x6m7i0.fsf@gnu.org \
--to=ludo@gnu.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).