[{"data":1,"prerenderedAt":51},["ShallowReactive",2],{"$f28vj7h77j8mk4":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\u002Faddresses-and-domains","Addresses and domains","Every enterprise receives mail on its own host under zerohuman.com. An owner can also attach a domain the company owns, prove it, and move the domain's mail onto Zero Human, one record at a time and with a way back.",null,false,[],"\u003Ch2 id=\"the-enterprises-own-mail-host\">The enterprise's own mail host\u003C\u002Fh2>\n\u003Cp>Every enterprise has a mail host from the day it is created: its slug under \u003Ccode>zerohuman.com\u003C\u002Fcode>. An enterprise with the\nslug \u003Ccode>northstar\u003C\u002Fcode> receives mail at \u003Ccode>northstar.zerohuman.com\u003C\u002Fcode>, and its members get addresses such as\n\u003Ccode>jules@northstar.zerohuman.com\u003C\u002Fcode>. The slug is chosen when the enterprise is created and the portal has no way to change\nit later, so the host stays the same for the life of the company (\u003Ca href=\"\u002Fdocs\u002Fcompany\u002Fenterprise#its-address\">Enterprise\u003C\u002Fa>).\u003C\u002Fp>\n\u003Cp>A member's address is made from its name: lower case, accents dropped, and spaces and dashes turned into dots, so\nMary-Jane van Dyke would be \u003Ccode>mary.jane.van.dyke@northstar.zerohuman.com\u003C\u002Fcode>. The part before the \u003Ccode>@\u003C\u002Fcode> is cut to 64\ncharacters. Mail sent to an address with a \u003Ccode>+\u003C\u002Fcode> tag, such as \u003Ccode>jules+github@northstar.zerohuman.com\u003C\u002Fcode>, reaches the same\nmailbox. A person's address is the one an owner gives them (\u003Ca href=\"\u002Fdocs\u002Femail\u002Fperson-mailboxes\">Person mailboxes\u003C\u002Fa>).\u003C\u002Fp>\n\u003Cp>No two mailboxes can hold the same address: not two members, not a member and a person, and not an extra address that\nsomebody else already holds.\u003C\u002Fp>\n\u003Ch2 id=\"extra-addresses\">Extra addresses\u003C\u002Fh2>\n\u003Cp>A member's or a person's mailbox can have extra addresses that deliver to it, on any of the enterprise's domains. An\nowner adds them under \u003Cstrong>Email aliases\u003C\u002Fstrong> on the member's page, or under the person's address on \u003Cstrong>People\u003C\u002Fstrong>:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>An exact address\u003C\u002Fstrong>, such as \u003Ccode>support@northstar.zerohuman.com\u003C\u002Fcode>, for a mailbox that answers as more than one name.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>A plus tag\u003C\u002Fstrong>, such as \u003Ccode>jules+news@northstar.zerohuman.com\u003C\u002Fcode>, kept under its own address.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>A catch-all\u003C\u002Fstrong>, written \u003Ccode>*@\u003C\u002Fcode> and the domain, which takes every address on that domain that nobody else holds.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Each extra address says whether a reply to mail that arrived at it goes out from it (the default) or from the\nmailbox's own address. A catch-all only receives: a mailbox sends from its own address and the exact addresses it has\nbeen given, never from whatever a catch-all happened to catch.\u003C\u002Fp>\n\u003Ch2 id=\"attaching-a-domain-you-own\">Attaching a domain you own\u003C\u002Fh2>\n\u003Cp>An owner attaches a domain the company owns on \u003Cstrong>Domains\u003C\u002Fstrong>, under \u003Cstrong>Settings\u003C\u002Fstrong> in the portal. Only an owner who is\nsigned in can attach, check, change or detach a domain; anyone whose grant covers \u003Ccode>enterprise\u003C\u002Fcode>, an API token included,\ncan read the list and see what each domain still waits on.\u003C\u002Fp>\n\u003Cp>Zero Human never gets access to the account at the company where you bought the domain. You add a few records there,\nand Zero Human only reads what you published. The portal and the API keep their own addresses whatever you choose.\u003C\u002Fp>\n\u003Cp>A domain can be attached by one enterprise only, and a name under \u003Ccode>zerohuman.com\u003C\u002Fcode> cannot be attached at all.\u003C\u002Fp>\n\u003Ch3 id=\"three-choices-for-its-mail\">Three choices for its mail\u003C\u002Fh3>\n\u003Cp>Attaching asks what happens to the domain's mail. Nothing is chosen for you:\u003C\u002Fp>\n\u003Cdiv class=\"prose__table\">\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Choice\u003C\u002Fth>\n\u003Cth>What it does\u003C\u002Fth>\n\u003Cth>Records it needs\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Receive email at\u003C\u002Fstrong> the domain\u003C\u002Ftd>\n\u003Ctd>Receive-only. Mail to the domain arrives in Zero Human instead of where it arrives today. Nobody can send or reply from it.\u003C\u002Ftd>\n\u003Ctd>Ownership and MX\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Send and receive email at\u003C\u002Fstrong> the domain\u003C\u002Ftd>\n\u003Ctd>All of the domain's mail moves to Zero Human. It receives as a receive-only domain does; sending from it is planned (below).\u003C\u002Ftd>\n\u003Ctd>Ownership, MX, DKIM and the bounce record\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Keep email on\u003C\u002Fstrong> your own mail host\u003C\u002Ftd>\n\u003Ctd>Nothing happens to the domain's mail: it is only checked to prove it is yours.\u003C\u002Ftd>\n\u003Ctd>Ownership\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003C\u002Fdiv>\n\u003Cp>With Send and receive, the domain also lists what sending from it still waits on, as of its last check, and a send\nfrom one of its addresses is refused until every sending check passes.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Receive email only\u003C\u002Fstrong> and \u003Cstrong>Send and receive email\u003C\u002Fstrong> on an attached domain switch between the first two at any time,\nand \u003Cstrong>Keep email on\u003C\u002Fstrong> your mail host switches to the third. The next mail reads the new choice.\u003C\u002Fp>\n\u003Ch3 id=\"the-records\">The records\u003C\u002Fh3>\n\u003Cp>The domain lists every record still to publish, in a table to copy into your domain company's form: its type, its\npriority, its name, its value, and whether it is for ownership or for email.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Ownership.\u003C\u002Fstrong> One TXT record at \u003Ccode>_zerohuman-verification\u003C\u002Fcode> under the domain, holding a value made for this claim\nalone. It proves the domain is yours, and nothing changes until it is published and checked.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>MX.\u003C\u002Fstrong> Three MX records at the domain itself, at priorities 10, 20 and 30. They send the domain's mail to Zero Human.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>DKIM.\u003C\u002Fstrong> Two CNAME records, \u003Ccode>zh1._domainkey\u003C\u002Fcode> and \u003Ccode>zh2._domainkey\u003C\u002Fcode> under the domain, for signing mail sent from it.\nOnly Send and receive asks for them.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Bounces.\u003C\u002Fstrong> One CNAME record at \u003Ccode>bounces\u003C\u002Fcode> under the domain, the address bounces come back to. Only Send and\nreceive asks for it.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>A record that is published stops being listed once it checks.\u003C\u002Fp>\n\u003Ch3 id=\"check-records\">Check records\u003C\u002Fh3>\n\u003Cp>\u003Cstrong>Check records\u003C\u002Fstrong> reads what the domain publishes now and marks each record as it goes: passed, or failed with what it\nfound instead, or \u003Cstrong>No record found\u003C\u002Fstrong>. Ownership holds only while its record is published: a record withdrawn since\nthe last check withdraws what it proved. Asking again proves nothing new until something changes at your domain\ncompany, and DNS changes can take a while to be seen.\u003C\u002Fp>\n\u003Cp>The domain then says where it stands: not verified yet, verified with its mail not moved yet, verified with mail kept\non your mail host, or receiving active on this domain.\u003C\u002Fp>\n\u003Ch3 id=\"what-changes-once-a-domain-is-active\">What changes once a domain is active\u003C\u002Fh3>\n\u003Cp>A domain is active once its ownership and its three MX records check, in either receiving choice:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Mail to an address on it is delivered to the mailbox that holds that address. Mail to an address that nobody holds\nis refused, and its sender is told.\u003C\u002Fli>\n\u003Cli>A member created from then on gets its address on the domain, such as \u003Ccode>jules@example.com\u003C\u002Fcode>. Members who already\nexist keep their address, and an owner can change it to the domain on the member's page.\u003C\u002Fli>\n\u003Cli>Addresses on the domain can be given as soon as its ownership checks, before its MX records move, so every address\ncan be ready before the first mail arrives.\u003C\u002Fli>\n\u003Cli>A receive-only domain never sends. A send from one of its addresses is refused before anything leaves.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2 id=\"moving-a-domains-mail-to-zero-human\">Moving a domain's mail to Zero Human\u003C\u002Fh2>\n\u003Cp>This guide moves a domain that already receives mail somewhere else, say \u003Ccode>example.com\u003C\u002Fcode> for Northstar, without losing\nany. It moves receiving: the domain is attached receive-only, every address is made ready, and only then do the MX\nrecords change. Do each step in order, and run its check before the next.\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cstrong>Attach the domain.\u003C\u002Fstrong> On \u003Cstrong>Domains\u003C\u002Fstrong>, type \u003Ccode>example.com\u003C\u002Fcode>, choose \u003Cstrong>Receive email at example.com\u003C\u002Fstrong> and press\n\u003Cstrong>Attach\u003C\u002Fstrong>. Check: the domain appears under \u003Cstrong>Attached domains\u003C\u002Fstrong> as not verified, with the ownership record and\nthree MX records to add. Nothing about its mail has changed yet.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Prove you own it.\u003C\u002Fstrong> Add only the ownership TXT record at your domain company, then press \u003Cstrong>Check records\u003C\u002Fstrong>.\nCheck: the ownership row passes and the domain says it is verified and its email has not moved yet. Leave the MX\nrecords alone for now.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>List every address in use.\u003C\u002Fstrong> Write down every address at the domain that receives mail today: each person's,\neach shared address such as \u003Ccode>support@example.com\u003C\u002Fcode>, and any catch-all. Check: compare your list with the mail\nprovider you are leaving, so no address is missed.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Give every address a mailbox.\u003C\u002Fstrong> Give each person their address on \u003Cstrong>People\u003C\u002Fstrong>, and add each shared address as an\nextra address on the member or person who should receive it, with \u003Cstrong>Reply from this address\u003C\u002Fstrong> as you want it. Check:\neach address shows on People or on the member's page. An address left out is refused once mail moves.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Shorten the wait for DNS.\u003C\u002Fstrong> If your domain company lets you, lower the time to live of the domain's MX records\nand wait for the old value to pass. Check: your domain company shows the new time to live. It makes the move, and\na rollback, take effect sooner.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Publish the three MX records.\u003C\u002Fstrong> Add them exactly as the domain lists them, at 10, 20 and 30. Keep your old\nprovider's MX records for now, at higher numbers than 30, so they are only a fallback. Press \u003Cstrong>Check records\u003C\u002Fstrong>.\nCheck: all three MX rows pass and the domain says receiving is active on this domain.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Watch mail arrive.\u003C\u002Fstrong> From a mailbox outside the company, send a message to two of the addresses you prepared.\nCheck: each arrives in the mailbox you gave it, on the member's \u003Cstrong>Inbox\u003C\u002Fstrong> or the person's own \u003Cstrong>Inbox\u003C\u002Fstrong>.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Remove the old MX records.\u003C\u002Fstrong> Once mail is arriving, delete your old provider's MX records. Check: press \u003Cstrong>Check\nrecords\u003C\u002Fstrong> again, and send one more message from outside to verify it still arrives. Keep the old provider's account\nuntil the old records' time to live has long passed, so any mail still in flight is not lost.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch3 id=\"how-to-roll-back\">How to roll back\u003C\u002Fh3>\n\u003Cp>Changing DNS does not clear what other mail servers have already looked up, so a rollback takes effect as their cached\nanswers expire, as the move did:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Put the old MX records back\u003C\u002Fstrong> at your domain company, and remove the three Zero Human ones. Mail goes back to your\nold provider as caches expire.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Then switch or detach.\u003C\u002Fstrong> Once the old records are back, \u003Cstrong>Keep email on\u003C\u002Fstrong> your mail host stops the domain\nreceiving in Zero Human, and \u003Cstrong>Detach\u003C\u002Fstrong> removes it altogether. Do this after DNS, not before: while the MX records\nstill point at Zero Human, mail to a domain that is no longer active is refused.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>What already arrived stays.\u003C\u002Fstrong> Mail delivered to Zero Human during the move stays in its mailboxes for your plan's\nperiod (\u003Ca href=\"\u002Fdocs\u002Femail\u002Fretention-and-deletion\">Retention and deletion\u003C\u002Fa>).\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cdiv class=\"prose__planned\">\n\u003Cp class=\"prose__flag\">Planned\u003C\u002Fp>\n\u003Ch2 id=\"sending-from-your-domain\">Sending from your domain\u003C\u002Fh2>\n\u003Cp>With \u003Cstrong>Send and receive email\u003C\u002Fstrong>, members and people will send and reply from the domain's addresses once its DKIM and\nbounce records check: their mail signed with the domain's own DKIM keys, and bounces coming back to its bounce\naddress. The move guide above will then end with a last step, publishing those records and checking them, after\nmail is already arriving.\u003C\u002Fp>\n\u003C\u002Fdiv>\n\u003Ch2 id=\"detaching-a-domain\">Detaching a domain\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>Detach\u003C\u002Fstrong> on a domain asks you to confirm, then removes it: mail routing and who may send from it go back to how they\nwere before it was attached, and its records no longer prove anything. Attaching it again starts from a new ownership\nrecord.\u003C\u002Fp>\n\u003Ch2 id=\"over-the-api\">Over the API\u003C\u002Fh2>\n\u003Cp>Reading the list is \u003Ccode>GET \u002Fv1\u002Fenterprise\u002Fdomains\u003C\u002Fcode>, open to a token whose scopes cover \u003Ccode>enterprise\u003C\u002Fcode>. The rest is for a\nsigned-in owner only: \u003Ccode>POST \u002Fv1\u002Fenterprise\u002Fdomains\u003C\u002Fcode> with \u003Ccode>{ &quot;domain&quot;, &quot;mailMode&quot; }\u003C\u002Fcode> attaches one (\u003Ccode>mailMode\u003C\u002Fcode> is\n\u003Ccode>receive\u003C\u002Fcode>, \u003Ccode>migrate\u003C\u002Fcode> for send and receive, or \u003Ccode>keep\u003C\u002Fcode>), \u003Ccode>POST \u002Fv1\u002Fenterprise\u002Fdomains\u002F{domain}\u002Fverify\u003C\u002Fcode> checks its\nrecords and answers what each one found, \u003Ccode>PATCH \u002Fv1\u002Fenterprise\u002Fdomains\u002F{domain}\u003C\u002Fcode> with \u003Ccode>{ &quot;mailMode&quot; }\u003C\u002Fcode> changes the\nchoice, and \u003Ccode>DELETE\u003C\u002Fcode> on the same path detaches it. A domain another enterprise holds is refused with\n\u003Ccode>domain_already_claimed\u003C\u002Fcode>, a name under \u003Ccode>zerohuman.com\u003C\u002Fcode> with \u003Ccode>domain_reserved\u003C\u002Fcode>, and a name that is not a domain with\n\u003Ccode>invalid_domain\u003C\u002Fcode>.\u003C\u002Fp>\n",[12,16,19,22,26,29,32,35,38,41,45,48],{"id":13,"text":14,"level":15,"planned":8},"the-enterprises-own-mail-host","The enterprise's own mail host",2,{"id":17,"text":18,"level":15,"planned":8},"extra-addresses","Extra addresses",{"id":20,"text":21,"level":15,"planned":8},"attaching-a-domain-you-own","Attaching a domain you own",{"id":23,"text":24,"level":25,"planned":8},"three-choices-for-its-mail","Three choices for its mail",3,{"id":27,"text":28,"level":25,"planned":8},"the-records","The records",{"id":30,"text":31,"level":25,"planned":8},"check-records","Check records",{"id":33,"text":34,"level":25,"planned":8},"what-changes-once-a-domain-is-active","What changes once a domain is active",{"id":36,"text":37,"level":15,"planned":8},"moving-a-domains-mail-to-zero-human","Moving a domain's mail to Zero Human",{"id":39,"text":40,"level":25,"planned":8},"how-to-roll-back","How to roll back",{"id":42,"text":43,"level":15,"planned":44},"sending-from-your-domain","Sending from your domain",true,{"id":46,"text":47,"level":15,"planned":8},"detaching-a-domain","Detaching a domain",{"id":49,"text":50,"level":15,"planned":8},"over-the-api","Over the API",1794928142867]