Enum imap_types::flag::Flag
source · pub enum Flag<'a> {
Seen,
Answered,
Flagged,
Deleted,
Draft,
Extension(FlagExtension<'a>),
Keyword(Atom<'a>),
}
Expand description
There are two types of flags in IMAP4rev1: System and keyword flags.
A system flag is a flag name that is pre-defined in RFC3501.
All system flags begin with “" and certain system flags (\Deleted
and \Seen
) have special semantics.
Flags that begin with “" but are not pre-defined system flags, are extension flags.
Clients MUST accept them and servers MUST NOT send them except when defined by future standard or standards-track revisions.
A keyword is defined by the server implementation.
Keywords do not begin with “" and servers may permit the client to define new ones
in the mailbox by sending the “*” flag (FlagPerm::AllowNewKeywords
) in the PERMANENTFLAGS response..
Note that a flag of either type can be permanent or session-only.
Variants§
Seen
Message has been read (\Seen
).
Answered
Message has been answered (\Answered
).
Flagged
Message is “flagged” for urgent/special attention (\Flagged
).
Deleted
Message is “deleted” for removal by later EXPUNGE (\Deleted
).
Draft
Message has not completed composition (marked as a draft) (\Draft
).
Extension(FlagExtension<'a>)
A future expansion of a system flag.
Keyword(Atom<'a>)
A keyword.
Implementations§
Trait Implementations§
source§impl<'a, 'arbitrary: 'a> Arbitrary<'arbitrary> for Flag<'a>
impl<'a, 'arbitrary: 'a> Arbitrary<'arbitrary> for Flag<'a>
source§fn arbitrary(u: &mut Unstructured<'arbitrary>) -> Result<Self>
fn arbitrary(u: &mut Unstructured<'arbitrary>) -> Result<Self>
Self
from the given unstructured data. Read moresource§fn arbitrary_take_rest(u: Unstructured<'arbitrary>) -> Result<Self>
fn arbitrary_take_rest(u: Unstructured<'arbitrary>) -> Result<Self>
Self
from the entirety of the given
unstructured data. Read more