[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#24422: Proposal to create `sieve-manage-ignore-broken-tls' option
From: |
Ted Zlatanov |
Subject: |
bug#24422: Proposal to create `sieve-manage-ignore-broken-tls' option |
Date: |
Tue, 20 Sep 2016 09:00:02 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux) |
On Wed, 14 Sep 2016 09:08:17 +0900 Katsumi Yamaoka <yamaoka@jpl.org> wrote:
KY> On Tue, 13 Sep 2016 09:21:48 -0400, Ted Zlatanov wrote:
>> I think the option is badly named. It doesn't ignore broken TLS
>> (whatever that means), it avoids STARTTLS altogether. So maybe it should
>> be `sieve-manage-ignore-starttls' or something like that.
KY> Agreed. I misunderstood what it tries to do. It is irrelevant
KY> if the one is broken or not, it simply makes it not use STARTTLS,
KY> and the docstring is correct:
KY> "Ignore STARTTLS even if STARTTLS capability is provided."
KY> I've renamed it as suggested, with this log entry:
KY> sieve-manage.el: Rename sieve-manage-ignore-broken-tls
KY> * lisp/net/sieve-manage.el (sieve-manage-ignore-starttls):
KY> Rename from sieve-manage-ignore-broken-tls. If it is set,
KY> sieve-manage will never use STARTTLS even if the server says
KY> it is capable (but may be broken).
Thank you, as always!!! This can be marked as done?
Ted