Scheduled email reminders that actually arrive.
Write an email once — attach files, images or archives — and Aevistle sends it on time, even with the window closed. Once, every weekday at 09:00, on the 1st of the month, or on any cron expression you like. It knows your public holidays, so the Monday report does not go out on a Monday nobody is working. Windows and Android, no account, no server, no telemetry. Two devices stay in step over your own network — no cloud in the middle.
The weekly report every Friday. The invoice on the 1st. The birthday message at midnight while you are asleep.
Every mail client can send an email. Almost none of them can promise you it will go out at 07:00 next Tuesday with the right file attached, whether or not you remember, whether or not the app is open.
Aevistle is that promise first. No account to create — it connects to the SMTP server you already have (Gmail, Outlook, QQ, 163, your company's server) and sends. Receiving is there too, but it stays out of the way until you turn it on: point an account at its IMAP server and Aevistle pulls in a unified inbox, lifts out verification codes and login links automatically, and leaves everything else alone by default.
People use it to send a weekly report every Friday at 17:00 · remind a class about homework the night before it is due · mail an invoice on the 1st of every month · post a birthday message at midnight while asleep · deliver a rent reminder every 30 days · schedule a follow-up so a reply lands in the morning rather than at 02:00 · grab a login code the moment it lands without switching apps.
It might not be for you if you want a full-featured mail client — no folder management, no push IDLE sync, no server-side delete, on purpose — a marketing tool with tracking pixels and open rates, or a hosted service that keeps sending while your devices are switched off. Aevistle sends and reads from your machine using your mailbox, which is exactly why it needs no account of its own and collects nothing.
Aevistle has no server. There is no account to create, no telemetry and no crash reporting.
A short, fixed list of things ever leaves your device: the SMTP connection to
your own provider; the IMAP connection to your own provider, for accounts
where you turned receiving on; a remote image in a received message, only
when you ask for that one by name; an update check to api.github.com, if
you leave it on; and one year of public holiday dates, when you press
"check online". The last two are whitelisted by host and exact path and leave
from the trusted process, not from the part of the app that renders mail —
which has no outbound network reach at all.
Pairing two devices adds nothing to that list. They talk to each other on your own network, with no cloud and no relay in the middle.
With updates switched off, every remaining request in that list is one you pressed a button for.
Where each thing is stored, what moving the data folder does, and the two things that deliberately stay behind → docs/PRIVACY.md.
| ⏰ Fires when closed | A tray process on Windows, an exact alarm plus WorkManager on Android. Closing the window does not cancel your reminders. → |
| 🔁 Real recurrence | Once, every N minutes, daily, weekly, monthly, yearly, or a full 5-field cron expression. → |
| 📎 Attachments that survive the wait | Files are snapshotted when you schedule, so moving or renaming the original does not silently break the send. → |
| 🎌 Working calendars | Public holidays, weekends of your own choosing, 调休 make-up days, six country presets and .ics both ways. Each reminder opts in. → |
| 🌐 Delivery windows | A reminder lands inside the recipient's working day, not yours — and it is reported, never held back, when the windows cannot agree. → |
| 📆 The month grid is the schedule | Drag to move, click to open, tinted by how busy the day is — plus recipient chips, a body preview and delivery badges. → |
| 📥 Optional inbox | IMAP, unified across accounts, remote images blocked by default, with verification codes lifted onto a screen of their own. → |
| 🔤 Merge variables | Per-recipient contact fields plus calendar ones like {{nextWorkday}}, resolved at send time, with Cc and Bcc dropped from the copies. → |
| 🔐 Passwords stay put | Encrypted by the OS: DPAPI on Windows, the hardware-backed Keystore on Android. Never in the settings file, never in an export. → |
| 🎨 Seven visual styles | Each with a real light and a real dark form, and one of them WCAG AAA throughout rather than approximately. → |
Thirty-six of these, each with the reasoning behind it → docs/FEATURES.md
The account list and tab strip hold up past a handful of accounts. Every
layout bug here shared one cause: a flex child had its automatic minimum size
zeroed out (min-width: 0 or overflow: hidden) without anything to catch
what that was protecting against, so the bug stayed invisible on the two- or
three-account screen every earlier check ran against and only showed up once
someone had real inbox worth of them.
- The account list no longer turns into unreadable overlapping text. Its row buttons sat bare on the row instead of inside their own container, so on a narrow window the address/host line was squeezed to near-zero width and wrapped one character at a time.
- The account list scrolls again with many accounts. The card holding it
used
overflow: hiddeninside a column flex modal body, which let the modal shrink the card to fit instead of scrolling past it — past a screenful of accounts, the rest were simply clipped and unreachable. - The inbox's account tabs stop smearing together. Past three or four accounts, the tab strip divided its width evenly and crushed every label into the next one instead of falling back to the horizontal scroll it already had.
- Switching "All accounts" and a single account no longer overlaps rows. The windowed list kept the previous account's scroll range for one frame after the item list changed underneath it.
- Settings on a phone no longer offers the same four cards twice. Daily digest, holiday greetings, calendar subscription and pairing already live on Home; Settings dropped its second copy of each on a narrow window. A wide window is unchanged.
Any two devices can pair now, from either end. The phone and tablet apps can show a pairing QR code, not just read one — so phone-to-phone, tablet-to-tablet and tablet-to-phone work without a computer in the room to hold the code. Android answers ongoing sync too, rather than only starting it.
- The QR code and the camera appeared where you were not looking. Tapping "Pair a new device" added a panel after the device list, which on a phone is below the fold — the camera switched on off-screen. All three pairing panels are dialogs now, full screen, each with the close button they never had.
- Tablets were getting the desktop layout. The phone/desktop switch was a 760px query and a tablet is 800px in portrait, so Settings rendered a grid of cards instead of rows that open. Structure now asks "narrow window or touch platform"; the tab bar still goes by width, so a tablet keeps all nine tabs.
- "Publish the working calendar" opened an empty screen on Android. It now
says why a phone cannot hold that listener open, and offers a
.icsexport instead — which also fixes exporting a backup, a reminder transfer file and an encrypted pairing file from a phone, all blocked the same way.
The pairing handshake is not new code: the socket is the only native part, and
core/pairing.ts still holds the one implementation of the key exchange.
Repairs to the phone layout 0.1.15 introduced — no feature changed, and nothing about how mail is scheduled, sent, stored or encrypted was touched.
- Dialogs are the screen, not a card floating on it. A settings section opened with a gutter all round and the tab bar showing through underneath. Content dialogs now go edge to edge, closed with the button in the header; short confirmations deliberately stay cards.
- Screens opened from Home had lost their main button. Hiding a duplicated heading also hid the element carrying each screen's primary control, so Contacts offered no way to add a contact. Only the heading text goes now.
- Settings stopped repeating itself — the sticky subtitle that summarised the rows directly beneath it, and each section naming itself twice.
Measured on the running window rather than reasoned about: the three content
dialogs each report (0, 0, 390, 800) in a 390×800 viewport, the
confirmation 350×254 with symmetric gutters.
- 📲 Android updates itself. The check always worked; downloading and
installing were desktop-only, so the phone could announce a new version and
then offer a link to a web page. It now fetches the APK in-app with a
progress bar, verified against the release's published
SHA256SUMS, and hands it to the system installer — which still asks you to confirm. The file is written to app-private storage, not a shared Downloads folder. - 🏠 A Home tab, and a bottom bar that fits. Nine tabs never fit a 360px
screen; the bar had quietly been a horizontal scroller with four of them
off-screen. It is five now — Compose, Codes, Home, Inbox, Settings — with
schedules, contacts, templates, the working calendar and the send log behind
Home. The desktop sidebar still lists all nine, and
Ctrl+1–Ctrl+9still reach all nine on both. - ⚙️ Settings is a list, not fourteen screens of scrolling. Sixteen sections in one column made reaching Privacy a scroll past every other section. On a phone it is now sixteen rows that open one at a time; the desktop keeps its two-column grid. Explanatory text under toggles stands down on phones — warnings and errors never do.
- 📡 Pairing dials the right network card. It used to publish the first address the OS listed, which on a machine with a VPN, a hypervisor or a container runtime was routinely a virtual adapter no phone can reach — a four-second timeout on the other device and no clue anywhere. Addresses are ranked now, the chosen one is printed beside the QR code, and a multi-homed machine gets a picker.
Also fixed: toggle switches whose knob never moved on older Android WebView builds, and a "launch at login" entry a source checkout could leave pointing at Electron's own placeholder window.
- 🔗 Pair two devices over your LAN, and nothing else. Scan a QR code on the other device: ECDH P-256 + AES-GCM, a one-time token that expires in two minutes, and no cloud and no relay server at any point. Choose what syncs — accounts, schedule, contacts, templates, appearance — and manage paired devices from one screen. Two devices that cannot see each other exchange a PIN-encrypted file instead.
- 📅 The calendar knows about the mail. Recipient chips and mail counts per
day, a density heatmap, body preview without leaving the grid, the
recipient's local time shown while you drag to reschedule, a suggestion
when a send lands on a holiday, bulk actions across a recurring series,
filtering by account or recipient, delivery-status badges, and a local
.icssubscribe address for the working calendar. - 🎨 A new visual style: runecircuit. Chinese-classical ink meets cyberpunk neon, with day and night forms, an atmosphere-intensity dial and a two-axis accent picker. The seventh style, and the first one with weather.
- 🌾 24 solar terms (节气), computed rather than looked up. Meeus's solar position, not a bundled table — so there is no year the coverage stops. It tints the calendar; it never touches a send time.
Written up at length in docs/FEATURES.md; what changed
before this is in the release-notes-0.1.*.md files.
Grab the latest build from Releases.
| Platform | File to pick | Notes |
|---|---|---|
| Windows 10/11 (x64) | Aevistle-<version>-win-x64-setup.exe |
Installer, adds a Start-menu and desktop shortcut |
| Windows 10/11 (x64) | Aevistle-<version>-win-x64-portable.exe |
Single file, no installation, runs from a USB stick |
| Android 7.0+ | Aevistle-<version>.apk |
Phones and tablets. Enable "install unknown apps" for your browser or file manager for this first install; later updates are offered inside the app. |
<version> is whatever the latest release
page is showing — the badge at the top of this page reads it from the same
place. Deliberately not written out here, so this table cannot go stale.
Verifying a download. Every release publishes
SHA256SUMS.txt, a detached signatureSHA256SUMS.txt.asc, and the public key that made it:gpg --import aevistle-public-key.asc gpg --verify SHA256SUMS.txt.asc SHA256SUMS.txt sha256sum -c SHA256SUMS.txtThe checksums alone prove the file arrived intact; the signature proves it came from this project's key. The fingerprint is in SECURITY.md.
Windows SmartScreen will warn about an unrecognised publisher. That is what a release without a paid code-signing certificate looks like; choose More info → Run anyway, or check the SHA-256 from the release page first.
- Add your mailbox. Settings → Add account. Pick your provider and Aevistle fills in the server, port and encryption for you.
- Get an app password. Gmail, Outlook, Yahoo, iCloud, QQ and 163 all refuse your normal login password from a third-party app. The account dialog links straight to the page where you create one.
- Test the connection. One button. It authenticates without sending anything, so you find out now rather than at 03:00.
- Write your reminder, attach what you need, and choose Schedule.
For scheduled sends to fire while the window is closed, leave Keep running in the tray on (Windows), and allow exact alarms and notifications when Android asks.
The threat model, the hardening choices, and how to report a vulnerability are in SECURITY.md.
The short version: the renderer runs with no Node access, context isolation on and a strict CSP; every string bound for a mail header is rejected if it contains a line break (that is how open relays happen); TLS certificates are verified unless you explicitly turn that off per account; a received message's HTML is sanitized in the main process to a strict allowlist before it ever reaches the renderer, and rendered in a sandboxed iframe with no script execution allowed regardless; and the Android alarm receiver is not exported, so no other app can make Aevistle send mail.
You can check all of that yourself with npm run audit:self — 21 checks,
plain-language output, exit code 1 if anything needs attention.
Requirements — Node.js 20+, and for Android: JDK 17+, Android SDK
(platform 36, build-tools 35+). npm run build:android finds a JDK and an SDK
that are installed but not on PATH, so setting JAVA_HOME is optional.
git clone https://github.com/Aevorine/Aevistle.git
cd Aevistle
npm install| Task | Command |
|---|---|
| Run in a browser (no SMTP, everything else live) | npm run dev |
| Type-check | npm run typecheck |
| Security audit (21 checks) | npm run audit:self |
| Everything CI runs (42 checks) | npm run check |
| Run the desktop app | npm start |
| Build Windows installers | npm run dist:win |
| Build the Android APK | npm run build:android |
Release signing for Android reads ~/.aevistle/keystore.properties or the
AEVISTLE_KEYSTORE* environment variables. Without either, the build falls
back to the debug key so you still get an installable APK.
One React + TypeScript interface, two native shells.
src/core/ platform-independent: domain model, recurrence engine,
validation, SMTP provider presets — no DOM, no Node, no Android
src/ the React interface (six locales, seven visual styles, each in
a real light and a real dark form)
↓ PlatformBridge — the single seam between the UI and an operating system
electron/ Windows: nodemailer + imapflow, DPAPI secret storage, tray,
hybrid tick/precise scheduler, HTML sanitization for received mail
android/ Android: JavaMail (send + receive), Keystore, AlarmManager + WorkManager
The recurrence engine deliberately lives in TypeScript only. It precomputes a list of absolute timestamps, and each platform's scheduler just answers "wake me at T" — so every calendar rule (leap years, short months, DST, weekend skipping) exists once, in one language, and is testable without an emulator.
More detail in docs/ARCHITECTURE.md.
Not promises — the things most likely to come next.
- OAuth 2.0 for Gmail and Microsoft 365, so app passwords stop being needed
- A rich-text composer. Inline images already work; the box itself is still plain text with Markdown
- macOS and Linux desktop builds (the code already targets them)
-
docs/FEATURES.mdin the other five languages - iOS
Something missing? Open an issue — feature requests are genuinely welcome.
Pull requests are welcome. See CONTRIBUTING.md for the layout of the codebase and what a good change looks like, and CODE_OF_CONDUCT.md for how people are expected to treat each other here. Adding a seventh language is one file and needs no build tooling — the type system tells you exactly which strings are missing.
Bug reports and feature requests have
templates; every pull
request runs the same npm run check you would run locally.
| English | 简体中文 | Français |
| Español | Русский | العربية |
MIT © Aevistle contributors