Changes have been made in Git (master):

commit 0e52d5b3e40615cff89ad7e58e5def473ef5bf5d
Author: Michael M Slusarz <slusarz@horde.org>
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

Changes have been made in Git (FRAMEWORK_5_2):

commit 5f829b5e334b49ff6e320c4575fb1d0f09b1e587
Author: Michael M Slusarz <slusarz@horde.org>
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

agreed. I was not aware of this behaviour, is it documented?

Thanks,
Torben

closed.

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 'secure' 
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.

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