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.
Spam on the way in
Mail that reaches Zero Human through its own receiving servers, as the mail of an attached domain does, is scored for spam before it is stored (Addresses and domains):
- A message scored as spam is stored, and marked Spam in the mailbox's list and when it is open, with its score. A task reads the same score and flag on each message, so a triage task can label or skip it.
- A message scoring 50 or more is refused at the door and never stored. Its sender's server is told.
- Spam headers a sender wrote themselves are removed before scoring, so a message cannot mark itself clean.
- Mail that was not scored shows no mark, and a task reads no score for it.
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 in the mail runs and nothing reaches the portal.
What an unknown recipient gets
Mail to an address that belongs to no mailbox is not kept: no member's, no person's, and no extra address or catch-all covers it. On an attached domain it is refused at the door, so the sender's server tells its sender the mail could not be delivered. Mail to an enterprise that has been closed is not kept either. Give every address that should receive mail a mailbox before its domain's mail moves (Moving a domain's mail).
Outbound controls
Nothing leaves a mailbox unless it is the mailbox's to send:
- Every send from a member waits for approval on the exact message, as it will leave, and a rejected or expired approval sends nothing (Member mailboxes).
- A run sends only from its own member's addresses: the member's own address, or an exact extra address given to it. A catch-all receives but never lets a mailbox send as whatever it caught.
- A person's mail leaves at once, but only from their own address or an extra address of theirs.
- A receive-only domain never sends, and a domain another enterprise has proved it owns cannot be sent from by anyone else.
- Attachments named by link are fetched only over https, and a link that points at an internal address, itself or through a redirect, is refused before anything leaves.
A send that breaks one of these is refused by name, and nothing leaves. See Troubleshooting.
Bounces and complaints
Mail sent from the enterprise's own mail host leaves through Zero Human's own mail provider, which handles bounces and complaints for it. The mailbox records that each mail was handed over and files its sent copy; it shows no later delivery status for it.
Planned
Delivery status for your own domain
Mail sent from an attached domain will carry its delivery status on the sent copy: accepted, delivered, delayed, bounced, failed, or a complaint from its recipient. Bounces will come back to the domain's own bounce address, and an address that bounced or complained will not be sent to again.
Authentication
Receiving servers check where mail came from with SPF, DKIM and DMARC. Mail from the enterprise's own mail host leaves
under Zero Human's own domain authentication: zerohuman.com publishes SPF, DKIM and DMARC records for the mail it
sends, so nothing is yours to publish for it. The mailbox does not show a received message's own SPF, DKIM or DMARC
results.
Planned
Authentication for your own domain
Mail sent from an attached domain will be signed with DKIM keys made for that domain alone, under the two DKIM records the domain lists, with its bounce address under the domain too, so a receiving server sees the mail as your domain's own.