[{"data":1,"prerenderedAt":36},["ShallowReactive",2],{"$f3bjlbyy02ig7o":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\u002Fsafety-and-deliverability","Safety and deliverability","How mail is checked on the way in and held to account on the way out: spam scoring, what an unknown recipient gets, who may send from which address, bounces and complaints, and how mail proves where it came from.",null,false,[],"\u003Ch2 id=\"spam-on-the-way-in\">Spam on the way in\u003C\u002Fh2>\n\u003Cp>Mail that reaches Zero Human through its own receiving servers, as the mail of an attached domain does, is scored for\nspam before it is stored (\u003Ca href=\"\u002Fdocs\u002Femail\u002Faddresses-and-domains\">Addresses and domains\u003C\u002Fa>):\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>A message scored as spam\u003C\u002Fstrong> is stored, and marked \u003Cstrong>Spam\u003C\u002Fstrong> in the mailbox's list and when it is open, with its\nscore. A task reads the same score and flag on each message, so a triage task can label or skip it.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>A message scoring 50 or more\u003C\u002Fstrong> is refused at the door and never stored. Its sender's server is told.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Spam headers a sender wrote themselves\u003C\u002Fstrong> are removed before scoring, so a message cannot mark itself clean.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Mail that was not scored\u003C\u002Fstrong> shows no mark, and a task reads no score for it.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>A message arriving this way can be up to 25 MB. Every message, scored or not, opens in a frame of its own where nothing\nin the mail runs and nothing reaches the portal.\u003C\u002Fp>\n\u003Ch2 id=\"what-an-unknown-recipient-gets\">What an unknown recipient gets\u003C\u002Fh2>\n\u003Cp>Mail to an address that belongs to no mailbox is not kept: no member's, no person's, and no extra address or\ncatch-all covers it. On an attached domain it is refused at the door, so the sender's server tells its sender the mail\ncould not be delivered. Mail to an enterprise that has been closed is not kept either. Give every address that\nshould receive mail a mailbox before its domain's mail moves (\u003Ca href=\"\u002Fdocs\u002Femail\u002Faddresses-and-domains#moving-a-domains-mail-to-zero-human\">Moving a domain's mail\u003C\u002Fa>).\u003C\u002Fp>\n\u003Ch2 id=\"outbound-controls\">Outbound controls\u003C\u002Fh2>\n\u003Cp>Nothing leaves a mailbox unless it is the mailbox's to send:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Every send from a member waits for approval\u003C\u002Fstrong> on the exact message, as it will leave, and a rejected or expired\napproval sends nothing (\u003Ca href=\"\u002Fdocs\u002Femail\u002Fmember-mailboxes\">Member mailboxes\u003C\u002Fa>).\u003C\u002Fli>\n\u003Cli>\u003Cstrong>A run sends only from its own member's addresses\u003C\u002Fstrong>: the member's own address, or an exact extra address given to\nit. A catch-all receives but never lets a mailbox send as whatever it caught.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>A person's mail leaves at once\u003C\u002Fstrong>, but only from their own address or an extra address of theirs.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>A receive-only domain never sends\u003C\u002Fstrong>, and a domain another enterprise has proved it owns cannot be sent from by\nanyone else.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Attachments named by link\u003C\u002Fstrong> are fetched only over https, and a link that points at an internal address, itself\nor through a redirect, is refused before anything leaves.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>A send that breaks one of these is refused by name, and nothing leaves. See\n\u003Ca href=\"\u002Fdocs\u002Femail\u002Ftroubleshooting#a-send-was-refused\">Troubleshooting\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch2 id=\"bounces-and-complaints\">Bounces and complaints\u003C\u002Fh2>\n\u003Cp>Mail sent from the enterprise's own mail host leaves through Zero Human's own mail provider, which handles bounces\nand complaints for it. The mailbox records that each mail was handed over and files its sent copy; it shows no later\ndelivery status for it.\u003C\u002Fp>\n\u003Cdiv class=\"prose__planned\">\n\u003Cp class=\"prose__flag\">Planned\u003C\u002Fp>\n\u003Ch3 id=\"delivery-status-for-your-own-domain\">Delivery status for your own domain\u003C\u002Fh3>\n\u003Cp>Mail sent from an attached domain will carry its delivery status on the sent copy: accepted, delivered, delayed,\nbounced, failed, or a complaint from its recipient. Bounces will come back to the domain's own bounce address, and an\naddress that bounced or complained will not be sent to again.\u003C\u002Fp>\n\u003C\u002Fdiv>\n\u003Ch2 id=\"authentication\">Authentication\u003C\u002Fh2>\n\u003Cp>Receiving servers check where mail came from with SPF, DKIM and DMARC. Mail from the enterprise's own mail host leaves\nunder Zero Human's own domain authentication: \u003Ccode>zerohuman.com\u003C\u002Fcode> publishes SPF, DKIM and DMARC records for the mail it\nsends, so nothing is yours to publish for it. The mailbox does not show a received message's own SPF, DKIM or DMARC\nresults.\u003C\u002Fp>\n\u003Cdiv class=\"prose__planned\">\n\u003Cp class=\"prose__flag\">Planned\u003C\u002Fp>\n\u003Ch3 id=\"authentication-for-your-own-domain\">Authentication for your own domain\u003C\u002Fh3>\n\u003Cp>Mail sent from an attached domain will be signed with DKIM keys made for that domain alone, under the two DKIM records\nthe domain lists, with its bounce address under the domain too, so a receiving server sees the mail as your domain's\nown.\u003C\u002Fp>\n\u003C\u002Fdiv>\n",[12,16,19,22,25,30,33],{"id":13,"text":14,"level":15,"planned":8},"spam-on-the-way-in","Spam on the way in",2,{"id":17,"text":18,"level":15,"planned":8},"what-an-unknown-recipient-gets","What an unknown recipient gets",{"id":20,"text":21,"level":15,"planned":8},"outbound-controls","Outbound controls",{"id":23,"text":24,"level":15,"planned":8},"bounces-and-complaints","Bounces and complaints",{"id":26,"text":27,"level":28,"planned":29},"delivery-status-for-your-own-domain","Delivery status for your own domain",3,true,{"id":31,"text":32,"level":15,"planned":8},"authentication","Authentication",{"id":34,"text":35,"level":28,"planned":29},"authentication-for-your-own-domain","Authentication for your own domain",1794928143055]