Exceptions in Rebex components:
ArgumentException (bad argument provided)
InvalidOperationException (you called a method when you shouldn't)
ObjectDisposedException (the client object is disposed)
Then there are component dependant exceptions, typically one per protocol/component, i.e.
SftpException for SFTP
FtpException for FTP
TlsException for FTP/SSL
Rebex Secure Mail:
ImapException for IMAP
Pop3Exception for POP3
SmtpException for SMTP
and others for other components (
Good news is that all the protocol dependant exceptions iherit from
NetworkSessionException so you can catch for this type and make your code easier.
Please note that
NeworkSessionException.Status represents the category of error that ocurred. In case the
Status is set to
ProtocolError, there is usually another property that you can check, and it provides the protocol-dependant error info, like:
SftpException.Code in Rebex SFTP or
FtpException.Response in Rebex FTP
ImapException.Response in Rebex IMAP, etc.