AuthenticationMethods Enumeration
Provides authentication methods to be used for logging in the user account on the server.

Namespace: MailBee
Assembly: MailBee.NET (in MailBee.NET.dll) Version: 12.5.0 build 687 for .NET 4.5
Syntax
Copy
[FlagsAttribute]
public enum AuthenticationMethods
Members
  Member nameValueDescription
None0 No authentication. Sometimes used with Smtp when the server allows relay for anonymous senders.
Regular1 Standard authentication. Passwords are transmitted as clear-text. Not supported by SMTP servers.
Apop2 Secure APOP authentication. Supported by many POP3 servers but cannot be used with other servers like SMTP because APOP is POP3-specific. Disabled when FipsMode is enabled.
SaslUserDefined4 A custom SASL authentication method implemented by the developer.
SaslLogin8 SASL LOGIN authentication. Not secure but widely supported. Passwords are transmitted as Base64 strings. Note for IMAP users: this is AUTHENTICATE LOGIN command, not just LOGIN command (which corresponds to Regular method).
SaslPlain16 SASL PLAIN authentication. Not secure but widely supported. Passwords are transmitted as Base64 strings.
SaslCramMD532 Secure SASL CRAM-MD5 authentication. Might not be supported by particular server implementations. Disabled when FipsMode is enabled.
SaslDigestMD564 Secure SASL DIGEST-MD5 authentication. Might not be supported by particular server implementations. Disabled when FipsMode is enabled.
SaslNtlm128 Secure SASL NTLM authentication (also known as Secure Password Authentication - SPA). In Windows domain environment such as Active Directory, can also be used to authenticate the current Windows user (in this case, the developer should pass a null reference (Nothing in Visual Basic) as accountName and password values). Might not be supported by particular server implementations. May not work in UWP apps, consider GSSAPI instead. See remarks section for futher details regarding Integrated Windows Authentication.
SaslMsn256 Secure SASL MSN authentication (equivalent to NTLM). Not widely supported nowadays.
SaslGssApi512 Secure SASL GSSAPI authentication (through Kerberos or NTLM). Like SaslNtlm, supports Integrated Windows Authentication mode. The internal implementation (Kerberos or NTLM) is selected upon whether targetName of Login method is an empty string or not (for SMTP case, TargetName). Empty string denotes NTLM, all other values (including a null reference) denote Kerberos. Also, the underlying implementation downgrades to NTLM from Kerberos if targetName is not empty but not valid (denotes non-existent SPN).
SaslOAuth1024 OAuth v1.0 authentication (widely used by Google in the past). It's a password-only authentication. To create a key to be supplied as the OAuth password, use OAuth class. As the OAuth account name, specify a null reference (Nothing in Visual Basic). Note that if you supplied both the password and the account name when logging in, MailBee will exclude OAuth from the set of authentication methods to be tried unless SaslOAuth is the only method listed in this set. This is because OAuth is not compatible with other authentication methods which require a login and a password, not a "key". You can, however, specify non-null account name if you explicitly specified SaslOAuth method to be used for login. This account name can be any string, it won't be used during the login process itself (because it uses only the password) but it will be displayed in the log file in place of the account name.
SaslOAuth22048 OAuth v2.0 authentication. A newer and recommended version of OAuth. All MailBee-specific details (listed above in SaslOAuth description) are valid for this method as well.
Auto4095 Tells MailBee to automatically select the best supported authentication method and downgrade to insecure methods if secure methods are not supported by the server. This behavior can be changed with AuthenticationOptions flags.
Remarks

A SASL method can be used with all protocols (SMTP, POP3, IMAP) provided that the server supports the given method. Non-SASL methods are protocol-specific.

You can implement your own authentication methods. See SaslMethod topic for details.

Note Note
When the application is a web application which operates under context of anonymous user, Integrated Windows Authentication will use the context of this anonymous user (which most likely doesn't have an account on the mail server). Thus, using Integrated Windows Authentication does not make sense for web apps operating under anonymous user account (Internet Guest User).
See Also