Your addresses

When your server receives mail, you have addresses of your own to send things in from any mail client. Each one only takes mail from your account's own address, so it's no use to anybody else.

  • A board's card and page addresses (card-… and page-…): the board's … menu › Email to this board, on the board or in its wiki. You have them for every board you can edit.
  • A wiki folder's address (page-…): right-click the folder in the wiki tree › Email this folder…
  • Your personal address (add-…): on your Account page, under Email a card in. It reaches any board.

Every address has a Copy button and New address. If one leaks, make a new one: mail to the old address bounces from then on. From the CLI, slipdock inbound <board>, --folder <path> or slipdock inbound me shows the same addresses.

Permitted senders. A board's owner can let other people mail its card address too: Board settings › Features › Permitted senders, one address per line. Their mail still has to pass DMARC or DKIM. It is added as you and says who sent it. It never answers a wait, and the page addresses stay yours alone.

Emailing a card in

Mail to a board's card address is a new card on its ready list, added by you. Forward an invoice, a bug report or a note to yourself:

  • the subject is the title, with Re: and Fwd: taken off;
  • the body is the description, with quoted replies and your signature trimmed;
  • attachments go on the card, and images in the message show where they were.

Your personal address reads the subject the way Quick add does, so it can set the board, list, priority and due date: [Website] Renew the cert due: friday #high. With no board named, the card goes to your Quick add default board.

To add to a card that already exists, start the subject with its number: [#42] Hinge replaced to the board's card address is a comment on card 42, with any attachments on the card, rather than a new card. It works for cards on the board's sub-boards too. Replying to an email about the card does the same.

Emailing a wiki page

Mail to a board's page address is a new wiki page. The subject is its title, the body the page, and attachments are the page's files. Send meeting notes, a write-up or a day's journal.

  • It goes in the Inbox folder, made the first time it's needed.
  • [Design/Decisions] Use Postgres files it in that folder instead, making any folder along the path that's missing.
  • + Journal adds the message to the existing page called Journal, under a heading with today's date and your name, instead of making a new page. It suits a running log.
  • Mail to a folder's address goes in that folder without a [Folder] in the subject. [Sub] Title files it in a folder beneath that one.

Replying to an email

Emails about a card, such as a mention, an automation's email or something waiting on you, can be answered from your mail client. Reply as you would to anyone:

  • what you wrote is a comment on the card, by you, with the quoted history and your signature taken off;
  • attachments go on the card, and @name tells that person;
  • if the card is waiting on you, your reply answers it. Start with a choice's number or text to pick it, and give each question its own paragraph.

Emails about one card thread together in your mail client.

When mail bounces

The bounce says why. The usual reasons:

  • it wasn't sent from your account's address, or couldn't be shown to be;
  • the address has been replaced with a new one;
  • you can no longer edit that board, or it's archived;
  • a + Title names no page on the board (the bounce suggests close titles);
  • a reply had nothing in it once the quoted message was taken off.

Auto-replies and list mail are dropped without a bounce, so two systems can't answer each other forever.

Checking and automating

  • Did it arrive? Account › Email log lists your last 50 messages: what each made, or why it bounced. From the CLI, slipdock inbound log.
  • A link back. Tick Email me back a link to each card my mail makes on the Account page for a short reply with the new card's link.
  • Rules for what mail brings in. The card_emailed and page_emailed triggers let an automation act on it as it arrives, such as flagging every emailed card for review (see Automations).