Enum ImapStatusCode
ImapStatusCode enumeration
Represents the status responses.
[Flags]
public enum ImapStatusCode
Values
| Name | Value | Description |
|---|---|---|
| NotDefined | 0 | Not defined |
| Ok | 1 | The OK response indicates an information message from the server. When tagged, it indicates successful completion of the associated command. The human-readable text MAY be presented to the user as an information message. The untagged form indicates an information-only message; the nature of the information MAY be indicated by a response code. |
| No | 2 | The NO response indicates an operational error message from the server. When tagged, it indicates unsuccessful completion of the associated command. The untagged form indicates a warning; the command can still complete successfully. The human-readable text describes the condition. |
| Bad | 4 | The BAD response indicates an error message from the server. When tagged, it reports a protocol-level error in the client’s command; the tag indicates the command that caused the error. The untagged form indicates a protocol-level error for which the associated command can not be determined; it can also indicate an internal server failure. The human-readable text describes the condition. |
| Preauth | 8 | The PREAUTH response is always untagged, and is one of three possible greetings at connection startup. It indicates that the connection has already been authenticated by external means and thus no LOGIN command is needed. |
| Bye | 10 | The BYE response is always untagged, and indicates that the server is about to close the connection. The human-readable text MAY be displayed to the user in a status report by the client. The difference between a BYE that occurs as part of a normal LOGOUT sequence (the first case) and a BYE that occurs because of a failure (the other three cases) is that the connection closes immediately in the failure case. |
| Alert | 20 | The human-readable text contains a special alert that MUST be presented to the user in a fashion that calls the user’s attention to the message. |
| BadCharset | 40 | Optionally followed by a parenthesized list of charsets. A SEARCH failed because the given charset is not supported by this implementation. |
| Capability | 80 | Followed by a list of capabilities. |
| Parse | 100 | The human-readable text represents an error in parsing the [RFC-2822] header or [MIME-IMB] headers of a message in the mailbox. |
| PermanentFlags | 200 | Followed by a parenthesized list of flags, indicates which of the known flags the client can change permanently. |
| ReadOnly | 400 | The mailbox is selected read-only. |
| ReadWrite | 800 | The mailbox is selected read-write. |
| TryCreate | 1000 | An APPEND or COPY attempt is failing because the target mailbox does not exist. |
| UIDNext | 2000 | Indicates the next unique identifier value. |
| UIDValidity | 4000 | Indicates the unique identifier validity value. |
| Unseen | 8000 | Indicates the number of the first message without the \Seen flag set. |
| Unsolicited | 10000 | Untagged status responses. |
See Also
- namespace Aspose.Email.Clients.Imap
- assembly Aspose.Email
