pub struct Capabilities(_);
From section 7.2.1 of RFC 3501.
A list of capabilities that the server supports.
The capability list will include the atom "IMAP4rev1".
In addition, all servers implement the STARTTLS
, LOGINDISABLED
, and AUTH=PLAIN
(described
in IMAP-TLS) capabilities. See the Security
Considerations section of the RFC for
important information.
A capability name which begins with AUTH=
indicates that the server supports that particular
authentication mechanism.
The LOGINDISABLED
capability indicates that the LOGIN
command is disabled, and that the
server will respond with a super::Error::No
response to any attempt to use the LOGIN
command even if the user name and password are valid. An IMAP client MUST NOT issue the
LOGIN
command if the server advertises the LOGINDISABLED
capability.
Other capability names indicate that the server supports an extension, revision, or amendment
to the IMAP4rev1 protocol. Capability names either begin with X
or they are standard or
standards-track RFC 3501 extensions, revisions, or
amendments registered with IANA.
Client implementations SHOULD NOT require any capability name other than IMAP4rev1
, and MUST
ignore any unknown capability names.
Check if the server has the given capability.
Iterate over all the server's capabilities
Returns how many capabilities the server has.
Returns true if the server purports to have no capabilities.
🔬 This is a nightly-only experimental API. (try_from
)
The type returned in the event of a conversion error.
🔬 This is a nightly-only experimental API. (try_from
)
Immutably borrows from an owned value. Read more
🔬 This is a nightly-only experimental API. (try_from
)
The type returned in the event of a conversion error.
🔬 This is a nightly-only experimental API. (try_from
)
Mutably borrows from an owned value. Read more
🔬 This is a nightly-only experimental API. (get_type_id
)
this method will likely be replaced by an associated static