Struct OutgoingAttachment 

#[non_exhaustive]
pub struct OutgoingAttachment {
    pub filename: String,
    pub content_type: String,
    pub data: Vec<u8>,
    pub is_inline: bool,
    pub content_id: Option<String>,
}

An attachment to include in an outgoing email.

References

• RFC 2183 (Content-Disposition: attachment / inline)
• RFC 2392 (Content-ID)
• RFC 2045 (Content-Transfer-Encoding: base64)

Fields (Non-exhaustive)

Non-exhaustive structs could have additional fields added in future. Therefore, non-exhaustive structs cannot be constructed in external crates using the traditional Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.

filename: String

Filename for the Content-Disposition header.

content_type: String

MIME content type (e.g., "application/pdf").

data: Vec<u8>

Raw file data — will be base64-encoded in the message.

is_inline: bool

When true, the part uses Content-Disposition: inline instead of attachment (RFC 2183 Section 2). Typically used for images embedded in HTML via cid: URLs.

content_id: Option<String>

Optional Content-ID header value (RFC 2392). Should be a bare addr-spec (e.g., "image001@example.com"); the builder wraps it in angle brackets. Required for HTML-embedded inline images that are referenced as <img src="cid:image001@example.com">.

Implementations

impl OutgoingAttachment

pub fn new( filename: impl Into<String>, content_type: impl Into<String>, data: impl Into<Vec<u8>>, ) -> Self

Creates a regular (non-inline) attachment.

References

• RFC 2183 (Content-Disposition: attachment)
• RFC 2045 (Content-Transfer-Encoding: base64)

pub fn inline( filename: impl Into<String>, content_type: impl Into<String>, data: impl Into<Vec<u8>>, content_id: impl Into<String>, ) -> Self

Creates an inline attachment with a Content-ID for embedding in HTML.

Inline attachments use Content-Disposition: inline (RFC 2183 Section 2) and are referenced by the HTML body via cid: URLs (RFC 2392).

References

• RFC 2183 Section 2 (Content-Disposition: inline)
• RFC 2392 (Content-ID)

Trait Implementations

impl Clone for OutgoingAttachment

fn clone(&self) -> OutgoingAttachment

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for OutgoingAttachment

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Hash for OutgoingAttachment

fn hash<__H: Hasher>(&self, state: &mut __H)

Feeds this value into the given Hasher.

fn hash_slice<H>(data: &[Self], state: &mut H)

where H: Hasher, Self: Sized,

Feeds a slice of this type into the given Hasher.

impl PartialEq for OutgoingAttachment

fn eq(&self, other: &OutgoingAttachment) -> bool

Tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

Tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl Eq for OutgoingAttachment

impl StructuralPartialEq for OutgoingAttachment