Software you install — not a service you sign up for
Skim all your inboxes.
On a server you run.
SkimMail puts every mailbox you have — Gmail, Outlook, and anything that speaks IMAP — into one keyboard-driven reading list, on hardware you control. It ships as a single Go binary with its web interface built in. It reads your mail. It never sends any.
- Current release 1.18.0
- One binary, SQLite built in
- No telemetry, no analytics, no crash reports
- Business Source License 1.1
What SkimMail does
Mail spread across a personal Gmail, a work Outlook and a couple of mailboxes on your own domain means checking several apps, several times a day, and still missing things. SkimMail connects to each mailbox independently and presents one inbox, with a local cache so reading stays fast whether or not every provider supports the same protocol extensions.
It reads. It does not send.
There is no compose window and no SMTP connection anywhere in SkimMail — it cannot send mail, not even a test message to itself. Adding an account opens a connection and lists the mailboxes, and that is the whole test. Archive, delete and move act on the mailbox over IMAP; delete moves the message to that account's Trash folder, and SkimMail never permanently deletes a message.
Every mailbox in one list
Any IMAP server, plus Gmail and Outlook by signing in with Google or Microsoft. Sort accounts into named groups and read a group on its own. New mail arrives in real time over IMAP IDLE, with a poll fallback when IDLE drops.
Built for getting through it
Keyboard shortcuts throughout, a focus mode, a command palette, split-inbox bundles, snooze, pin, starred across every account, multi-select bulk actions, undo on archive, delete and move, and one-click unsubscribe on senders that offer it.
Search that stays on the machine
A local index of every subject and sender address answers instantly and never leaves your server. Message bodies are deliberately not indexed. A second tier can ask one mail server directly, to reach mail older than your sync window.
Remote content stays blocked
Nothing in a message loads until you ask for it. When you do, the server fetches the image through that account's own network route and serves it locally — your browser never contacts the sender's host, so a tracking pixel learns nothing about you.
A separate way out per account
Each account can leave through its own SOCKS5 proxy, HTTP proxy, embedded WireGuard tunnel or a relay you deploy. Every connection reports the public IP it actually left from, and warns you when two that are meant to be separate arrive from the same address.
Rules, alerts and notifications
Match on sender, subject, account, group — or "looks like a one-time code" — then tag it, toast it, push it, or send it to a webhook, Telegram, Slack, Discord, Teams or Google Chat. An account that keeps failing stops on its own and tells you.
And the parts you only notice once you are operating it
Credentials, OAuth tokens, two-factor secrets and proxy URLs are encrypted at rest with AES-256-GCM, under a master key that never leaves the instance. Multi-user instances give each person their own accounts and mail, invisible to everyone else, as owner, operator or viewer. Backups are encrypted snapshots that restore onto any SkimMail server, even one on a different database. The mail cache can live on the local filesystem or any S3-compatible bucket, with a size ceiling, a retention period and a manual purge. SQLite is the default database; PostgreSQL and MySQL are compiled into the same build, MySQL still experimentally. Everything above is documented page by page in the wiki.
Run it
The only requirement is somewhere to run a container — SQLite is built in, and there is no external service to stand up first.
docker run -d --name skimmail -p 8080:8080 \
-v skimmail-data:/data -e AUTH_MODE=passphrase \
ghcr.io/lyquyduong/skimmail:latest
Then open http://localhost:8080. Before it will let anyone
create anything, SkimMail asks for a one-time claim code
it printed at first boot — which is what stops whoever reaches the port
first from claiming your instance:
docker logs skimmail 2>&1 | grep 'claim code'
There is also a Docker Compose file, an apt repository for Ubuntu and Debian that installs it as a systemd service, and signed binaries for Linux and macOS on amd64 and arm64. The full install matrix, the configuration reference and the upgrade notes live in the wiki ▸ Installation; releases and checksums are on GitHub.
Then add a mailbox: host, port 993, TLS, and an app password
— or sign in with Google or Microsoft, which is covered below.
There is no SkimMail service
This is the part most easily misread, so it comes before the details: SkimMail is software you install, not a service anyone signs up for. There is no SkimMail account, no SkimMail server holding your mail, and no hosted version operated by its publisher. LyQuyDuong publishes a program and runs nothing.
You — or whoever administers the machine you use — download a binary or a container image, run it, and connect your own mailboxes to it. Everything the software reads goes into the database and files you configured, on infrastructure you control. It sends no telemetry, no analytics and no crash reports, and there is no code path that sends your accounts, messages or settings to LyQuyDuong.
Your instance does make outbound connections, and every one of them is either something you switched on or a download of a public file. It syncs your mail servers; it refreshes an OAuth sign-in with Google or Microsoft if you configured one; it fetches a remote image or follows an unsubscribe link when you ask it to; it posts to a notification channel, a backup destination or an AI provider if you set one up; it checks GitHub for a new release, and pulls the signed plugin index and the signed licence-revocation list on the same schedule, all three only once you turn the update check on; it downloads a plugin from its vendor if you install one; and it asks an IP-echo service which address an egress leaves from, only when someone presses that button. The privacy policy lists all of them, in full and in one place, because a claim like this one is worth little if it cannot be checked.
The consequence for data protection is spelled out on the privacy policy: the operator of each installation is the data controller for the mail inside it, and the publisher of SkimMail is neither controller nor processor for any of it, because none of it is ever received.
Connecting a Gmail or Outlook mailbox
A mailbox is connected with one of two credentials: an app password — a second password issued by the provider, for IMAP only — or signing in with Google or Microsoft over OAuth 2.0.
SkimMail ships no OAuth client of its own
If you choose the OAuth route, you register your own
application with Google or Microsoft and paste its client ID
and secret into your instance. There is no shared SkimMail client ID,
and that is deliberate rather than unfinished:
https://mail.google.com/ is a restricted scope tied to
whoever owns the application that requested it, and a client secret
published in a source repository would be revoked once and break every
installation at the same moment. Thunderbird, Roundcube and Nextcloud
Mail take the same bring-your-own approach.
So each installation's consent screen, its authorised domains and its verification status belong to that installation's operator. The sign-in exchange runs directly between that operator's server and Google or Microsoft, and later token refreshes run the same way. No token, code or message ever passes through anything the publisher of SkimMail runs, because no such server exists.
For Gmail, OAuth is usually not the shortest path
An app password takes two clicks, needs no Google Cloud project, and is revoked on its own from the Google account's security settings. OAuth earns its setup cost when a Workspace administrator has disabled app passwords, or when you would rather not store a password that opens the whole account. For personal Outlook.com, Hotmail and Live.com addresses there is nothing to weigh: Microsoft issues no app passwords for them and has switched basic authentication off, so OAuth is the only way in. Which to pick, in detail: wiki ▸ Gmail or Outlook sign-in.
What has actually been watched working
The project states this precisely rather than in marketing terms, because "supported" and "watched working" are different claims and only one of them is evidence.
| Provider | Status |
|---|---|
| Gmail | Verified end to end on 2026-09-17 with a real Google Cloud client and a real mailbox: folders listed, messages synced, and a token renewal since. |
| Outlook — personal account | Connected for the first time on 2026-09-18: a real app registration, thirteen folders listed, mail synced, and the first token renewal observed to come through cleanly. That renewal matters, because Microsoft replaces the stored sign-in each time. Nothing beyond the first few hours has been watched. |
| Microsoft 365 work or school account | Untested. It is a different registration, under an administrator who can block the application outright. This path is documentation, not experience. |
| Any other IMAP server | Connected with whatever credential that server issues. SkimMail's OAuth support covers Google and Microsoft only. |
If you connect a Microsoft mailbox, please say what happened either way — skimmail@base101.app.
Why the Google sign-in asks for full mailbox access
If you arrived here from a consent screen
This is the home page of the application asking to read your mailbox: SkimMail, published by LyQuyDuong — a self-hosted email reader. It is running on a server operated by whoever set that copy up, and not on any server of ours, because we run none. What it does with the access it is granted is set out below and in full on the privacy policy.
When an operator connects a Gmail mailbox, the consent screen asks to
"Read, compose, send and permanently delete all your email from Gmail".
That is the wording Google attaches to the scope
https://mail.google.com/, and it is far broader than what
SkimMail does with it. The reason it is requested anyway is mechanical:
-
SkimMail's sync engine speaks IMAP. It authenticates to
imap.gmail.comover XOAUTH2, the same as any IMAP client. -
Google grants IMAP access only through that one scope.
https://mail.google.com/is what Google documents for IMAP, POP and SMTP. The narrower-sounding alternatives grant the Gmail REST API instead: a token issued forgmail.modifyis a perfectly valid token thatimap.gmail.comsimply refuses. - So there is no narrower scope to ask for. Requesting one does not reduce what is granted; it stops the mailbox syncing at all. The breadth of the grant is Google's classification of what IMAP access implies. It is not a description of what SkimMail does.
Everything the Google sign-in requests
| Scope | What it is used for |
|---|---|
https://mail.google.com/ |
Connecting to imap.gmail.com over IMAP to list folders, fetch headers and message bodies, and carry out the actions you take in the interface: read and unread, starred, archive, and moving a message between folders. "Delete" moves the message to the account's Trash. It never sends mail. |
userinfo.email |
Reading the address of the mailbox that was just authorised, so the account can be labelled correctly and a later reconnection matches the existing account instead of creating a duplicate. |
openid |
Standard OpenID Connect sign-in, used alongside the address above. |
Microsoft's equivalent is
https://outlook.office.com/IMAP.AccessAsUser.All — an Outlook
resource scope rather than a Microsoft Graph one, because one token
carries one audience — together with offline_access, which is
what makes the sign-in able to renew itself.
What it never does with that access
- It never sends mail. No compose window, no SMTP.
- It never permanently deletes a message. Delete means move to Trash.
- It never transfers your mail to LyQuyDuong — there is no code path that could, and no server to receive it.
- It is never used for advertising, ad targeting or profiling, and it is never sold.
- It never trains a model belonging to LyQuyDuong, for the same reason it never arrives here.
SkimMail's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. The full statement, scope by scope, is section 2 of the privacy policy.
If you are the operator registering the application, note that Google will ask your project for a home page, a privacy policy and a terms of service on a domain you control and verify. These pages describe the software so you can write yours with accurate facts in them; adapt them rather than copying them. The step-by-step is in the wiki ▸ Register the OAuth application.
The optional AI features, stated rather than buried
SkimMail contains optional AI features — summarise a message or a thread, classify, translate, extract action items, build a digest — and they send message content to an inference service you choose and configure. They are implemented and present in every release, including this one, and the buttons for them are hidden in the current interface.
Nothing is sent anywhere until you configure a provider. With no provider and API key set, every one of those endpoints returns an error and no message content leaves your server; a default installation sends nothing at all. Anthropic, OpenAI and Google Gemini are supported, and so is Ollama, which runs on your own hardware and sends nothing to anyone. LyQuyDuong chooses none of them, has no relationship with any of them, and receives nothing either way.
There is one path that runs without anyone pressing a button — background classification of newly arrived mail — and it sits behind two separate switches, both off by default. All of it, including what an earlier version of the privacy policy got wrong about it, is set out in section 6 of the privacy policy. It is here on the front page rather than only there because a feature that sends your mail somewhere should not be something you discover on page six.
Licence, tiers and contact
SkimMail's source is published under the Business Source License 1.1. It is not an Open Source licence today: you may copy, modify and run it, including inside a commercial organisation, but you may not offer it to third parties as a hosted or embedded service that competes with it. On 2030-07-23 the same code becomes available under the GNU Affero General Public License v3.0 or later. The full text and the terms of service are both worth reading before you deploy it somewhere that matters.
Community Edition is free and needs no licence key — ten mailboxes, three network connections and two account groups. Sponsor and Pro keys raise those limits and are verified entirely offline: the software never contacts a licence server, and a key expiring or being revoked never removes anything you already added. It only stops you adding more.
Questions, security reports and commercial enquiries: skimmail@base101.app.