Release ledger · Vol. I

What changed in the inbox,
and why it matters.

The changelog is the public ledger for Folio. It records product changes, reliability work, and setup guidance in the language an operator can act on: what changed, who it helps, and what to try next.

Latest

5 June 2026

Entries

9

Scope

Product · Reliability · Manual

I · Release notes

No. 009

Prove deliverability before you switch — and a roomier free preview.

Three changes aimed at the moment before you commit: test that mail lands before repointing MX, get setup steps for your actual DNS host, and a free preview big enough to actually trust the result.

  • New

    Send a test before you move MX

    From a domain's setup page you can now send a real, DKIM-signed test letter to an inbox you control — before repointing MX. Sending never touches your incoming mail, so you can confirm a letter lands in the inbox (not spam) with zero risk to your current setup. Test sends use a separate allowance and never count against your preview sends.

  • New

    Guided, registrar-aware DNS setup

    Folio now detects where your domain's DNS is hosted — Cloudflare, GoDaddy, Namecheap, Squarespace, Route 53, and more — and shows the exact click-path to the record editor instead of a generic table. Unrecognized host? You'll still get your nameservers and clear next steps.

  • New

    Export all mail as .mbox

    Security → Export all mail downloads your inbox, archive, sent, and spam as a standard .mbox file that Thunderbird, Apple Mail, mutt, and Google Takeout all read. Paired with Google Takeout import, your mail moves in and out freely — nothing held hostage.

  • Improved

    Free preview raised to 100 sends

    The no-card preview now includes 100 sends (up from 25), so you can live with the product long enough to trust its deliverability before adding a card. Still one domain in preview; the rest of every plan is unchanged.

No. 008

Emcognito WebMail is now Folio — at folioinbox.com.

Same inbox, same team, same product. We've moved off the shared Emcognito address onto a home of our own. Your email, domains, and DNS are untouched; old links redirect automatically.

  • New

    A name and a home of our own

    The product now lives at folioinbox.com. Bookmarks and links to the old wm.emcognito.com address forward to the new one automatically — nothing to update. Your email address, custom domains, and MX/DNS records are unchanged.

  • Improved

    Passkeys: one quick re-enrollment

    A passkey is tied to a site's address, and ours changed — so a passkey set up on the old domain can't sign you in here. Sign in with your email link as usual and you'll be prompted to add a fresh passkey; the Security page flags any old one that needs replacing. Magic-link sign-in always works as a fallback.

No. 007

AgentDraft now reads like a first-party calendar connection.

The Calendar setup panel now presents AgentDraft as a same-studio integration, with explicit token scope, connection status, rotation, and disconnect controls.

  • Improved

    First-party AgentDraft bridge

    The old numbered setup step became a full integration panel with the AgentDraft mark, same-studio badge, agentdraft.io link, clear connection state, and a scoped-token row that tells you exactly where to paste the Webmail / Folio token.

No. 006

Calendar invites read like the actual invite, not a stub.

The agenda card now carries the full briefing — description, named guests with RSVP status, recurrence sentence, and a Join chip that picks the right video provider even when the LOCATION field stacks several URLs.

  • Improved

    Briefing pull-block

    The agenda card now surfaces the invite description as an editorial pull-block under the meta line — collapsed to a single-line excerpt by default, expanded in place when you click Read all. No more bouncing to Google Calendar to figure out what the meeting is.

  • Improved

    Named guests

    Attendees moved from anonymous coloured dots to named chips with partstat-toned pips. First four guests render inline; the rest collapse to a +N more chip with the overflow names available on hover.

  • Fixed

    Join chip provider label

    Invites whose LOCATION jammed two URLs together with a semicolon (a GitHub thread and the Meet link, for example) were labelling the chip with the wrong hostname. The parser now splits stacked URLs before extraction so the chip always names the recognised provider — Google Meet, Zoom, Teams, Webex, Whereby, and the rest of the known set.

No. 005

Invites land in the inbox with a real agenda behind them.

Calendar invites are now first-class objects in the reading view: RSVP without leaving the letter, see conflicts before you accept, and let any calendar app subscribe to the result.

  • New

    Inbox-side agenda

    A new Agenda view groups every invite that has arrived in the inbox into Today / Tomorrow / weekday rails, with per-identity filtering so a portfolio operator can see one brand's week at a time.

  • New

    RSVP, with conflict warning

    Inbound invites get accept, decline, and propose-new-time controls inline. Accepting an event that overlaps another accepted event surfaces the conflict in a confirm step before the reply goes out.

  • New

    Recurring events from RRULE

    Recurring invites expand by RFC 5545 RRULE, so a weekly standup shows up on every occurrence rather than only the series start.

  • New

    Subscribe-out iCal feed

    Each account can mint a private iCal feed URL that exposes its accepted agenda to Apple Calendar, Google Calendar, or any CalDAV-aware reader — read-only and revocable.

  • Improved

    Time zones and clipping

    Invite times now honour the original TZID on the inbound message instead of being silently rewritten to the server zone, and declined or canceled events drop off the agenda automatically.

  • Improved

    Public Domain Health tool

    The free /tools/domain-health checker now detects DKIM at common provider selectors (Google, Microsoft 365, Mailchimp, SendGrid, Amazon SES, others) instead of penalising a domain whose selector lives outside the usual default.

No. 004

Android availability is now part of the public product story.

The homepage now treats the Android app as proof that the same multi-domain inbox works on the phone operators already use.

  • New

    Android app link on the homepage

    The landing page now links to the Folio Android app on Google Play while keeping web signup as the primary action.

  • Improved

    Mobile release panel

    A new mobile section explains that Android is live, iPhone is coming next, and the same account, identities, passkey sign-in, and auto-From behavior carry across devices.

  • Improved

    App-aware structured data

    Homepage SoftwareApplication metadata now reflects Web and Android availability and points crawlers to the Google Play listing.

No. 003

Clearer setup, safer billing, better sending identity control.

Today's work focused on reducing setup uncertainty and making account state changes more dependable behind the scenes.

  • New

    Native From selector in compose

    Compose now exposes a first-class From dropdown so multi-domain operators can choose the exact sending identity before a letter leaves the desk.

  • Improved

    Expected-vs-found DNS checks

    Domain setup now shows clearer DNS verification differences, making it easier to spot a copied value, stale record, or registrar formatting issue.

  • Fixed

    Tighter DKIM and DMARC verification

    Verification now handles DKIM and DMARC edge cases more carefully, so a domain is less likely to sit in an unclear partially verified state.

  • Reliability

    More resilient subscription handling

    Stripe subscription webhooks now handle duplicate and thin events more defensively, keeping billing status aligned when providers retry or send compact payloads.

  • Improved

    DMARC reporting documentation

    The Manual now explains DMARC aggregate reporting authorization so operators understand why the wizard asks for the records it does.

No. 002

No-card preview and a cleaner Workspace migration path.

This release made the first trial safer and gave Google Workspace switchers a concrete DNS plan before they move mail.

  • New

    No-card preview

    New accounts can start with one domain and 25 sends before adding a card. The card-required trial begins only when the operator chooses to lift those caps.

  • New

    Google Workspace migration wizard

    A public cutover guide now walks Workspace users through a no-downtime MX transition, including overlap, verification, and when to cancel the old tenant.

  • Improved

    Preview-cap follow-ups

    Upgrade prompts and account state copy now match the new preview model, removing stale wording from CTAs and billing explanations.

  • Improved

    Push notification groundwork

    Native push notification plumbing and iOS APNs configuration were wired so the mobile app can notify operators about new correspondence.

No. 001

Public pages received a conversion and clarity pass.

The earliest changelog entry covers the visible product-market surfaces: how the site explains the product, handles capture, and routes readers.

  • Improved

    Landing-page QA fixes

    Tap targets, analytics consent placement, and public-page wiring were tightened so prospects can evaluate and start without small layout snags.

  • Improved

    Newsletter capture polish

    The newsletter flow now gives a clearer success state and avoids pointing readers at a direct email CTA that was no longer part of the public surface.

  • Improved

    Founder and editorial polish

    The public story gained stronger founder framing and magazine-style details that better match the single-reader, many-identities positioning.

II · How to read this page

Not every commit belongs in the ledger.

User-facing changes are written here when they alter setup, sending, billing, deliverability, or the public manual. Internal infrastructure work appears only when it changes the reliability or safety a customer would actually feel.

The success metric is simple: fewer support questions that begin with "what changed?" and more operators completing domain setup, first send, and billing upgrades without asking for context.

Read the manualStart free

Sources