Features
A normal mailbox, with the mail encrypted at rest.
xail.me is a normal email client with the standard set of features — folders, search, contacts, attachments, threaded replies — plus mail stored encrypted at rest and decrypted in the browser when you open it.
Inbox and folders
The inbox, sent, drafts, archive, junk, and trash folders are in the sidebar. The last folder you had open stays open when you come back. Per-folder unread counts update as you read.
Foldered inbox
Inbox, Sent, Drafts, Archive, Junk, Trash in the sidebar, with keyboard navigation and per-folder unread counts.
Last folder remembered
The web client remembers which folder you had open and returns you to it the next time you sign in.
Threaded replies
Replies carry the standard SMTP In-Reply-To link back to the parent message and stay grouped in the inbox.
Compose and send
The composer runs in the browser. Drafts autosave locally so a refresh does not lose your typing. A saved signature is appended to outgoing messages and edited from the settings page.
Composer with autosave
In-progress messages are saved to your browser as you type, so a refresh or a network blip does not lose the draft.
Saved signatures
Save a signature once; outgoing messages append it. Edit or clear the signature on the settings page.
Reply and reply-all
Reply keeps the sender; reply-all carries the same recipients as the message you are replying to, with the ones you have blocked filtered out.
Attachments
Attach a file to a message; the recipient downloads it from the message they received. Files share the same at-rest storage shape as the body.
Find and triage
Search runs over the locally-decrypted copy of every message in the current folder, so matches show up as you type and never surface another account's mail. Per-recipient junk and blocklists let you triage mail without affecting anyone else on the same domain.
Subject and body search
The search box matches against the locally-decrypted subject and body of every message in the current folder.
Per-recipient junk
Mark a message as junk and the next message from that sender lands in your junk folder automatically.
Per-recipient blocklist
Block a sender and the next message from that sender is rejected on the server and never reaches your inbox.
Contacts
Save the addresses you write to often. The composer suggests matching contacts as you type the recipient line.
Account and sign-in
Sign-in happens on my.netquirk.com; the same account signs you in to xail.me. Settings cover your signature, an away auto-reply, optional two-factor codes, and the close-account flow.
One sign-in for xail.me
The same my.netquirk.com identity you use for billing signs you in to xail.me.
Two-factor codes
Add a second factor from any standard authenticator app; settings lets you enrol, verify, and disable.
Away auto-reply
Set an away message from settings; new mail received while the away message is on triggers an auto-reply.
Close account
The close-account control in settings deletes the account and its stored mail after a re-entry of the password.
Storage and offline
A storage pill on the settings page shows how much of the quota you have used. A PIN lock hides every page after a configurable idle window, and a single banner reflects the network state and clears on the next successful request.
Storage quota
The settings page shows the current storage use against the quota for your plan.
PIN lock
Set a PIN and the web client re-prompts for it after the idle window you choose.
Connectivity banner
A single banner shows when the client is offline and clears on the next successful request.
Encryption
Every message on the server is stored as opaque ciphertext. Decryption happens in the browser when you open the message; the server never sees the plaintext body, subject, or attachment bytes. The plain-language description of which fields are sealed and which the server sees for routing is in the security model and the encryption pages.
Mail stored encrypted at rest
The body, subject, and attachment bytes on the server are sealed; the server holds the bytes but does not have the key to open them.
Decryption in your browser
Decryption happens in your browser when you open the message; the key never leaves your device.