<?xml version="1.0" encoding="UTF-8"?> 
<?xml-stylesheet href="https://dev.horde.org/themes/horde//default/feed-rss.xsl" type="text/xsl"?> 
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> 
 <channel> 
  <title>Mailer: Add Setting for TLS</title> 
  <pubDate>Fri, 10 Apr 2026 19:46:44 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/13373</link> 
  <atom:link rel="self" type="application/rss+xml" title="Mailer: Add Setting for TLS" href="https://bugs.horde.org/ticket/13373/rss" /> 
  <description>Mailer: Add Setting for TLS</description> 
 
   
   
  <item> 
   <title>It is not possible to control whether the horde mailer shoul</title> 
   <description>It is not possible to control whether the horde mailer should access the SMTP server via TLS or not.

Since some servers are configured to refuse plaintext settings, it is important to control whther to use TLS or not.

Thanks!

Torben</description> 
   <pubDate>Tue, 15 Jul 2014 14:19:25 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/13373#t84777</link> 
  </item> 
   
  <item> 
   <title>This is intentional.

Authentication *requires* TLS so the</title> 
   <description>This is intentional.

Authentication *requires* TLS so there is no need to have any configuration for that.

Non-authenticated connections use TLS if available and fall-back to non-authenticated if not available.  But non-authenticated connections are deprecated so I see no need to support explicit non-secure connections here either.

Explicit secure configuration can be passed via the &#039;secure&#039; parameter, but as noted above I see no reason to make the configuration more complicated for the 99% of people that should just use the default.</description> 
   <pubDate>Tue, 15 Jul 2014 19:00:38 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/13373#t84779</link> 
  </item> 
   
  <item> 
   <title>&gt; This is intentional.
&gt;
&gt; Authentication *requires* TLS s</title> 
   <description>&gt; This is intentional.
&gt;
&gt; Authentication *requires* TLS so there is no need to have any 
&gt; configuration for that.
&gt;
&gt; Non-authenticated connections use TLS if available and fall-back to 
&gt; non-authenticated if not available.  But non-authenticated 
&gt; connections are deprecated so I see no need to support explicit 
&gt; non-secure connections here either.
&gt;
&gt; Explicit secure configuration can be passed via the &#039;secure&#039; 
&gt; parameter, but as noted above I see no reason to make the 
&gt; configuration more complicated for the 99% of people that should just 
&gt; use the default.


agreed. I was not aware of this behaviour, is it documented?

Thanks,
Torben

closed.</description> 
   <pubDate>Thu, 17 Jul 2014 17:24:03 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/13373#t84804</link> 
  </item> 
   
  <item> 
   <title>Changes have been made in Git (FRAMEWORK_5_2):

commit 5f829</title> 
   <description>Changes have been made in Git (FRAMEWORK_5_2):

commit 5f829b5e334b49ff6e320c4575fb1d0f09b1e587
Author: Michael M Slusarz &lt;slusarz@horde.org&gt;
Date:   Thu Aug 14 22:50:58 2014 -0600

    Documentation (Ticket #13373)

 horde/config/conf.xml |    3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)

http://github.com/horde/horde/commit/5f829b5e334b49ff6e320c4575fb1d0f09b1e587</description> 
   <pubDate>Fri, 15 Aug 2014 04:51:06 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/13373#t85178</link> 
  </item> 
   
  <item> 
   <title>Changes have been made in Git (master):

commit 0e52d5b3e406</title> 
   <description>Changes have been made in Git (master):

commit 0e52d5b3e40615cff89ad7e58e5def473ef5bf5d
Author: Michael M Slusarz &lt;slusarz@horde.org&gt;
Date:   Thu Aug 14 22:50:58 2014 -0600

    Documentation (Ticket #13373)

 horde/config/conf.xml |    3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)

http://github.com/horde/horde/commit/0e52d5b3e40615cff89ad7e58e5def473ef5bf5d</description> 
   <pubDate>Fri, 15 Aug 2014 06:06:09 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/13373#t85181</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
