The exception that is thrown when the IMAP server reports the given SASL authentication method is not supported and use of another authentication methods is not allowed by the application.
For a list of all members of this type, see MailBeeImapLoginBadMethodException Members.
System.Object
System.Exception
System.ApplicationException
MailBee.MailBeeException
MailBee.MailBeeNetworkException
MailBee.MailBeeRemoteHostException
MailBee.MailBeeProtocolException
MailBee.MailBeeEmailProtocolException
MailBee.MailBeeEmailProtocolNegativeResponseException
MailBee.ImapMail.MailBeeImapNegativeResponseException
MailBee.ImapMail.MailBeeImapLoginNegativeResponseException
MailBee.ImapMail.MailBeeImapLoginBadMethodException
Public static (Shared in Visual Basic) members of this type are safe for multithreaded operations. Instance members are not guaranteed to be thread-safe.
By default, if a particular SASL authentication method is not supported by the server, MailBee switches to the previous method listed in authMethods parameter of Login method. If no more methods left, MailBeeLoginNoSupportedMethodsException is thrown. However, if UseSingleMethodOnly flag is set in authOptions parameter of Login method, MailBee will not try other methods. Instead, if will immediately throw MailBeeImapLoginBadMethodException.
Note This exception does not indicate that authentication using the given method failed. Instead, it indicates the method itself is not supported by the server. When the method is supported but the authentication using this method fails (invalid account name/password), MailBee does not try another methods (there would be no sense if it did), and throws MailBeeImapLoginBadCredentialsException.
Namespace: MailBee.ImapMail
Assembly: MailBee.NET (in MailBee.NET.dll)
MailBeeImapLoginBadMethodException Members | MailBee.ImapMail Namespace | AuthenticationMethods | AuthenticationOptions | MailBeeImapLoginBadCredentialsException