Struct mailslurp::models::email::Email [−][src]
pub struct Email {}Show fields
pub analysis: Option<Box<EmailAnalysis>>, pub attachments: Option<Vec<String>>, pub bcc: Option<Vec<String>>, pub body: Option<String>, pub body_md5_hash: Option<String>, pub cc: Option<Vec<String>>, pub charset: Option<String>, pub created_at: Option<String>, pub from: Option<String>, pub headers: Option<HashMap<String, String>>, pub id: Option<String>, pub inbox_id: Option<String>, pub is_html: Option<bool>, pub read: Option<bool>, pub reply_to: Option<String>, pub subject: Option<String>, pub team_access: Option<bool>, pub to: Option<Vec<String>>, pub updated_at: Option<String>, pub user_id: Option<String>,
Expand description
Email : Email entity (also known as EmailDto). When an SMTP email message is received by MailSlurp it is parsed. The body and attachments are written to disk and the fields such as to, from, subject etc are stored in a database. The body
contains the email content. If you want the original SMTP message see the getRawEmail
endpoints. The attachments can be fetched using the AttachmentController
Fields
analysis: Option<Box<EmailAnalysis>>
attachments: Option<Vec<String>>
List of IDs of attachments found in the email. Use these IDs with the Inbox and Email Controllers to download attachments and attachment meta data such as filesize, name, extension.
bcc: Option<Vec<String>>
List of BCC
recipients email was addressed to
body: Option<String>
The body of the email message
body_md5_hash: Option<String>
A hash signature of the email message
cc: Option<Vec<String>>
List of CC
recipients email was addressed to
charset: Option<String>
Detected character set of the email body such as UTF-8
created_at: Option<String>
When was the email received by MailSlurp
from: Option<String>
Who the email was sent from
headers: Option<HashMap<String, String>>
Collection of SMTP headers attached to email
id: Option<String>
ID of the email entity
inbox_id: Option<String>
ID of the inbox that received the email
is_html: Option<bool>
Is the email body HTML
read: Option<bool>
Read flag. Has the email ever been viewed in the dashboard or fetched via the API? If so the email is marked as read.
reply_to: Option<String>
The replyTo
field on the received email message
subject: Option<String>
The subject line of the email message
team_access: Option<bool>
Can the email be accessed by organization team members
to: Option<Vec<String>>
List of To
recipients that email was addressed to
updated_at: Option<String>
When was the email last updated
user_id: Option<String>
ID of user that email belongs to
Implementations
Email entity (also known as EmailDto). When an SMTP email message is received by MailSlurp it is parsed. The body and attachments are written to disk and the fields such as to, from, subject etc are stored in a database. The body
contains the email content. If you want the original SMTP message see the getRawEmail
endpoints. The attachments can be fetched using the AttachmentController
Trait Implementations
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>,
Deserialize this value from the given Serde deserializer. Read more
Auto Trait Implementations
impl RefUnwindSafe for Email
impl UnwindSafe for Email
Blanket Implementations
Mutably borrows from an owned value. Read more
Instruments this type with the provided Span
, returning an
Instrumented
wrapper. Read more