Struct google_gmail1::api::Message
source · pub struct Message {
pub history_id: Option<u64>,
pub id: Option<String>,
pub internal_date: Option<i64>,
pub label_ids: Option<Vec<String>>,
pub payload: Option<MessagePart>,
pub raw: Option<Vec<u8>>,
pub size_estimate: Option<i32>,
pub snippet: Option<String>,
pub thread_id: Option<String>,
}
Expand description
An email message.
§Activities
This type is used in activities, which are methods you may call on this type or where this type is involved in. The list links the activity name, along with information about where it is used (one of request and response).
- drafts send users (response)
- messages get users (response)
- messages import users (request|response)
- messages insert users (request|response)
- messages modify users (response)
- messages send users (request|response)
- messages trash users (response)
- messages untrash users (response)
Fields§
§history_id: Option<u64>
The ID of the last history record that modified this message.
id: Option<String>
The immutable ID of the message.
internal_date: Option<i64>
The internal message creation timestamp (epoch ms), which determines ordering in the inbox. For normal SMTP-received email, this represents the time the message was originally accepted by Google, which is more reliable than the Date
header. However, for API-migrated mail, it can be configured by client to be based on the Date
header.
label_ids: Option<Vec<String>>
List of IDs of labels applied to this message.
payload: Option<MessagePart>
The parsed email structure in the message parts.
raw: Option<Vec<u8>>
The entire email message in an RFC 2822 formatted and base64url encoded string. Returned in messages.get
and drafts.get
responses when the format=RAW
parameter is supplied.
size_estimate: Option<i32>
Estimated size in bytes of the message.
snippet: Option<String>
A short part of the message text.
thread_id: Option<String>
The ID of the thread the message belongs to. To add a message or draft to a thread, the following criteria must be met: 1. The requested threadId
must be specified on the Message
or Draft.Message
you supply with your request. 2. The References
and In-Reply-To
headers must be set in compliance with the RFC 2822 standard. 3. The Subject
headers must match.