[{"data":1,"prerenderedAt":28},["ShallowReactive",2],{"$f2wnsxkrkc8z5a":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\u002Fmail-in-tasks","Mail in tasks","A member's tasks read, file and answer the member's own mailbox with the OS's built-in mail tools. Every send waits for approval on the exact message first.",null,false,[],"\u003Ch2 id=\"whose-mailbox-a-run-reads\">Whose mailbox a run reads\u003C\u002Fh2>\n\u003Cp>A run reads the mailbox of the member doing it, and no other: a member named in the call is ignored, and the OS's own\ntasks have no member, so no mailbox. A task needs no tool binding for it. The mail tools are part of the OS's\n\u003Ca href=\"\u002Fdocs\u002Ftools\u002Fbuilt-in\">built-in tools\u003C\u002Fa>, and a task calls the ones it declares, like any other tool\n(\u003Ca href=\"\u002Fdocs\u002Fcontrol\u002Fgates\">Gates and tool scopes\u003C\u002Fa>).\u003C\u002Fp>\n\u003Ch2 id=\"reading-and-filing\">Reading and filing\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Ccode>os.mail_list\u003C\u002Fcode> lists the mailbox, newest first, with filters for unread mail, a label, a handled state or one\nconversation. Each row carries its labels, its handled state and, when the mail was scored, its spam score.\u003C\u002Fli>\n\u003Cli>\u003Ccode>os.mail_read\u003C\u002Fcode> opens one message: its text, its formatted part and the names of its attachments. Reading marks it\nread, as opening it in the portal does.\u003C\u002Fli>\n\u003Cli>\u003Ccode>os.mail_set_label\u003C\u002Fcode> and \u003Ccode>os.mail_set_handled\u003C\u002Fcode> record what the task decided about one message: its labels, and\nwhether it is unhandled, replied, skipped, escalated to the owner, or snoozed until a date. \u003Ccode>os.mail_set_many\u003C\u002Fcode> makes\none such change on many messages at once, by id or for every unhandled message from one sender.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The portal shows the labels as tabs and the handled state as Inbox or Archive\n(\u003Ca href=\"\u002Fdocs\u002Femail\u002Fmember-mailboxes\">Member mailboxes\u003C\u002Fa>).\u003C\u002Fp>\n\u003Ch2 id=\"answering-and-sending\">Answering and sending\u003C\u002Fh2>\n\u003Cp>\u003Ccode>os.mail_reply\u003C\u002Fcode> replies to a message in the mailbox, from the address it arrived at and threaded under it, and\n\u003Ccode>os.mail_send\u003C\u002Fcode> sends a new one. Both take the body as \u003Ccode>markdown\u003C\u002Fcode>, or as \u003Ccode>text\u003C\u002Fcode> with optional \u003Ccode>html\u003C\u002Fcode>, and attachments,\nTo, Cc and Bcc as \u003Ca href=\"\u002Fdocs\u002Femail\u002Fwriting-mail\">Writing mail\u003C\u002Fa> describes. The OS adds the mailbox's signature and, on a\nreply, the quoted original, unless the call says \u003Ccode>signature: false\u003C\u002Fcode> or \u003Ccode>quote: false\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Every send waits for approval on the exact message first.\u003C\u002Fstrong> The call opens a gate, the approval card shows the mail\nexactly as it will leave, signature and quote included, and approving it sends that and nothing more. A rejected or\nexpired gate sends nothing, and the message the reply answered is closed. Nobody can declare these sends ungated: a\nmember never sends mail nobody approved. See \u003Ca href=\"\u002Fdocs\u002Fcontrol\u002Fgates\">Gates and tool scopes\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>A run can only send from an address that delivers to its own member's mailbox. A send from any other address is\nrefused before anyone is asked to approve it.\u003C\u002Fp>\n\u003Ch2 id=\"contacts-and-follow-ups\">Contacts and follow-ups\u003C\u002Fh2>\n\u003Cp>\u003Ccode>os.mail_contacts\u003C\u002Fcode> looks up the mailbox's contacts by part of a name or an address, so &quot;mail Sarah from Acme&quot; finds\nthe address, and \u003Ccode>os.mail_contact_save\u003C\u002Fcode> saves one. Neither sends anything, so neither waits for approval.\u003C\u002Fp>\n\u003Cp>A task that chases replies can ask for the conversations where the member had the last word and nobody has answered\nfor three weekdays, mark one as chased today, or snooze one until a later date. Its follow-up is a reply like any\nother, and waits for approval. The full list of mail tools, with every field, is in the\n\u003Ca href=\"\u002Fdocs\u002Ftools\u002Fbuilt-in\u002Fos\">built-in tools reference\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch2 id=\"buttons-that-start-a-task\">Buttons that start a task\u003C\u002Fh2>\n\u003Cp>A task can declare a mailbox button, so a mailbox offers it as one click above its list or on an open mail. Pressing\nit starts the task over that mailbox: a member's, for a task that runs as a role the member holds, or a person's own,\nwhere the run reads and files the person's mail under the same gates. See\n\u003Ca href=\"\u002Fdocs\u002Femail\u002Fmember-mailboxes#mailbox-buttons-and-their-schedules\">Member mailboxes\u003C\u002Fa> and\n\u003Ca href=\"\u002Fdocs\u002Femail\u002Fperson-mailboxes\">Person mailboxes\u003C\u002Fa>.\u003C\u002Fp>\n",[12,16,19,22,25],{"id":13,"text":14,"level":15,"planned":8},"whose-mailbox-a-run-reads","Whose mailbox a run reads",2,{"id":17,"text":18,"level":15,"planned":8},"reading-and-filing","Reading and filing",{"id":20,"text":21,"level":15,"planned":8},"answering-and-sending","Answering and sending",{"id":23,"text":24,"level":15,"planned":8},"contacts-and-follow-ups","Contacts and follow-ups",{"id":26,"text":27,"level":15,"planned":8},"buttons-that-start-a-task","Buttons that start a task",1794928142972]