Writing mail
How a mail is written and what it carries, from the portal, a task, an agent or code: formatting and Markdown, attachments, Cc and Bcc, quoted text, signatures, and the contacts a mailbox writes to.
Formatting
A reply, a forward or a new mail written in the portal has formatting: bold, italic, underline, bulleted and numbered lists, links and quotes. It leaves as a formatted mail with a plain-text copy, for mail clients that show no formatting. A forward carries the original with its own formatting below its forwarded-message line.
Mail written in Markdown
A task, an agent or a script can write its mail in Markdown, as models do, by giving markdown in place of text.
It leaves as a formatted mail: headings, bold and italics, lists, links, quotes, code and tables, with a line break
where the writer broke the line. The OS writes the plain-text copy from the formatted part, so it carries no Markdown
symbols, and each link is written out after its words. HTML typed into the Markdown is shown as text, never run.
A member's Markdown is rendered before its send waits for approval, so the approval card shows the formatted mail
exactly as it will leave. text, with optional html formatted by the writer, still works; a call that gives both
markdown and text (or markdown and html) is refused before anyone is asked to approve it.
Attachments
A mail can carry up to 10 files, 7 MB together; on a forward, the original's own files count towards the same limit. In the portal you add files to the mail you are writing. A task, an agent or a script names each file one of three ways: a public https link the OS fetches, a file already on a mail in the same mailbox, or the file's bytes. A file past the limit, one that cannot be read, or a link that is not https or does not answer is refused by name before anything leaves, and nothing is sent. The sent copy lists the files it carried.
To, Cc and Bcc
A mail goes to as many people as you name, in To, Cc and Bcc: at most 50 addresses in all. Everyone in
To and Cc sees who else the mail went to. Bcc reaches its people unseen: no recipient's copy names them, and only the
mailbox's own sent copy lists them. A reply's To starts with the mail's sender, and a person writing it can change
it or add people. Reply all answers the sender and copies in everyone else on the original, never the mailbox's
own addresses. A task's own reply always answers the mail's sender, or everyone on the original with replyAll.
Quoted text
A reply carries the mail it answers below it, after the signature, under an "On (date), (name) wrote:" line, as other
mail clients show a conversation: in a quote block in the formatted part, cleaned of anything that runs and of its
style sheet, and as lines starting > in the plain-text part. While you write a reply, Show quoted text under
the editor shows what will be quoted, and Remove quoted text sends it without. A task or a script leaves it off
with quote: false. A member's reply is quoted before it waits for approval, so nothing is quoted a second time, and
a very long original is quoted as its text, cut short if it has to be.
Signatures
The OS signs every mail a mailbox sends, the same way every time, so no task's instructions need to sign off. A
signature is written with the same formatting as a mail. The formatted part carries it as a block after the body;
the plain-text part carries it after a line holding -- . A signature is at most 20 KB. Add signature under the
editor, unticked, leaves it off one mail, and a task or a script does the same with signature: false. A member's
mail is signed before it waits for approval, so the approval card shows it as it will leave.
- A mailbox's own signature is set on its Signature tab: by the owner for a member's mailbox, and by the person for their own.
- A signature per address. Each extra address can carry a signature of its own. A mail sent from that address, and a reply to mail that arrived at it when it answers from itself, carries that signature; an address with none says Uses the mailbox signature.
- The enterprise template. An owner sets one signature for every mailbox in the company on the
Enterprise page, under Mail signature. It signs each
mailbox that has no signature of its own, filled in for that mailbox:
{name}is the mailbox's name,{role}the names of a member's roles (several joined with commas) or a person's job title from their profile,{address}the address the mail is sent from, and{enterprise}the company's name. A placeholder with nothing to fill it in is left empty, and any other word in braces is refused when you save, so a typo never reaches a mail. A change reaches the next mail of every mailbox that uses it. Use the enterprise signature on a mailbox's Signature tab switches it off for that mailbox.
With neither a signature of its own nor the template, a mailbox's mail leaves unsigned.
Contacts
A mailbox keeps contacts: everyone a send, reply or forward from it went to, in To, Cc and Bcc alike, saved once the mail has left, with the name they gave when it is a reply, and everyone added by hand. Mail that only arrived never makes a contact. The To, Cc and Bcc fields offer contacts from the second letter typed, then the enterprise's own people and members who have an address. The Contacts tab lists them, with Add contact, rename and remove; a name set by hand is kept, and a later reply never replaces it. A member's task looks a contact up and saves one without sending anything, so neither waits for approval.
Import and export
Import on the Contacts tab takes a CSV or vCard file of up to 1 MB and 5,000 contacts, such as the contacts export of the mail service or address book you are moving from. A CSV needs a header row with an email column, and reads a name from a name column or from first, middle and last names; a vCard gives its full name. Contacts are merged by address: a contact you already have keeps its name, and importing the same file again adds nothing. The tab says what was added, named, left alone and skipped. Export CSV and Export vCard download the mailbox's contacts, and either imports back to the same contacts.
Over the API
For a member's mailbox, a signed-in owner only: /v1/members/{id}/mail/signature (GET, PUT with { "html" } or
{ "text" }, DELETE), /v1/members/{id}/mail-aliases/{aliasId}/signature for one address's, and
/v1/members/{id}/mail/contacts, with /import and /export?format=csv|vcard under it. The enterprise template is
GET, PUT and DELETE on /v1/enterprise/mail/signature-template, for a signed-in owner only. A person's own
signature and contacts are under /v1/mail (Mail over MCP and the API).