| SecurityProtocol Enumeration |
Specifies the protocols to be used for performing TLS/SSL negotiation and data encryption.
Namespace: MailBee.Security
Assembly: MailBee.NET (in MailBee.NET.dll) Version: 12.5.0 build 687 for .NET 4.5
SyntaxMembers| Member name | Value | Description | |
|---|---|---|---|
| Auto | 0 | The most secure protocol supported by the server will be used to authenticate the client and encrypt the data as specified by SecurityProtocol setting (if it's available and set). If it's not set or set to the value which permits the usage of a highly vulnerable SSL 3.0 protocol, TlsAuto will be tried instead. For better security, you can set Tls12 or Tls13 explicitly. | |
| Ssl2 | 12 | SSL 2.0 will be used to authenticate the client and encrypt the data. Highly vulnerable! | |
| Ssl3 | 48 | SSL 3.0 will be used to authenticate the client and encrypt the data. Highly vulnerable! | |
| Tls1 | 192 | TLS 1.0 will be used to authenticate the client and encrypt the data. Somewhat vulnerable but there are still some mail servers around which don't support better options. | |
| Tls11 | 768 | TLS 1.1 will be used to authenticate the client and encrypt the data. | |
| Tls12 | 3072 | TLS 1.2 will be used to authenticate the client and encrypt the data. The highest level of security among widely adopted. | |
| Tls13 | 12288 | TLS 1.3 will be used to authenticate the client and encrypt the data. The highest level of security but may be not supported by the particular .NET version (.NET Core 3.0+ is recommended, .NET Framework 4.5+ MAY work provided that all Windows updates are installed and TLS 1.3 is enabled in the registry). | |
| TlsAuto | 4032 | TLS 1.2 will be used if supported by the server. If not, falls back to TLS 1.1 and if it's not supported either, falls back to TLS 1.0. Highly vulnerable SSL 3.0 and its predecessors will NOT be tried anyway. This option is a decent trade-off between security and compatibility. This option does not try TLS 1.3 as it's not well supported by still used .NET versions. |
RemarksThe security protocol can be set via SslProtocol property of SmtpServer, Pop3, or Imap classes.
If the mail server does not support automatic protocol negotiation (this usually results in getting MailBeeSocketResetException thrown during TLS/SSL negotiation), the developer should manually specify the protocol to be used (for example Tls12).
 Note |
|---|
| In case of UWP platform, MailBee always uses TlsAuto setting. |
See Also