Version 0.19.0
This document describes how emails can be used to implement typical messenger functions while staying compatible to existing MUAs.
- Encryption
- Outgoing messages
- Incoming messages
- Forwarded messages
- Groups
- Set profile image
- Miscellaneous
Messages SHOULD be encrypted by the Autocrypt standard; prefer-encrypt=mutual MAY be set by default.
Meta data (at least the subject and all chat-headers) SHOULD be encrypted by the Memoryhole standard.
If Memoryhole is not used, the subject of encrypted messages SHOULD be replaced by the string
Chat: Encrypted message where the part after the colon MAY be localized.
Messengers MUST add a Chat-Version: 1.0 header to outgoing messages.
For filtering and smart appearance of the messages in normal MUAs,
the Subject header SHOULD start with the characters Chat: and SHOULD be an excerpt of the message.
Replies to messages MAY follow the typical Re:-format.
The body MAY contain text which MUST have the content type text/plain
or mulipart/alternative containing text/plain.
The text MAY be divided into a user-text-part and a footer-part using the
line -- (minus, minus, space, lineend).
The user-text-part MUST contain only user generated content. User generated content are eg. texts a user has actually typed or pasted or forwarded from another user. Full quotes, footers or sth. like that MUST NOT go to the user-text-part.
From: sender@domain
To: rcpt@domain
Chat-Version: 1.0
Content-Type: text/plain
Subject: Chat: Hello ...
Hello world!
The Chat-Version header MAY be used to detect if a messages comes from a compatible messenger.
The Subject header MUST NOT be used to detect compatible messengers, groups or whatever.
Messenger SHOULD show the Subject if the message comes from a normal MUA together with the email-body.
The email-body SHOULD be converted to plain text, full-quotes and similar regions SHOULD be cut.
Attachments SHOULD be shown where possible. If an attachment cannot be shown, a non-distracting warning SHOULD be printed.
Forwarded messages are outgoing messages that contain a forwarded-header before the user generated content.
The forwarded header MUST contain two lines:
The first line contains the text
---------- Forwarded message ----------
(10 minus, space, text Forwarded message, space, 10 minus).
The second line starts with From: followed by the original sender
which SHOULD be anonymized or just a placeholder.
From: sender@domain
To: rcpt@domain
Chat-Version: 1.0
Content-Type: text/plain
Subject: Chat: Forwarded message
---------- Forwarded message ----------
From: Messenger
Hello world!
Incoming forwarded messages are detected by the header. The messenger SHOULD mark these messages in a way that it becomes obvious that the message is not created by the sender. Note that most messengers do not show the original sender with forwarded messages but MUAs typically expose the sender in the UI.
Groups are chats with usually more than one recipient, each defined by an email-address. The sender plus the recipients are the group members.
To allow different groups with the same members, groups are identified by a group-id.
The group-id MUST be created only from the characters 0-9, A-Z, a-z _ and -.
Groups MUST have a group-name. The group-name is any non-zero-length UTF-8 string.
Groups MAY have a group-image.
All group members MUST be added to the From/To headers.
The group-id MUST be written to the Chat-Group-ID header.
The group-name MUST be written to Chat-Group-Name header (the forced presence of this header makes it easier to join a group chat on a second device any time).
The Subject header of outgoing group messages SHOULD start with the characters Chat: followed by the group-name and a colon followed by an excerpt of the message.
To identify the group-id on replies from normal MUAs, the group-id MUST also be added to
the message-id of outgoing messages. The message-id MUST have the
format Gr.<group-id>.<unique data>.
From: member1@domain
To: member2@domain, member3@domain
Chat-Version: 1.0
Chat-Group-ID: 1234xyZ
Chat-Group-Name: My Group
Message-ID: Gr.1234xyZ.0001@domain
Subject: Chat: My Group: Hello group ...
Hello group - this group contains three members
Messengers adding the member list in the form Name <email-address> MUST take care only to spread the names authorized by the contacts themselves.
Otherwise, names as Daddy or Honey may be spread (this issue is also true for normal MUAs, however, for more contact- and chat-centralized apps
such situations happen more frequently).
The messenger MUST search incoming messages for the group-id in the following headers: Chat-Group-ID,
Message-ID, In-Reply-To and References (in this order).
If the messenger finds a valid and existent group-id, the message SHOULD be assigned to the given group.
If the messenger finds a valid but not existent group-id, the messenger MAY create a new group.
If no group-id is found, the message MAY be assigned to a normal single-user chat with the email-address given in From.
Messenger clients MUST construct the member list from the From/To headers only on the first group message or if they see a Chat-Group-Member-Added or Chat-Group-Member-Removed action header.
Both headers MUST have the email-address of the added or removed member as the value.
Messenger clients MUST NOT construct the member list on other group messages (this is to avoid accidentally altered To-lists in normal MUAs; the user
does not expect adding a user to a message will also add him to the group "forever").
The messenger SHOULD send an explicit mail for each added or removed member. The body of the message SHOULD contain a localized description about what happened and the message SHOULD appear as a message or action from the sender.
From: member1@domain
To: member2@domain, member3@domain, member4@domain
Chat-Version: 1.0
Chat-Group-ID: 1234xyZ
Chat-Group-Name: My Group
Chat-Group-Member-Added: member4@domain
Message-ID: Gr.1234xyZ.0002@domain
Subject: Chat: My Group: Hello, ...
Hello, I've added member4@domain to our group. Now we have 4 members.
To remove a member:
From: member1@domain
To: member2@domain, member3@domain
Chat-Version: 1.0
Chat-Group-ID: 1234xyZ
Chat-Group-Name: My Group
Chat-Group-Member-Removed: member4@domain
Message-ID: Gr.1234xyZ.0003@domain
Subject: Chat: My Group: Hello, ...
Hello, I've removed member4@domain from our group. Now we have 3 members.
To change the group-name,
the messenger MUST send the action header Chat-Group-Name-Changed
with the value set to the old group name to all group members.
The new group name goes to the header Chat-Group-Name.
The messenger SHOULD send an explicit mail for each name change. The body of the message SHOULD contain a localized description about what happened and the message SHOULD appear as a message or action from the sender.
From: member1@domain
To: member2@domain, member3@domain
Chat-Version: 1.0
Chat-Group-ID: 1234xyZ
Chat-Group-Name: Our Group
Chat-Group-Name-Changed: My Group
Message-ID: Gr.1234xyZ.0004@domain
Subject: Chat: Our Group: Hello, ...
Hello, I've changed the group name from "My Group" to "Our Group".
A group MAY have a group-image.
To change or set the group-image, the messenger MUST attach an image file to a message and MUST add the header Chat-Group-Image with the
value set to the image name.
To remove the group-image, the messenger MUST add the header Chat-Group-Image: 0.
The messenger SHOULD send an explicit mail for each group image change. The body of the message SHOULD contain a localized description about what happened and the message SHOULD appear as a message or action from the sender.
From: member1@domain
To: member2@domain, member3@domain
Chat-Version: 1.0
Chat-Group-ID: 1234xyZ
Chat-Group-Name: Our Group
Chat-Group-Image: image.jpg
Message-ID: Gr.1234xyZ.0005@domain
Subject: Chat: Our Group: Hello, ...
Content-Type: multipart/mixed; boundary="==break=="
--==break==
Content-Type: text/plain
Hello, I've changed the group image.
--==break==
Content-Type: image/jpeg
Content-Disposition: attachment; filename="image.jpg"
/9j/4AAQSkZJRgABAQAAAQABAAD/2wBDAAYEBQYFBAYGBQYHBw ...
--==break==--
The image format SHOULD be image/jpeg or image/png. To save data, it is RECOMMENDED to add a Chat-Group-Image only on image changes.
A user MAY have a profile-image that MAY be spread to his contacts.
To change or set the profile-image, the messenger MUST attach an image file to a message and MUST add the header Chat-Profile-Image with the
value set to the image name.
To remove the profile-image, the messenger MUST add the header Chat-Profile-Image: 0.
To spread the image, the messenger MAY send the profile image together with the next mail to a given contact
(to do this only once, the messenger has to keep a profile_image_update_state somewhere).
Alternatively, the messenger MAY send an explicit mail for each profile-image change to all contacts using a compatible messenger.
The messenger SHOULD NOT send an explicit mail to normal MUAs.
From: sender@domain
To: rcpt@domain
Chat-Version: 1.0
Chat-Profile-Image: photo.jpg
Subject: Chat: Hello, ...
Content-Type: multipart/mixed; boundary="==break=="
--==break==
Content-Type: text/plain
Hello, I've changed my profile image.
--==break==
Content-Type: image/jpeg
Content-Disposition: attachment; filename="photo.jpg"
AKCgkJi3j4l5kjoldfUAKCgkJi3j4lldfHjgWICwgIEBQYFBA ...
--==break==--
The image format SHOULD be image/jpeg or image/png. Note that Chat-Profile-Image may appear together with all other headers, eg. there may be a
Chat-Profile-Image and a Chat-Group-Image header in the same message. To save data, it is RECOMMENDED to add a Chat-Profile-Image header only on image changes.
Messengers SHOULD use the header Chat-Predecessor instead of In-Reply-To as
the latter one results in infinite threads on typical MUAs.
Messengers SHOULD add a Chat-Voice-message: 1 header if an attached audio file is a voice message.
Messengers MAY add a Chat-Duration header to specify the duration of attached audio or video files.
The value MUST be the duration in milliseconds.
This allows the receiver to show the time without knowing the file format.
Chat-Predecessor: foo123@domain
Chat-Voice-Message: 1
Chat-Duration: 10000
Messengers MAY send and receive Message Disposition Notifications (MDNs, RFC 8098, RFC 3503)
using the Chat-Disposition-Notification-To header instead of the Disposition-Notification-To (which unfortunately forces many other MUAs to send weird mails not following any
standard).
If some action is required by a message header, the action should only be performed if the effective date is newer than the date the last action was performed.
We define the effective date of a message as the sending time of the message as indicated by its Date header, or the time of first receipt if that date is in the future or unavailable.
Licensed under the CC0, see LICENSE file for details. Different implementations and libraries are licensed under different licenses.
Copyright © 2017-2019 Delta Chat contributors.