org.freedesktop.Telepathy.Channel.Interface.Messages

# Interface org.freedesktop.Telepathy.Channel.Interface.Messages

Interface Index (Compact) | Summary | Description | Methods | Signals | Properties | Types

### Methods

SendMessage | (aa{sv}: Message, u: Flags) | → | s: Token |
GetPendingMessageContent | (u: Message_ID, au: Parts) | → | a{uv}: Content |

### Signals

MessageSent | (aa{sv}: Content, u: Flags, s: Message_Token) |
PendingMessagesRemoved | (au: Message_IDs) |
MessageReceived | (aa{sv}: Message) |

### Properties

SupportedContentTypes | as | Read only |
MessagePartSupportFlags | u (Message_Part_Support_Flags) | Read only |
PendingMessages | aaa{sv} (Message_Part_List_List) | Read only |
DeliveryReportingSupport | u (Delivery_Reporting_Support_Flags) | Read only |

### Types

Message_Part_Index | Simple Type | u |
Protocol_Message_Token | Simple Type | s |
Delivery_Status | Enum | u |
Message_Part_Support_Flags | Flags | u |
Message_Sending_Flags | Flags | u |
Delivery_Reporting_Support_Flags | Flags | u |
Message_Part | Mapping | a{sv} |
Message_Part_Content_Map | Mapping | a{uv} |

Added in 0.17.16. (as stable API)
Objects implementing this interface must also implement:

- org.freedesktop.Telepathy.Channel.Type.Text

### Description

This interface extends the Text interface to support more general messages, including:

- messages with attachments (like MIME multipart/mixed)
- groups of alternatives (like MIME multipart/alternative)
- delivery reports
- any extra types of message we need in future

Although this specification supports formatted (rich-text) messages with unformatted alternatives, implementations SHOULD NOT attempt to send formatted messages until the Telepathy specification has also been extended to cover capability discovery for message formatting.

We intend to expose all rich-text messages as XHTML-IM, but on some protocols, formatting is an extremely limited subset of that format (e.g. there are protocols where foreground/background colours, font and size can be set, but only for entire messages). Until we can tell UIs what controls to offer to the user, it's unfriendly to offer the user controls that may have no effect.

This interface also replaces Text.SendError, adding support for protocols where the message content is not echoed back to the sender on failure, adding support for receiving positive acknowledgements, and using the Messages queue for state-recovery (ensuring that incoming delivery reports are not lost if there is not currently a process handling them).

If this interface is present, clients that support it SHOULD listen for the MessageSent and MessageReceived signals, and ignore the Sent, SendError and Received signals on the Text interface (which are guaranteed to duplicate signals from this interface).

# Methods

(Permalink)

## SendMessage (aa{sv}: Message, u: Flags) → s: Token

### Parameters

- Message — aa{sv} (Message_Part_List)
The message content, including any attachments or alternatives
- Flags — u (Message_Sending_Flags)
Flags affecting how the message is sent.

### Returns

- Token — s (Protocol_Message_Token)
An opaque token used to match any incoming delivery or failure reports against this message, or an empty string if the message is not readily identifiable.

Submit a message to the server for sending. If this method returns successfully, the message has been submitted to the server and the MessageSent signal is emitted. A corresponding Sent signal on the Text interface MUST also be emitted.

This method MUST return before the MessageSent signal is emitted.

This means that the process sending the message is the first to see the Protocol_Message_Token, and can relate the message to the corresponding MessageSent signal by comparing message tokens (if supported by the protocol).

If this method fails, message submission to the server has failed and no signal on this interface (or the Text interface) is emitted.

### Possible Errors

- Invalid Argument
The requested message is malformed and cannot be sent.
- Not Available
Raised when the requested functionality is temporarily unavailable.
- Permission Denied
The user is not permitted to perform the requested operation.
- Network Error
Raised when there is an error reading from or writing to the network.

(Permalink)

## GetPendingMessageContent (u: Message_ID, au: Parts) → a{uv}: Content

### Parameters

- Message_ID — u (Message_ID)
The ID of a pending message
- Parts — au (Message_Part_Index_List)
The desired entries in the array of message parts, identified by their position. The "headers" part (which is not a valid argument to this method) is considered to be part 0, so the valid part numbers start at 1 (for the second Message_Part).

### Returns

- Content — a{uv} (Message_Part_Content_Map)

The content of the requested parts. The keys in this mapping are positions in the array of message parts; the values are either of type 's' or 'ay' (UTF-8 text string, or byte array), following the same rules as for the value of the 'content' key in the Message_Part mappings.

If the one of the requested part numbers was greater than zero but referred to a part that had no content (i.e. it had no 'content-type' key or no 'content' key), it is simply omitted from this mapping; this is not considered to be an error condition.

Retrieve the content of one or more parts of a pending message. Note that this function may take a considerable amount of time to return if the part's 'needs-retrieval' flag is true; consider extending the default D-Bus method call timeout. Additional API is likely to be added in future, to stream large message parts.

### Possible Errors

- Invalid Argument
Either there is no pending message with the given message ID, or one of the part numbers given was 0 or too large.
- Not Available
Raised when the requested functionality is temporarily unavailable.
- Permission Denied
The user is not permitted to perform the requested operation.
- Network Error
Raised when there is an error reading from or writing to the network.

# Signals

(Permalink)

## MessageSent (aa{sv}: Content, u: Flags, s: Message_Token)

### Parameters

- Content — aa{sv} (Message_Part_List)

The message content (see Message_Part for full details). If the message that was passed to SendMessage has a formatted text part that the connection manager recognises, but no text/plain alternative, the CM MUST use the formatted text part to generate a text/plain alternative which is also included in this signal argument.

If the connection manager can predict that the message will be altered during transmission, this argument SHOULD reflect what other contacts will receive, rather than being a copy of the argument to SendMessage (if the message is truncated, formatting or alternatives are dropped, etc., then the edited version SHOULD appear in this signal).

- Flags — u (Message_Sending_Flags)

Flags affecting how the message was sent. The flags might be a subset of those passed to SendMessage if the caller requested unsupported flags.

- Message_Token — s (Protocol_Message_Token)
An opaque token used to match any incoming delivery or failure reports against this message, or an empty string if the message is not readily identifiable.

Signals that a message has been submitted for sending. This MUST be emitted exactly once per emission of the Sent signal on the Text interface. This SHOULD be emitted as soon as the CM determines it's theoretically possible to send the message (e.g. the parameters are supported and correct).

This signal allows a process that is not the caller of SendMessage to log sent messages. The double signal-emission provides compatibility with older clients. Clients supporting Messages should listen for Messages.MessageSent only (if the channel has the Messages interface) or Text.Sent only (otherwise).

(Permalink)

## PendingMessagesRemoved (au: Message_IDs)

### Parameters

- Message_IDs — au (Message_ID_List)
The messages that have been removed from the pending message list.

The messages with the given IDs have been removed from the PendingMessages list. Clients SHOULD NOT attempt to acknowledge those messages.
This completes change notification for the PendingMessages property (previously, there was change notification when pending messages were added, but not when they were removed).
(Permalink)

## MessageReceived (aa{sv}: Message)

### Parameters

- Message — aa{sv} (Message_Part_List)
The message content, including any attachments or alternatives

Signals that a message has been received and added to the pending messages queue. This MUST be emitted exactly once per emission of the Received signal on the Text interface.
The double signal-emission provides compatibility with older clients. Clients supporting Messages should listen for Messages.MessageReceived only (if the channel has the Messages interface) or Text.Received only (otherwise).

# Properties

Accessed using the org.freedesktop.DBus.Properties interface.
(Permalink)

## SupportedContentTypes — as

Read only

A list of MIME types supported by this channel, with more preferred MIME types appearing earlier in the list. The list MAY include "*/*" to indicate that attachments with arbitrary MIME types can be sent. This list MUST NOT be empty, since all Messages implementations MUST accept messages containing a single "text/plain" part.

Some examples of how this property interacts with the MessagePartSupportFlags:

A simple IM implementation: only plain text messages are allowed
  SupportedContentTypes = ['text/plain'], MessagePartSupportFlags = 0
Formatted text with a plain text alternative is allowed (see the HTML interface draft)
  SupportedContentTypes = ['text/html', 'text/plain'], MessagePartSupportFlags = 0
JPEG or PNG images may be sent, but without any attached text
  SupportedContentTypes = ['text/plain', 'image/jpeg', 'image/png'], MessagePartSupportFlags = 0
Unformatted text to which an optional JPEG or PNG image may be attached
  SupportedContentTypes = ['text/plain', 'image/jpeg', 'image/png'], MessagePartSupportFlags = One_Attachment
Formatted text to which arbitrarily many images may be attached
  SupportedContentTypes = ['text/html', 'text/plain', 'image/jpeg', 'image/png', 'image/x-ms-bmp'], MessagePartSupportFlags = One_Attachment | Multiple_Attachments
A full SIP implementation: arbitrary MIME messages are allowed
  SupportedContentTypes = ['*/*'], MessagePartSupportFlags = One_Attachment | Multiple_Attachments

(Permalink)

## MessagePartSupportFlags — u (Message_Part_Support_Flags)

Read only
Flags indicating the level of support for message parts on this channel.
(Permalink)

## PendingMessages — aaa{sv} (Message_Part_List_List)

Read only
A list of incoming messages that have neither been acknowledged nor rejected. This list is a more detailed version of the one returned by Text.ListPendingMessages, and contains the same messages, uniquely identified by the same pending message IDs. Its items can be removed using Text.AcknowledgePendingMessages.
(Permalink)

## DeliveryReportingSupport — u (Delivery_Reporting_Support_Flags)

Read only
A bitfield indicating features supported by this channel.

# Types

Simple Type (Permalink)

## Message_Part_Index — u

Added in 0.17.17.
The index of a message part within a message.
Simple Type (Permalink)

## Protocol_Message_Token — s

An opaque token used to identify messages in the underlying. protocol. As a special case, the empty string indicates that there is no particular identification for a message.

CM implementations SHOULD use an identifier expected to be unique, such as a UUID, if possible.

Some protocols can only track a limited number of messages in a small message-ID space (SMS messages are identified by a single byte), and some implementations send non-unique identifiers (some XMPP clients use very simple message IDs, such as an incrementing integer that resets to 1 at the beginning of each connection). As a result, clients MUST NOT assume that protocol tokens will not be re-used.

In particular, clients SHOULD use a heuristic to assign delivery reports to messages, such as matching on message content or timestamp (if available), or assuming that the delivery report refers to the most recent message with that ID.

Enum (Permalink)

## Delivery_Status — u

The status of a message as indicated by a delivery report.

If this enum is extended in future specifications, this should only be to add new, non-overlapping conditions (i.e. all failures should still be signalled as either Temporarily_Failed or Permanently_Failed). If additional detail is required (e.g. distinguishing between the various types of permanent failure) this will be done using additional keys in the Message_Part.

- Unknown (0)
The message's disposition is unknown. Clients SHOULD consider all messages to have status Delivery_Status_Unknown unless otherwise specified; connection managers SHOULD NOT signal this delivery status explicitly.
- Delivered (1)
The message has been delivered to the intended recipient.
- Temporarily_Failed (2)
Delivery of the message has failed. Clients SHOULD notify the user, but MAY automatically try sending another copy of the message.
Similar to errors with type="wait" in XMPP; analogous to 4xx errors in SMTP.
- Permanently_Failed (3)
Delivery of the message has failed. Clients SHOULD NOT try again unless by specific user action. If the user does not modify the message or alter configuration before re-sending, this error is likely to happen again.
Similar to errors with type="cancel", type="modify" or type="auth" in XMPP; analogous to 5xx errors in SMTP.
- Accepted (4)
An intermediate server has accepted the message but the message has not been yet delivered to the ultimate recipient. The connection manager might send a Failed report or Delivered report later.
Similar to "202 Accepted" success code in SIP; analogous to 251 and 252 responses in SMTP.

Flags (Permalink)

## Message_Part_Support_Flags — u

Flags indicating the level of support for message parts on this channel. They are designed such that setting more flags always implies that the channel has more capabilities.

If no flags are set, this indicates that messages may contain a single message part whose content-type is any of the types from SupportedContentTypes, possibly with some alternatives.

There is no flag indicating support for alternatives. This is because the SendMessage implementation can always accept messages containing alternatives, even if the underlying protocol does not, by deleting all alternatives except the first (most preferred) that is supported.

Each of the flags so far implies the previous flag, so we could have used a simple enumeration here; however, we've defined the message-part support indicator as a flag set for future expansion.

See SupportedContentTypes for some examples.

- One_Attachment (1)
SendMessage will accept messages containing a textual message body, plus a single attachment of any type listed in the SupportedContentTypes property. It does not make sense for this flag to be set if Message_Part_Support_Flag_Data_Only is not also set (because the connection manager can trivially provide an empty text part if necessary).
- Multiple_Attachments (2)
SendMessage will accept messages containing a textual message body, plus an arbitrary number of attachments of any type listed in the SupportedContentTypes property. It does not make sense for this flag to be set if Message_Part_Support_Flag_One_Attachment is not also set.

Flags (Permalink)

## Message_Sending_Flags — u

Flags altering the way a message is sent. The "most usual" action should always be to have these flags unset.

- Report_Delivery (1)

Provide a successful delivery report if possible, even if this is not the default for this protocol. Ignored if delivery reports are not possible on this protocol.

In some protocols, like XMPP, it is not conventional to request or send positive delivery notifications.

Delivery failure reports SHOULD always be sent, but if this flag is present, the connection manager MAY also try harder to obtain failed delivery reports or allow them to be matched to outgoing messages.

Flags (Permalink)

## Delivery_Reporting_Support_Flags — u

Flags indicating the level of support for delivery reporting on this channel. Any future flags added to this set will conform to the convention that the presence of an extra flag implies that more operations will succeed.

- Receive_Failures (1)
Clients MAY expect to receive negative delivery reports if Message_Sending_Flag_Report_Delivery is specified when sending.
If senders want delivery reports, they should ask for them. If they don't want delivery reports, they can just ignore them, so there's no need to have capability discovery for what will happen if a delivery report isn't requested.
- Receive_Successes (2)
Clients MAY expect to receive positive delivery reports if Message_Sending_Flag_Report_Delivery is specified when sending.
Same rationale as Receive_Failures.

Mapping (Permalink)

## Message_Part — a{sv}

Part of a message's content. In practice, this mapping never appears in isolation - messages are represented by a list of Message_Part mappings.

An example of how a rich-text message, with an embedded image, might look, in a Python-like syntax:

    [
      {
        'message-token': '9de9546a-3400-4419-a505-3ea270cb834c',
        'message-sender': 42,
        'message-sent': 1210067943,
        'message-received': 1210067947,
        'message-type': 0,              # = Channel_Text_Message_Type_Normal
        'pending-message-id': 437,
      },
      { 'alternative': 'main',
        'content-type': 'text/html',
        'content': 'Here is a photo of my cat:<br />' +
                   '<img src="cid:catphoto" alt="lol!" />' +
                   '<br />Isn't it cute?',
      },
      { 'alternative': 'main',
        'content-type': 'text/plain',
        'content': 'Here is a photo of my cat:\n[IMG: lol!]\nIsn't it cute?',
      },
      { 'identifier': 'catphoto',
        'content-type': 'image/jpeg',
        'size': 101000,
        'needs-retrieval': True,
      },
    ]

An example of how a non-text message — in particular, a vCard sent via SMS as implemented by telepathy-ring on Nokia's Maemo 5 — looks:

    [
      {
        'message-token': '9de9546a-3400-4419-a505-3ea270cb834c',
        'message-sender': 42,
        'message-sent': 1210067943,
        'message-received': 1210067947,
        'message-type': 0,              # = Channel_Text_Message_Type_Normal
        'pending-message-id': 437,
      },
      { 'content-type': 'text/x-vcard',
        'content': [ 0x66, 0x69, 0x71, ...], # vCard data as an array of bytes
      },
    ]

The first part of the message contains "headers" which refer to the entire message.

It is an error for a connection manager to put keys referring to the message as a whole in the second or subsequent Message_Part, but clients MUST recover from this error by ignoring these keys in the second and subsequent parts.

Instead of representing messages as aa{sv} where the first dictionary is special (a dictionary of headers), we could have used a signature like (a{sv}aa{sv}) to separate out the headers and the body parts.

However, this would make access to the messages more awkward. In Python, the syntax for access to a header field would remain `message[0]['message-type']`, but access to a body field in the second body part would change from message[2]['content'] to message[1][1]['content']. In GLib, the message would change from being a GPtrArray(GHashTable) to being a GValueArray(GHashTable, GPtrArray(GHashTable)) which is rather inconvenient to dereference.

Well-known keys for the message as a whole, and the corresponding value types, include:

message-token (s)

  An opaque, globally-unique identifier for the entire message. This MAY be treated as if it were a MIME Message-ID, e.g. for the mid: and cid: URI schemes. If omitted, there is no suitable token; the protocol-token key SHOULD be provided if the protocol identifies messages in some less unique way.

protocol-token (s - Protocol_Message_Token)

  An opaque token for the entire message, with whatever uniqueness guarantee is provided by the underlying protocol. As described for the Protocol_Message_Token type, this token is not guaranteed to be unique between contacts, or even within the scope of a Channel.

  In practice, in most protocols there is no token with the uniqueness guarantees demanded for message-token; the definition of message-token was inappropriate, but must now be preserved for the benefit of clients that rely on it, at least until Telepathy breaks backwards compatibility.

  The message-token and protocol-token SHOULD NOT both be present; clients requiring an identifier with the semantics of the protocol-token SHOULD look for the message-token first, falling back to the protocol-token.

  This is for compatibility with CMs older than the protocol-token key.

message-sent (x - Unix_Timestamp64)
  The time the message was sent (if unavailable, the time it arrived at a central server MAY be used). Omitted if no reasonable approximation is available; SHOULD always be present on outgoing messages.
message-received (x - Unix_Timestamp64)
  The time the message was received locally. SHOULD always be present.
message-sender (u - Contact_Handle)
  The contact who sent the message. If 0 or omitted, the contact who sent the message could not be determined.
message-type (u - Channel_Text_Message_Type)
  The type of message; if omitted, Channel_Text_Message_Type_Normal MUST be assumed. MAY be omitted for normal chat messages.
pending-message-id (u - Message_ID)
  The incoming message ID. This MUST NOT be present on outgoing messages. Clients SHOULD NOT store this key - it is only valid for as long as the message remains unacknowledged.
interface (s - DBus_Interface)
  This message is specific to the given interface, which is neither Text nor Messages. It SHOULD be ignored if that interface is not supported. (Note that an 'interface' key can also appear on the second and subsequent parts, where it indicates that that part (only) should be ignored if unsupported.)
scrollback (b)
  If present and true, the incoming message was part of a replay of message history (this matches the Scrollback flag in Channel_Text_Message_Flags). This flag does not make sense on outgoing messages and SHOULD NOT appear there.
rescued (b)
  If present and true, the incoming message has been seen in a previous channel during the lifetime of the Connection, but had not been acknowledged when that channel closed, causing an identical channel (in which the message now appears) to open. This matches the Rescued flag in Channel_Text_Message_Flags; it does not make sense on outgoing messages, and SHOULD NOT appear there.

The second and subsequent parts contain the message's content, including plain text, formatted text and/or attached files.

It is an error for a connection manager to put keys referring to the message body in the first Message_Part; clients MUST recover from this error by ignoring these keys in first part.

In any group of parts with the same non-empty value for the "alternative" key (which represent alternative versions of the same content), more faithful versions of the intended message MUST come before less faithful versions (note that this order is the opposite of MIME "multipart/alternative" parts). Clients SHOULD display the first alternative that they understand.

Specifying the preference order means that if the underlying protocol doesn't support alternatives, the CM can safely delete everything apart from the first supported alternative when sending messages.

The order is the reverse of MIME because MIME's rationale for placing the "plainest" part first (legibility in pre-MIME UAs) does not apply to us, and placing the most preferred part first simplifies display (a client can iterate the message in order, display the first alternative that it understands, and skip displaying all subsequent parts with the same "alternative" key).

Clients SHOULD present all parts that are not redundant alternatives in the order they appear in this array, possibly excluding parts that are referenced by another displayed part. It is implementation-specific how the parts are presented to the user.

This allows CMs to assume that all parts are actually shown to the user, even if they are not explicitly referenced - we do not yet recommend formatted text, and there is no way for plain text to reference an attachment since it has no concept of markup or references. This also forces clients to do something sensible with messages that consist entirely of "attachments", with no "body" at all.

For instance, when displaying the above example, a client that understands the HTML part should display the JPEG image once, between the two lines "Here is a photo of my cat:" and "Isn't it cute?"; it may additionally present the image in some way for a second time, after "Isn't it cute?", or may choose not to.

A client that does not understand HTML, displaying the same message, should display the plain-text part, followed by the JPEG image.

Well-known keys for the second and subsequent parts, and the corresponding value types, include:

identifier (s)
  An opaque identifier for this part. Parts of a message MAY reference other parts by treating this identifier as if it were a MIME Content-ID and using the cid: URI scheme.
alternative (s)

  If present, this part of the message is an alternative for all other parts with the same value for "alternative". Clients SHOULD only display one of them (this is expected to be used for XHTML messages in a future version of this specification).

  If omitted, this part is not an alternative for any other part.

  Parts of a message MAY reference the group of alternatives as a whole (i.e. a reference to whichever of them is chosen) by treating this identifier as if it were the MIME Content-ID of a multipart/alternative part, and using the cid: URI scheme.

content-type (s)

  The MIME type of this part. See the documentation for ReceivedMessage for notes on the special status of "text/plain" parts.

  Connection managers MUST NOT signal parts without a 'content-type' key; if a protocol provides no way to determine the MIME type, the connection manager is responsible for guessing it, but MAY fall back to "text/plain" for text and "application/octet-stream" for non-text.

  Clients MUST ignore parts without a 'content-type' key, which are reserved for future expansion.

lang (s)
  The natural language of this part, identified by a RFC 3066 language tag.
  XMPP allows alternative-selection by language as well as by content-type.
size (u)
  The size in bytes (if needs-retrieval is true, this MAY be an estimated or approximate size). SHOULD be omitted if 'content' is provided.
  There's no point in providing the size if you're already providing all the content.
thumbnail (b)

  This part is a thumbnail. To represent an image together with its thumbnail in a single message, there should be one part for the full image followed by a part for the thumbnail (following the “more complete versions first” requirement), with the same 'alternative' value. For example:

      [ ... ,
        { 'alternative': 'catphoto',
          'content-type': 'image/jpeg',
          'size': 150000,
          'content': [0xFF, 0xD8, ... 0xFF 0xD9],
        },
        { 'alternative': 'catphoto',
          'content-type': 'image/jpeg'
          'size': 1024,
          'thumbnail': True,
          'content': [0xFF, 0xD8, ... 0xFF 0xD9],
        },
        ...
      ]

needs-retrieval (b)
  If false or omitted, the connection manager already holds this part in memory. If present and true, this part will be retrieved on demand (like MIME's message/external-body), so clients should expect retrieval to take time; if this specification is later extended to provide a streaming version of GetPendingMessageContent, clients should use it for parts with this flag.
truncated (b)
  The content available via the 'content' key or GetPendingMessageContent has been truncated by the server or connection manager (equivalent to Channel_Text_Message_Flag_Truncated in the Text interface).
content (s or ay)
  The part's content, if it is available and sufficiently small to include here (implies that 'needs-retrieval' is false or omitted). Otherwise, omitted. If the part is human-readable text or HTML, the value for this key MUST be a UTF-8 string (D-Bus signature 's'). If the part is not text, the value MUST be a byte-array (D-Bus signature 'ay'). If the part is a text-based format that is not the main body of the message (e.g. an iCalendar or an attached XML document), the value SHOULD be a UTF-8 string, transcoding from another charset to UTF-8 if necessary, but MAY be a byte-array (of unspecified character set) if transcoding fails or the source charset is not known.
interface (s - DBus_Interface)
  This part is specific to the given interface, which is neither Text nor Messages. It SHOULD be ignored if that interface is not supported. (Note that an 'interface' key can also appear on the first part, where it indicates that the entire message should be ignored if unsupported.)

Delivery reports are also represented as messages, of type Channel_Text_Message_Type_Delivery_Report, with the Non_Text_Content flag in the Text interface.

Whenever a message of type Channel_Text_Message_Type_Delivery_Report is signalled for a delivery error report, Channel.Type.Text.SendError SHOULD also be emitted; whenever Channel.Type.Text.SendError is emitted by a channel which supports this interface, a message of type Channel_Text_Message_Type_Delivery_Report MUST also be emitted.

The corresponding message in the Messages interface MUST contain "headers" for the delivery report, as specified below, in its first Message_Part.

message-sender (u - Contact_Handle as defined above)
  MUST be the intended recipient of the original message, if available (zero or omitted if the intended recipient is unavailable or is not a contact, e.g. a chatroom), even if the delivery report actually came from an intermediate server.
message-type (u - Channel_Text_Message_Type as defined above)
  MUST be Channel_Text_Message_Type_Delivery_Report.
delivery-status (u - Delivery_Status)
  The status of the message. All delivery reports MUST contain this key in the first Message_Part.
delivery-token (s - Protocol_Message_Token)

  An identifier for the message to which this delivery report refers. MUST NOT be an empty string. Omitted if not available.

  Clients may match this against the token produced by the SendMessage method and MessageSent signal. A status report with no token could match any sent message, and a sent message with an empty token could match any status report. If multiple sent messages match, clients SHOULD use some reasonable heuristic.

  In an ideal world, we could unambiguously match reports against messages; however, deployed protocols are not ideal, and not all reports and messages can be matched.
delivery-error (u - Channel_Text_Send_Error)
  The reason for the failure. MUST be omitted if this was a successful delivery; SHOULD be omitted if it would be Channel_Text_Send_Error_Unknown.
delivery-dbus-error (s - DBus_Error_Name)
  The reason for the failure, specified as a (possibly implementation-specific) D-Bus error. MUST be omitted if this was a successful delivery. If set, the 'delivery-error' key SHOULD be set to the closest available value.
delivery-error-message (s)
  Debugging information on why the message could not be delivered. MUST be omitted if this was a successful delivery; MAY always be omitted.
delivery-echo (aa{sv} - Message_Part[])

  The message content, as defined by the Messages interface. Omitted if no content is available. Content MAY have been truncated, message parts MAY have been removed, and message parts MAY have had their content removed (i.e. the message part metadata is present, but the 'content' key is not).

  Some protocols, like XMPP, echo the failing message back to the sender. This is sometimes the only way to match it against the sent message, so we include it here.

  Unlike in the Messages interface, content not visible in the value for this key cannot be retrieved by another means, so the connection manager SHOULD be more aggressive about including (possibly truncated) message content in the 'content' key.

  The Messages interface needs to allow all content to be retrieved, but in this interface, the content we provide is merely a hint; so some is better than none, and it doesn't seem worth providing an API as complex as Messages' GetPendingMessageContent for the echoed message.

The second and subsequent Message_Part dictionaries, if present, are a human-readable report from the IM service.

Clients MUST NOT attempt to send delivery reports using the SendMessage method in the Messages API, and connection managers MUST NOT allow this to be done. If support for sending delivery reports is later added, it will be part of this interface.

Some example delivery reports in a Python-like syntax (in which arrays are indicated by [a, b] and dictionaries by {k1: v1, k2: v2}) follow.

A minimal delivery report indicating permanent failure of the sent message whose token was `b9a991bd-8845-4d7f-a704-215186f43bb4` for an unknown reason

      [{
      # header
      'message-sender': 123,
      'message-type': Channel_Text_Message_Type_Delivery_Report,
      'delivery-status': Delivery_Status_Permanently_Failed,
      'delivery-token': 'b9a991bd-8845-4d7f-a704-215186f43bb4',
      }
      # no body
      ]

A delivery report where the failed message is echoed back to the sender rather than being referenced by ID, and the failure reason is that this protocol cannot send messages to offline contacts such as the contact with handle 123

      [{ # header
      'message-sender': 123,
      'message-type': Channel_Text_Message_Type_Delivery_Report,
      'delivery-status': Delivery_Status_Temporarily_Failed,
      'delivery-error': Channel_Text_Send_Error_Offline,
      'delivery-echo':
          [{ # header of original message
          'message-sender': 1,
          'message-sent': 1210067943,
          },
          { # body of original message
          'content-type': 'text/plain',
          'content': 'Hello, world!',
          }]
        ],

      # no body
      ]

A maximally complex delivery report: the server reports a bilingual human-readable failure message because the user sent a message "Hello, world!" with token `b9a991bd-8845-4d7f-a704-215186f43bb4` to a contact with handle 123, but that handle represents a contact who does not actually exist

      [{ # header
      'message-sender': 123,
      'message-type': Channel_Text_Message_Type_Delivery_Report,
      'delivery-status': Delivery_Status_Permanently_Failed,
      'delivery-error': Channel_Text_Send_Error_Invalid_Contact,
      'delivery-token': 'b9a991bd-8845-4d7f-a704-215186f43bb4',
      'delivery-echo':
          [{ # header of original message
          'message-sender': 1,
          'message-sent': 1210067943,
          },
          { # body of original message
          'content-type': 'text/plain',
          'content': 'Hello, world!',
          }]
        ],
      },
      { # message from server (alternative in English)
      'alternative': '404',
      'content-type': 'text/plain',
      'lang': 'en',
      'content': 'I have no contact with that name',
      },
      { # message from server (alternative in German)
      'alternative': '404'.
      'content-type': 'text/plain',
      'lang': 'de',
      'content', 'Ich habe keinen Kontakt mit diesem Namen',
      }
      ]

A minimal delivery report indicating successful delivery of the sent message whose token was `b9a991bd-8845-4d7f-a704-215186f43bb4`

      [{
      # header
      'message-sender': 123,
      'message-type': Channel_Text_Message_Type_Delivery_Report,
      'delivery-status': Delivery_Status_Delivered,
      'delivery-token': 'b9a991bd-8845-4d7f-a704-215186f43bb4',
      }
      # no body
      ]

- Key — s
A key, which SHOULD be one of the well-known keys specified, if possible.
- Value — v
The value corresponding to the given key, which must be of one of the types indicated.

Mapping (Permalink)

## Message_Part_Content_Map — a{uv}

Added in 0.17.17.
A mapping from message part indexes to their content, as returned by GetPendingMessageContent.

- Part — u (Message_Part_Index)
Indexes into the array of Message_Parts that represents a message. The "headers" part (which is not a valid argument to GetPendingMessageContent) is considered to be part 0, so the valid part numbers start at 1 (for the second message part).
- Content — v
The message part's content. The variant MUST contain either type 's' or 'ay' (UTF-8 text string, or byte array), following the same rules as for the value of the 'content' key in the Message_Part mappings.