No message selected
Accounts register themselves when a meerail-agent connects
(see agent/README.md). To add or remove one, edit the
agent's config.toml — the name, colour and footer set here
are local settings and stay put across syncs. The footer is prefilled
into the composer, so it can be edited or removed per message.
Any of the three can instead be pinned in meerail.toml
(label, color, footer under
[[agent.account]]); pinned ones are shown above but not
editable here, since every sync would write the file's value back.
meerail follows your operating system's light or dark setting on its own. Pick Light or Dark to hold it there instead, whatever the system does. Stored in this browser only.
Messages in the list fade from white towards red as they age,
reaching full red once they are this old. Set to 0 to
switch the tint off. Stored in this browser only.
A few seconds after the window goes behind another one or is minimised, meerail stops polling, closes its live connection and stops animating, and says so in a bar at the top. Bringing it back to the front reloads what is on screen. Turned off, it keeps everything running in the background — no bar, no pause, and a list that is already up to date when you return, at the cost of the work it takes to keep it that way. Mail is collected by the agent either way, so nothing is ever missed. Stored in this browser only.
Which way the composer's Send as HTML email button starts. Turned on, the markdown you write is rendered and the message is sent as HTML, so headings, lists and links arrive formatted. Turned off, the message goes out as plain text exactly as you typed it. Either way it stays a per-message choice. Stored in this browser only.
How long a message you send sits in the Outbox before it
actually goes out — the window in which you can still stop it. Every
message in the Outbox has Send now and Cancel send
on it, whatever this is set to. 0 sends straight away.
Applies to messages written from now on, and to every browser: this
one is stored on the server.
The paragraphs you write are checked by the LanguageTool server this install runs on its own network. Quoted text, code and the footer the composer puts in are left out, and nothing is sent anywhere else. Add to dictionary and Turn off this rule in the composer fill the two lists above. Stored on the server, so every browser gets the same.
Spelling and grammar are not set up on this server.
They need a LanguageTool running next to meerail: start the
grammar compose profile and set url under
[grammar] in meerail.toml (see
meerail.example.toml). Until then the browser's own
spell checker underlines the composer.
With a model saved, the robot beside the search box starts working — describe the mail you want and it writes the query — and more robots appear on the reading pane, where they can summarise a conversation, pull out what you need to do, draft a reply, or explain an attachment. All of them send text to the provider you pick here; nothing is sent until you press one of those buttons.
The key is encrypted in the database and never sent to the browser: every
call is made by the server. Other (OpenAI-compatible) is any
endpoint speaking OpenAI's /chat/completions — Ollama, LM
Studio, OpenRouter, Groq, Mistral, Gemini's compatibility URL. Pointing
it at a local model needs
server.llm_allow_private_hosts in meerail.toml,
because the server, not the browser, is what makes the request.
Copy it from Meerato's API page. With one saved, an Add Task button appears on the reading pane and on every message: the subject becomes the task title, the body its text, and any attachments you tick are uploaded with it. Leave the field empty to remove it.
A saved token is shown as •••••••• and never leaves the
server. Edit the address around it and the token is kept; to change
the token itself, paste the whole URL again.
—
Once a day the server asks github.com whether a newer meerail has
been released, and says so in the sidebar if one has. It sends
nothing about you or your mail — only the request itself. Set
update_check = false under [server] in
meerail.toml to stop it making that request at all.
The message body becomes the task text.
Plain words are ANDed — every one of them has to appear somewhere in
the mail: subject, participants, body, or the text of an attachment. Wrap a phrase in
"double quotes" to match it exactly, spaces and all.
Filters narrow the results instead of searching text, so they work on their own as well as alongside words. Mixing them is an AND.
:unread |
Conversations with at least one unread message. |
:read |
Conversations you have read all the way through. |
:has-attachment |
Only mail that carries an attachment. |
:no-trash |
Leave out mail that is only in Trash. A search reads every folder, so without this the copy you just deleted is still a result. |
:from pattern |
Sender address or display name matches. |
:to pattern |
Any recipient matches — To, Cc and Bcc. |
:similar fingerprint |
Mail whose body says the same thing as this one, however differently the subject is worded. The value is a message id, or one of the fingerprints the Cleanup panel puts in this box for you. |
The pattern in :from and :to is always a
regular expression, whether or not the Regex switch is on — a plain address works as
one. Use quotes if it contains a space, or :from=pattern if you prefer.
invoice :unread | Unread mail mentioning “invoice”. |
:from @acme\.com :has-attachment |
Everything anyone at Acme sent you with a file attached. |
:to (ada|grace)@ | Addressed to either of them. |
"board meeting" :from ada | That phrase, from Ada. |
:from noreply :no-trash |
Everything from a no-reply address that you have not already binned. |
:similar 8412 |
Everything built from the same template as message 8412 — the other ninety property alerts, none of which share a subject with it. |
The Regex switch turns the rest of the query into a POSIX regular expression instead of a list of words. The scope and time pickers next to it narrow the search the same way the filters do.
If a model is configured in Settings, the robot beside this ⓘ writes one of these for you: describe the mail in your own words and the query lands in the search box, where you can read it, change it, and pick the syntax up for next time.
meerail can hand four jobs to a language model, once you tell it which one to use. Nothing is sent anywhere until you press one of these buttons yourself, and none of them touches your mail on its own — each one answers with text you then decide what to do with.
To switch them on, open Settings → AI and save a provider, an API key and a model. The key is encrypted in the database and never sent back to the browser: every call is made by the server.
You do not need to buy anything, and the mail does not
have to leave your machine. Ollama runs a model locally: install it,
ollama pull llama3.1, then pick Other (OpenAI-compatible)
here, set the base URL to http://localhost:11434/v1, leave the key
blank and type the model's name. LM Studio and vLLM work the same way. A local
address needs server.llm_allow_private_hosts = true in
meerail.toml — the request is made by the server, not by this
browser, so it has to be told that a private host is on purpose.
In your own words — who it was from, roughly when, what it was about. The query comes back into the search box so you can see how it was written, edit it, and use the same syntax yourself next time.
The mail is sent, then filed in Meerato's Backlog. It moves to Now on that date.