#[non_exhaustive]pub struct EmailParseResponse {
pub account_id: Id,
pub parsed: Option<HashMap<Id, Email>>,
pub not_parsable: Option<Vec<Id>>,
pub not_found: Option<Vec<Id>>,
pub extra: Map<String, Value>,
}Expand description
Response to Email/parse (RFC 8621 §4.9).
Per RFC 8621 §4.9, parsed Email objects have id, mailboxIds,
keywords, and receivedAt set to null; callers should not rely on
those fields being populated.
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.account_id: IdThe account this response refers to.
parsed: Option<HashMap<Id, Email>>Parsed Emails keyed by source blob id.
not_parsable: Option<Vec<Id>>Blob ids whose contents were not parseable as RFC 5322 messages.
not_found: Option<Vec<Id>>Blob ids that could not be found in the account’s blob store.
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).
Constraint: keys in extra MUST NOT collide with the
typed-field wire names above (the camelCase spelling — e.g.
"accountId", "ids", "properties", "blobIds",
"fromAccountId", etc.). On collision the typed-field value
wins on the wire and the extra value is silently dropped at
serialization. Place vendor extensions under vendor-prefixed
keys (e.g. "acmeCorpFoo") to avoid the collision class.
Trait Implementations§
Source§impl Clone for EmailParseResponse
impl Clone for EmailParseResponse
Source§fn clone(&self) -> EmailParseResponse
fn clone(&self) -> EmailParseResponse
1.0.0 (const: unstable) · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more