#[non_exhaustive]pub struct Identity {
pub id: Id,
pub name: String,
pub email: String,
pub reply_to: Option<Vec<EmailAddress>>,
pub bcc: Option<Vec<EmailAddress>>,
pub text_signature: String,
pub html_signature: String,
pub may_delete: bool,
pub extra: Map<String, Value>,
}Expand description
An RFC 8621 §6 Identity object.
Stores information about an email address or domain the user may send from.
Fields (Non-exhaustive)§
This struct is marked as non-exhaustive
Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.id: IdThe id of the Identity (immutable; server-set).
name: StringThe “From” name the client SHOULD use when creating a new Email
from this Identity. Defaults to "".
email: StringThe “From” email address the client MUST use (immutable).
reply_to: Option<Vec<EmailAddress>>The Reply-To value the client SHOULD set. null if not set.
bcc: Option<Vec<EmailAddress>>The Bcc value the client SHOULD set. null if not set.
text_signature: StringPlaintext signature. Defaults to "".
html_signature: StringHTML snippet signature. Defaults to "".
may_delete: boolWhether the user may delete this Identity (server-set).
extra: Map<String, Value>Catch-all for vendor / site / private extension fields not covered by the typed fields above. Preserves unknown fields across deserialize/serialize round-trip per workspace extras-preservation policy (see workspace AGENTS.md).
Implementations§
Trait Implementations§
Source§impl<'de> Deserialize<'de> for Identity
impl<'de> Deserialize<'de> for Identity
Source§fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>where
__D: Deserializer<'de>,
fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>where
__D: Deserializer<'de>,
impl Eq for Identity
impl GetObject for Identity
Source§impl JmapObject for Identity
impl JmapObject for Identity
Source§impl SetObject for Identity
RFC 8621 §6 (rfc8621.txt:3988, 3997, 4039): id is “(immutable;
server-set)”, email is “(immutable)”, mayDelete is “(server-set)”.
impl SetObject for Identity
RFC 8621 §6 (rfc8621.txt:3988, 3997, 4039): id is “(immutable;
server-set)”, email is “(immutable)”, mayDelete is “(server-set)”.
Source§const SERVER_SET: &'static [&'static str]
const SERVER_SET: &'static [&'static str]
/set method text never accepts from a
client, on create or update, is server-set too. Read moreSource§const CLIENT_SETTABLE: &'static [&'static str]
const CLIENT_SETTABLE: &'static [&'static str]
SERVER_SET: the ones a
client may set through /set. Read moreSource§const IMMUTABLE: &'static [&'static str]
const IMMUTABLE: &'static [&'static str]
CLIENT_SETTABLE properties the spec marks “immutable”: “The
value MUST NOT change after the object is created.” (RFC 8620 §1.1).
A property the /set method text accepts on create but not on update
is immutable too. Read more