
MailCode
Email Client for EWS,IMAP - macOS, Windows
What is new , improved and fixed in new Version.
NEW — Summary: what today brought, and what it wants from you
A new view, and the counterpart of Analytics: how much arrived today and how that compares with your own last seven days, who sent it, which conversations moved — and then the mail itself sorted by what it wants from you: needs a reply, waiting on them, invitations, for information, automated. Beside it, your flags, the mail waiting to go out, and today's meetings. Almost all of that sorting is read off the mail on your own Mac; the part that is not stays off unless you supply your own AI key.
NEW — Name the file in the sentence that talks about it
A letter carrying nine attachments leaves the reader to work out which is which. Type § in the composer — or drag a file's chip into the text — and the file's own name goes into the sentence, with a numbered Attachments list at the foot of the letter if you want one. Take the file off the letter and the reference that named it turns red, heals itself if you attach it again, and asks once before the mail goes out pointing at something it is not carrying.
NEW — A line of the message under every row
The ≡ chip in the list toolbar puts one or two lines of each message under its row, in every grouping. Settings ▸ Read adds a Read text colour beside the unread one, so read and unread mail can differ by colour alone.
NEW — Five palettes, where there were two
Dark+ and Light+ changed the ground and nothing else. Settings ▸ Appearance now offers Syntax Dark and Syntax Light, which are what those two were; Quiet Dark and Quiet Light, which draw a message list in one ramp of grey and leave colour to the things that use it to mean something; and Paper, the palette from the website.
IMPROVED — The Flags timeline reads like a timeline
Every bar carries its own date beside it — "due 8 Sep", "done 2 Sep (2d early)", "due 4 Sep · 3d over" in red — instead of leaving you to count it off the ticks along the top. The work done now sits inside the plan it belongs to, so an overrun visibly pokes out of it.
IMPROVED — A sample inbox with a conversation worth the name
Open MailCode without adding an account and it starts in Demo mode, on a sample inbox that never touches the network. It now holds conversations of seventeen and sixteen messages, each forking three times, so the reply arcs, the fork marks and the conversation timeline have a real shape to draw before you have connected a mailbox of your own.
FIXED — Removing a mailbox removes all of it, and the disk space comes back
Mail you had deleted was kept so it could be brought back, and that copy — the message and the full bytes of every attachment on it — outlived the mailbox it belonged to: on one archive 2.06 GB, filed under an account that no longer existed and shown nowhere. Removing a mailbox now takes its Recently Deleted mail with it, hands the space back to the disk as it goes, and says how much it freed.
FIXED — Read and unread keep up with Office 365
Mail marked read in MailCode could stay unread in Outlook on the web for minutes or for good, and mail read there took just as long to catch up here. A busy mailbox's refusals no longer spend the few attempts a flip is given, reading through a run of mail travels as one instruction instead of one per message, and MailCode now polls IMAP accounts for flag changes every twelve seconds.
FIXED — Open an attachment from a message you opened as a file
The window a .eml or .msg opens into now offers View, Open and Download like the reading pane, instead of a single Open that ran the preview — and Open no longer removes the file it just handed to the application. Translation reaches that window too.
FIXED — A reply arc across a long conversation looks like one
The arc from a message to the one it answers was drawn to the same narrow width however far apart the two rows sat, so across a long thread it came out as a vertical line with a bend in it. The bow now widens with the distance it crosses.
I kept hitting the same wall: ten years of mail, an Exchange server with a quota, and a stack of PST files nothing on my Mac would open. The usual advice is to delete things. I wanted the opposite keep all of it, on my own disk, and find any of it.
So I built MailCode.
Mail lives on your disk, not in someone's cloud. Exchange, Microsoft 365 and IMAP in one window, every message archived locally. No service of mine in the middle. When the server quota fills up you move messages onto local or external storage, and it fetches the attachment bytes before anything is removed from the server.
It opens the archives nothing else will. PST and OST, .eml, .msg, maildir folder tree intact, everything indexed on the way in.
Search is a query language, not a box.f: s: b: to: cc: in: df:/dt: label: flag:, combined with AND or OR. Ask "find phone number of Alice Chen" in plain words and it reads the answer out of the mail it found — local pattern work, no model involved.
A message is usually a task. Seven flags, six of them mapped onto an Important/Urgent matrix. Due dates, reminders, notes that stand on their own, and the whole set readable as a Gantt style timeline. None of it moves a message.
Numbers from my own archive rather than a demo one: 280,901 messages, 31 GB,1,208,950 attachments. Median search 5 ms warm.
On the Mac App Store now, macOS 12+, Apple silicon. Free 14-day trial, then a one-time purchase, no subscription. Windows is built and waiting on installer code signing.
Two things I'd like input on:
1. The category is crowded and mostly subscription. Is "one-time purchase, your mail stays on your disk" a real wedge, or am I just the cheap option?
2. The people who need this have enormous Exchange mailboxes, sysadmins, lawyers, consultants. Beyond the App Store listing, where would you look?
Electron, better-sqlite3, FTS5, and a lot of fighting with EWS. Happy to go into any of it.
1 Like
Comment
Every app in my category now has an AI subscription attached. I built the same features compose, summarise, refine, translate and then took the resale out.
On the Mac App Store build there is no server of mine in the path. You paste in your own OpenAI or Anthropic key and the app talks to the provider directly. I don't meter it, mark it up, or see the text.
The reason is that the pitch of the whole product is that your mail stays on your disk and nothing routes through a machine I run. A relay would have made that false in the one place the content is most sensitive the body of themessage. I'd have needed a paragraph in the privacy policy explaining the exception, and that paragraph is the product arguing with itself.
What I keep hearing is that this leaves money on the table usage-based AI is where the margin is. Maybe. But the buyers I have are the ones with a compliance officer, and "no third party in the path" closes them faster than a feature does.
The part I'm actually proud of isn't AI at all. Translating an attachment properly means translating the file, not the preview. The viewer already renders .docx through mammoth and .xlsx through SheetJS, and translating that HTML would have been an afternoon's work — but then the download would be a different document: no styles, no headers, no page setup. So it rewrites the file. A .docx is XML in a zip; the entries it doesn't touch get copied across still compressed, and the two or three it does rewrite go through the platform's own CompressionStream. No zip library, works offline, works inside the App Store sandbox. Preview and download are the same bytes, and "Show Original" is a re-render of the untouched ones. PDFs keep their page and wear the translation over it; scanned ones go through macOS's own OCR.
Has anyone else taken the resale out and regretted it? If you're charging for AI on top of a one-time purchase, is it actually converting?
About
MailCode exists to make email faster, smarter, and more productive—especially where traditional email clients fall short in search, accuracy, writing flexibility, and workflow tool


1 Comment
The Summary view sounds like the biggest workflow change. Have users actually processed their inboxes faster with it, or is proving a measurable improvement over their existing mail client still the main unknown?