Skip to content
kumo

Email In

Each project’s backlog, and any folder of its wiki, can have its own email address. Forward or send a mail there and it becomes:

  • a task: the subject is its title, the text its description, and the attachments its media;
  • a wiki page: the subject is its title and the text its body. The attachments are saved beside it, with pictures shown on the page and other files linked.

Each address is secret. Anyone who has it can send to it, as with Jira or Trello.

  • A member’s mail is filed at once, as them. This happens only when the receiving mail server confirms the sender (DMARC passes for their domain) and their address is the one they sign in to kumo with.
  • Anyone else’s mail waits in Settings → Email in until someone accepts it or dismisses it.
  • Accepted mail is filed as the person who accepts it. The task or page names the sender and their address’s domain. Nobody is shown the sender’s full address.
  • A leaked address can be replaced: press New address and the old one stops working at once.
  • Mail from machines is never filed: auto-replies, bounces, mailing lists and bulk mail.

Whoever manages the studio’s integrations chooses how mail arrives, in Settings → Email in.

On the studio’s domain, through Cloudflare (free)

Section titled “On the studio’s domain, through Cloudflare (free)”

Use this if the studio’s domain is on Cloudflare. A domain used only for this works best, such as in.studio.games.

  1. In Integrations, connect Cloudflare with a token that has these permissions, all Edit:

    • Zone Settings
    • Email Routing Rules
    • Workers Scripts
    • Workers KV Storage

    Also give your account ID.

  2. In Settings → Email in, choose The studio’s domain, through Cloudflare, enter the domain, and press Set up with Cloudflare.

  3. If the domain is a subdomain that Email Routing doesn’t have yet, add it in Cloudflare first, under Email Routing → Settings → Subdomains. Then press Set up again.

What setup does:

  • Turns on Email Routing for the domain.
  • Deploys a small Worker for the studio. It posts each mail to the studio’s server, signed with a key only the two of them hold.
  • Routes each address to the Worker. No catch-all rule is used, so nothing else of the domain’s mail changes.
  • Keeps up with your addresses. When an address is made, renewed or removed, its route follows within seconds.
  • Holds mail while the server is down. If the studio’s server can’t be reached, the Worker keeps the mail and retries every minute for up to seven days.

In a mailbox the studio already has (IMAP)

Section titled “In a mailbox the studio already has (IMAP)”

Use this with Gmail, Outlook, Fastmail or the studio’s own mail server.

  1. Turn on IMAP in the mailbox’s settings. Make an app password for kumo: Gmail and Outlook need one when two-step sign-in is on.
  2. In Integrations, connect IMAP mailbox for the whole studio. Give the server (imaps://imap.gmail.com, or imap://host:143 for STARTTLS), the mailbox’s address and the app password.
  3. In Settings → Email in, choose A mailbox the studio has, and enter the mailbox’s address.

A place’s address is then the mailbox’s own address with + and a token, for example bugs+k3j…@gmail.com. Gmail, Outlook and most mail servers deliver these plus addresses.

The studio’s server reads the mailbox every minute and never changes it: it doesn’t delete, move or mark any message as read. A mailbox used only for kumo keeps things tidy.

Open Settings → Email in, with the project on screen:

  • Mail to the backlog: press Make an address, then Copy.
  • Mail to the wiki: pick one of the wiki stores you can read, enter a folder (Inbox by default), and press Make an address for this folder.

A backlog’s address can be made by anyone who sets the project up. A wiki folder’s address can be made by anyone who may change the wiki’s settings and write to that store.

  • A message can be at most 25 MiB, which is Cloudflare’s own limit.
  • Attachments over 20 MiB are left out and named in the text.
  • An address takes at most 30 mails a minute, and a sender at most 10. Cloudflare and the mailbox keep anything beyond that for later.