You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When setting up Other SMTP you are presented with your configuration page for the settings including those shown below.
The issue
The Encryption options are none, SSL and TLS but there is not STARTTLS in this list, but for some confusing reason this has its own option Use Auto TLS.
STARTTLS when used, the email handshake tries to use encryption starting with the most secure protocol available and then moves down the list (i.e. TLS 1.3 --> TLS 1.2 --> TLS 1.1) and if all of these fail the connection will drop to an insecure connection (unless specified by server not to). This does not require userland settings to tell it to use SSL or TLS.
Proposed solution
Add STARTTLS option to the Encryption list as this is a much more logical location because STARTTLS is a protocol.
Remove the Use Auto TLS section as this is confusion and would no longer be required
You could add descriptions of the none, SSL TLS, STARTLS where the Use Auto TLS option was if you need to keep ease of use and clarity for users.
The text was updated successfully, but these errors were encountered:
shoulders
changed the title
Use Auto TLS options needs to be moved and renames to STARTTLSUse Auto TLS option needs to be moved and renamed to STARTTLSNov 6, 2024
shoulders
changed the title
Use Auto TLS option needs to be moved and renamed to STARTTLSUse Auto TLS option needs to be moved and renamed to STARTTLS protocol
Nov 6, 2024
FluentSMTP: 2.2.8
WordPress: 6.5.5
Background
When setting up
Other SMTP
you are presented with your configuration page for the settings including those shown below.The issue
The
Encryption
options are none, SSL and TLS but there is notSTARTTLS
in this list, but for some confusing reason this has its own optionUse Auto TLS
.STARTTLS
when used, the email handshake tries to use encryption starting with the most secure protocol available and then moves down the list (i.e. TLS 1.3 --> TLS 1.2 --> TLS 1.1) and if all of these fail the connection will drop to an insecure connection (unless specified by server not to). This does not require userland settings to tell it to use SSL or TLS.Proposed solution
STARTTLS
option to theEncryption
list as this is a much more logical location becauseSTARTTLS
is a protocol.Use Auto TLS
section as this is confusion and would no longer be requiredUse Auto TLS
option was if you need to keep ease of use and clarity for users.The text was updated successfully, but these errors were encountered: