diff options
| author | Kevin McCarthy <kevin@8t8.us> | 2020-09-20 18:46:48 -0700 |
|---|---|---|
| committer | Kevin McCarthy <kevin@8t8.us> | 2020-09-20 18:47:51 -0700 |
| commit | 9204b24e99767ae06b5df25eca55c028d702528b (patch) | |
| tree | a1f614540ebfa2715c9c8d28b12181d3dc16a38d /doc | |
| parent | 2ce2fb7baefa42ea564e894eb07edb2d8756d6ff (diff) | |
Reenable $ssl_force_tls.
The next release will be 2.0, providing more justification for
(reasonable) breaking changes. In 2020, this should be the default.
The documentation seems to already make appropriate warnings about
$tunnel_is_secure. Since that option is introduced this release,
there is no need to worry about existing users with it unset.
However, there were a couple stray double-quotes in the documentation
for that, so clean those up in this commit.
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/manual.xml.head | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/manual.xml.head b/doc/manual.xml.head index b2c7f4c3..1ad49f54 100644 --- a/doc/manual.xml.head +++ b/doc/manual.xml.head @@ -9095,7 +9095,7 @@ communication</quote>. <title>Tunnel</title> <para> When connecting through a <link linkend="tunnel">$tunnel</link> - and <link linkend="tunnel-is-secure">$tunnel_is_secure"</link> is + and <link linkend="tunnel-is-secure">$tunnel_is_secure</link> is set (the default), Mutt will assume the connection to the server through the pipe is already secured. Mutt will ignore <link linkend="ssl-starttls">$ssl_starttls</link> and <link @@ -9103,7 +9103,7 @@ communication</quote>. has already been negotiated. </para> <para> - When <link linkend="tunnel-is-secure">$tunnel_is_secure"</link> is + When <link linkend="tunnel-is-secure">$tunnel_is_secure</link> is unset, Mutt will respect the values of <link linkend="ssl-starttls">$ssl_starttls</link> and <link linkend="ssl-force-tls">$ssl_force_tls</link>. It is |