Struct SendMessageOptions 

pub struct SendMessageOptions {
    pub priority: Option<MessagePriority>,
    pub reply_to_msg: Option<String>,
    pub content_type: Option<ContentType>,
    pub reply_context: Option<ReplyContext>,
    pub media_metadata: Option<MediaMetadata>,
    pub forward_info: Option<ForwardInfo>,
    pub via_transport: Option<TransportType>,
    pub app_id: Option<String>,
}

Options for OfflineProtocol::send_message_with: priority and reply threading (as on send_message), plus the rich fields introduced with the sealed rich payload.

The rich fields (reply_context, media_metadata, forward_info) only ever travel inside the MLS-sealed __RICH_V1__ body, and only toward recipients whose key package advertised rich_versions support. Toward anyone else they are silently dropped — never sent cleartext — so the message degrades to plain text with reply_to_msg threading intact.

Fields

priority: Option<MessagePriority>

Message priority (defaults to Medium).

reply_to_msg: Option<String>

ID of the message this is replying to.

content_type: Option<ContentType>

Content type stamped on the outer message (defaults to Text). A coarse rendering hint — the actual content stays MLS-sealed. Toward a recipient that advertised the sealed rich payload, a copy travels inside the sealed body — whenever extras seal, or the hint itself is non-Text — and the receiver treats that copy as authoritative, so a relay cannot rewrite the hint. Must not be ContentType::FileChunk (an internal transport content type; the receiver would route the message into its file-transfer manager and drop it) — rejected as InvalidArgument.

reply_context: Option<ReplyContext>

Quoted-reply context, delivered sealed-only.

media_metadata: Option<MediaMetadata>

Rich media metadata (cloud attachments, stickers — including any encryption_key/iv secrets), delivered sealed-only.

forward_info: Option<ForwardInfo>

Forward attribution, delivered sealed-only.

via_transport: Option<TransportType>

Send via this specific transport (bypassing DORS selection), like send_message_via_transport.

app_id: Option<String>

Application id stamped on this message, in place of the configured crate::ProtocolConfig::app_id.

For an instance that serves several local applications behind one identity: the receiver’s MessageReceived.app_id reports it, so the receiving instance can route the message to the right client. It changes the stamp on this one frame only, never the storage namespace, the MLS session, the BLE app tag, or the id on the acknowledgements and control frames the engine sends for it.

It travels in the clear, outside the sealed body and outside every signature, so any carrier can read and rewrite it (threat model R17). Treat it as routing metadata, never as an authorization input. Held to the same rules as the configured id; an invalid value fails the call with InvalidArgument before anything is queued.

Trait Implementations

impl Clone for SendMessageOptions

fn clone(&self) -> Self

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Debug for SendMessageOptions

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

Formats the value using the given formatter.

impl Default for SendMessageOptions

fn default() -> Self

Returns the “default value” for a type.