[{"data":1,"prerenderedAt":40},["ShallowReactive",2],{"$fp2v1ei2yshuu":3},{"href":4,"title":5,"description":6,"kind":7,"mark":7,"planned":8,"contributors":9,"provenance":7,"express":8,"bridge":8,"html":10,"headings":11},"\u002Fdocs\u002Femail\u002Fwriting-mail","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.",null,false,[],"\u003Ch2 id=\"formatting\">Formatting\u003C\u002Fh2>\n\u003Cp>A reply, a forward or a new mail written in the portal has formatting: bold, italic, underline, bulleted and\nnumbered lists, links and quotes. It leaves as a formatted mail with a plain-text copy, for mail clients that show no\nformatting. A forward carries the original with its own formatting below its forwarded-message line.\u003C\u002Fp>\n\u003Ch2 id=\"mail-written-in-markdown\">Mail written in Markdown\u003C\u002Fh2>\n\u003Cp>A task, an agent or a script can write its mail in Markdown, as models do, by giving \u003Ccode>markdown\u003C\u002Fcode> in place of \u003Ccode>text\u003C\u002Fcode>.\nIt leaves as a formatted mail: headings, bold and italics, lists, links, quotes, code and tables, with a line break\nwhere the writer broke the line. The OS writes the plain-text copy from the formatted part, so it carries no Markdown\nsymbols, and each link is written out after its words. HTML typed into the Markdown is shown as text, never run.\u003C\u002Fp>\n\u003Cp>A member's Markdown is rendered before its send waits for approval, so the approval card shows the formatted mail\nexactly as it will leave. \u003Ccode>text\u003C\u002Fcode>, with optional \u003Ccode>html\u003C\u002Fcode> formatted by the writer, still works; a call that gives both\n\u003Ccode>markdown\u003C\u002Fcode> and \u003Ccode>text\u003C\u002Fcode> (or \u003Ccode>markdown\u003C\u002Fcode> and \u003Ccode>html\u003C\u002Fcode>) is refused before anyone is asked to approve it.\u003C\u002Fp>\n\u003Ch2 id=\"attachments\">Attachments\u003C\u002Fh2>\n\u003Cp>A mail can carry up to 10 files, 7 MB together; on a forward, the original's own files count towards the same limit.\nIn the portal you add files to the mail you are writing. A task, an agent or a script names each file one of three\nways: a public https link the OS fetches, a file already on a mail in the same mailbox, or the file's bytes. A file\npast the limit, one that cannot be read, or a link that is not https or does not answer is refused by name before\nanything leaves, and nothing is sent. The sent copy lists the files it carried.\u003C\u002Fp>\n\u003Ch2 id=\"to-cc-and-bcc\">To, Cc and Bcc\u003C\u002Fh2>\n\u003Cp>A mail goes to as many people as you name, in \u003Cstrong>To\u003C\u002Fstrong>, \u003Cstrong>Cc\u003C\u002Fstrong> and \u003Cstrong>Bcc\u003C\u002Fstrong>: at most 50 addresses in all. Everyone in\nTo and Cc sees who else the mail went to. Bcc reaches its people unseen: no recipient's copy names them, and only the\nmailbox's own sent copy lists them. A reply's \u003Cstrong>To\u003C\u002Fstrong> starts with the mail's sender, and a person writing it can change\nit or add people. \u003Cstrong>Reply all\u003C\u002Fstrong> answers the sender and copies in everyone else on the original, never the mailbox's\nown addresses. A task's own reply always answers the mail's sender, or everyone on the original with \u003Ccode>replyAll\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Ch2 id=\"quoted-text\">Quoted text\u003C\u002Fh2>\n\u003Cp>A reply carries the mail it answers below it, after the signature, under an &quot;On (date), (name) wrote:&quot; line, as other\nmail clients show a conversation: in a quote block in the formatted part, cleaned of anything that runs and of its\nstyle sheet, and as lines starting \u003Ccode>&gt; \u003C\u002Fcode> in the plain-text part. While you write a reply, \u003Cstrong>Show quoted text\u003C\u002Fstrong> under\nthe editor shows what will be quoted, and \u003Cstrong>Remove quoted text\u003C\u002Fstrong> sends it without. A task or a script leaves it off\nwith \u003Ccode>quote: false\u003C\u002Fcode>. A member's reply is quoted before it waits for approval, so nothing is quoted a second time, and\na very long original is quoted as its text, cut short if it has to be.\u003C\u002Fp>\n\u003Ch2 id=\"signatures\">Signatures\u003C\u002Fh2>\n\u003Cp>The OS signs every mail a mailbox sends, the same way every time, so no task's instructions need to sign off. A\nsignature is written with the same formatting as a mail. The formatted part carries it as a block after the body;\nthe plain-text part carries it after a line holding \u003Ccode>-- \u003C\u002Fcode>. A signature is at most 20 KB. \u003Cstrong>Add signature\u003C\u002Fstrong> under the\neditor, unticked, leaves it off one mail, and a task or a script does the same with \u003Ccode>signature: false\u003C\u002Fcode>. A member's\nmail is signed before it waits for approval, so the approval card shows it as it will leave.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>A mailbox's own signature\u003C\u002Fstrong> is set on its \u003Cstrong>Signature\u003C\u002Fstrong> tab: by the owner for a member's mailbox, and by the person\nfor their own.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>A signature per address.\u003C\u002Fstrong> Each extra address can carry a signature of its own. A mail sent from that address,\nand a reply to mail that arrived at it when it answers from itself, carries that signature; an address with none\nsays \u003Cstrong>Uses the mailbox signature\u003C\u002Fstrong>.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>The enterprise template.\u003C\u002Fstrong> An owner sets one signature for every mailbox in the company on the\n\u003Ca href=\"\u002Fdocs\u002Fcompany\u002Fenterprise#settings-on-the-enterprise-page\">Enterprise page\u003C\u002Fa>, under \u003Cstrong>Mail signature\u003C\u002Fstrong>. It signs each\nmailbox that has no signature of its own, filled in for that mailbox: \u003Ccode>{name}\u003C\u002Fcode> is the mailbox's name, \u003Ccode>{role}\u003C\u002Fcode> the\nnames of a member's roles (several joined with commas) or a person's job title from their profile, \u003Ccode>{address}\u003C\u002Fcode> the\naddress the mail is sent from, and \u003Ccode>{enterprise}\u003C\u002Fcode> the company's name. A placeholder with nothing to fill it in is\nleft empty, and any other word in braces is refused when you save, so a typo never reaches a mail. A change reaches\nthe next mail of every mailbox that uses it. \u003Cstrong>Use the enterprise signature\u003C\u002Fstrong> on a mailbox's Signature tab switches\nit off for that mailbox.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>With neither a signature of its own nor the template, a mailbox's mail leaves unsigned.\u003C\u002Fp>\n\u003Ch2 id=\"contacts\">Contacts\u003C\u002Fh2>\n\u003Cp>A mailbox keeps contacts: everyone a send, reply or forward from it went to, in To, Cc and Bcc alike, saved once the\nmail has left, with the name they gave when it is a reply, and everyone added by hand. Mail that only arrived never\nmakes a contact. The \u003Cstrong>To\u003C\u002Fstrong>, \u003Cstrong>Cc\u003C\u002Fstrong> and \u003Cstrong>Bcc\u003C\u002Fstrong> fields offer contacts from the second letter typed, then the\nenterprise's own people and members who have an address. The \u003Cstrong>Contacts\u003C\u002Fstrong> tab lists them, with \u003Cstrong>Add contact\u003C\u002Fstrong>, rename\nand remove; a name set by hand is kept, and a later reply never replaces it. A member's task looks a contact up and\nsaves one without sending anything, so neither waits for approval.\u003C\u002Fp>\n\u003Ch2 id=\"import-and-export\">Import and export\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>Import\u003C\u002Fstrong> on the \u003Cstrong>Contacts\u003C\u002Fstrong> tab takes a CSV or vCard file of up to 1 MB and 5,000 contacts, such as the contacts\nexport of the mail service or address book you are moving from. A CSV needs a header row with an email column, and\nreads a name from a name column or from first, middle and last names; a vCard gives its full name. Contacts are merged\nby address: a contact you already have keeps its name, and importing the same file again adds nothing. The tab says\nwhat was added, named, left alone and skipped. \u003Cstrong>Export CSV\u003C\u002Fstrong> and \u003Cstrong>Export vCard\u003C\u002Fstrong> download the mailbox's contacts,\nand either imports back to the same contacts.\u003C\u002Fp>\n\u003Ch2 id=\"over-the-api\">Over the API\u003C\u002Fh2>\n\u003Cp>For a member's mailbox, a signed-in owner only: \u003Ccode>\u002Fv1\u002Fmembers\u002F{id}\u002Fmail\u002Fsignature\u003C\u002Fcode> (\u003Ccode>GET\u003C\u002Fcode>, \u003Ccode>PUT\u003C\u002Fcode> with \u003Ccode>{ &quot;html&quot; }\u003C\u002Fcode> or\n\u003Ccode>{ &quot;text&quot; }\u003C\u002Fcode>, \u003Ccode>DELETE\u003C\u002Fcode>), \u003Ccode>\u002Fv1\u002Fmembers\u002F{id}\u002Fmail-aliases\u002F{aliasId}\u002Fsignature\u003C\u002Fcode> for one address's, and\n\u003Ccode>\u002Fv1\u002Fmembers\u002F{id}\u002Fmail\u002Fcontacts\u003C\u002Fcode>, with \u003Ccode>\u002Fimport\u003C\u002Fcode> and \u003Ccode>\u002Fexport?format=csv|vcard\u003C\u002Fcode> under it. The enterprise template is\n\u003Ccode>GET\u003C\u002Fcode>, \u003Ccode>PUT\u003C\u002Fcode> and \u003Ccode>DELETE\u003C\u002Fcode> on \u003Ccode>\u002Fv1\u002Fenterprise\u002Fmail\u002Fsignature-template\u003C\u002Fcode>, for a signed-in owner only. A person's own\nsignature and contacts are under \u003Ccode>\u002Fv1\u002Fmail\u003C\u002Fcode> (\u003Ca href=\"\u002Fdocs\u002Femail\u002Fmcp-and-api\">Mail over MCP and the API\u003C\u002Fa>).\u003C\u002Fp>\n",[12,16,19,22,25,28,31,34,37],{"id":13,"text":14,"level":15,"planned":8},"formatting","Formatting",2,{"id":17,"text":18,"level":15,"planned":8},"mail-written-in-markdown","Mail written in Markdown",{"id":20,"text":21,"level":15,"planned":8},"attachments","Attachments",{"id":23,"text":24,"level":15,"planned":8},"to-cc-and-bcc","To, Cc and Bcc",{"id":26,"text":27,"level":15,"planned":8},"quoted-text","Quoted text",{"id":29,"text":30,"level":15,"planned":8},"signatures","Signatures",{"id":32,"text":33,"level":15,"planned":8},"contacts","Contacts",{"id":35,"text":36,"level":15,"planned":8},"import-and-export","Import and export",{"id":38,"text":39,"level":15,"planned":8},"over-the-api","Over the API",1794928143069]