Mutt, NeoMutt, mblaze or mu for recovering mail from a local Maildir
Mutt, narrowly ahead of NeoMutt, is the careful way to find one message in a Maildir archive and save its attachment without changing the archive. Open the folder read-only and keep the client updated.
Mutt
Opens a Maildir read-only with one command, finds a message by words in its body, and saves the decoded attachment where you choose. Its 2026 security fixes shipped quickly with CVE numbers.
A narrow lead over NeoMutt (4.50 to 4.25). Update to 2.4.3 or a patched package, and do not reuse a recovered message as a template.
Why Mutt is our PickTeam behind Mutt? Get your award badge
No Rising Star selected
Himalaya first appeared in 2021 and meli was publicly available by 2020. Their latest versions do not make them new products.
A recent update alone does not make an established client a new entrant.
Who is this article for? Linux terminal users recovering a known message and its attachment from a Maildir archive already stored on disk, without an account or network connection.
About 23 min read
What Preferred Pick, Rising Star and Ready to Rock mean
The quick list
Choose Mutt for one careful recovery. NeoMutt suits existing users, mblaze suits shell workflows, and mu suits repeated indexed searches. All four are free.
All four are free, open-source programs with no account or subscription for a Maildir on your own disk, checked November 7, 2026. Licences: GPL for Mutt and NeoMutt, public domain for mblaze, GPLv3 or later for mu. Backup, storage and your time are separate costs.
The comparison at a glance
Compare how each client opens a Maildir on your disk, finds one message, saves its attachment and leaves the archive alone, and its 2026 security and maintenance record.
Mutt leads narrowly for one careful recovery, followed by NeoMutt, mblaze for shell workflows and mu for repeated indexed searches. All tools remain selectable.
Hides matching answers for the selected tools. Unknowns and unverified claims stay visible.
| Feature | Mutt | NeoMutt | mblaze | mu |
|---|---|---|---|---|
| Best fit | Preferred Pick: manual recovery from a read-only copy of the archive, with fixes that distributions track | Readers who already use NeoMutt, or archives large enough to index with notmuch first | Direct recovery for shell users, without an index; separate search and extraction commands | Repeated indexed searches across a large archive; Mutt is simpler for one recovery |
| Opening a Maildir already on disk | mutt -R -f with the folder path opens it read-only; no account or configuration file needed | neomutt -R -f with the folder path opens it read-only; no account needed | Reads local Maildir messages directly; no account or database required | Configure a local Maildir root and build a separate Xapian index for search; extraction alone needs no index |
| Finding one message among similar ones | Limit the list with ~b (body), ~B (whole message), ~s or ~d patterns; body patterns read every message, so they slow down on large folders | The same ~b and ~B patterns; can also open a notmuch search as a read-only folder | magrep searches headers or plain-text body parts using regular expressions | Query body text and message fields in the index, then pass the message file to mu extract |
| Saving the attachment | Attachment menu saves the decoded part to a file you name | Attachment menu saves the decoded part to a file you name | mshow -t lists MIME parts; mshow -x extracts selected part bytes without rendering conversion; refuses existing output files | mu extract lists MIME parts and saves selected parts into a separate directory; refuses overwriting by default |
| Leaving the archive unchanged | Read-only mode with -R; without it, quitting can mark messages old or read and rename their files | Read-only mode with -R; same defaults as Mutt without it | Search and extraction read source messages; use a separate output directory; flag changes and moving mail are separate commands | Keep its index outside the archive; searching and extracting read message files, while moving or flagging is a separate action |
| Security record | 2026 flaws fixed in 2.3.2 (April) and 2.4.3 (October), all with CVE numbers; most are in network, signature-checking or encryption code; one involves reusing a crafted message as a template | 2026 fixes released in May and June, mainly in network and authentication code; no CVE numbers or advisories published; attachment file-name fix merged October 19, unreleased | Debian lists no package advisories; GitHub has no detected policy or published advisories; limited reporting, not proof of safety | Debian lists no package advisories; GitHub has no detected security policy or published advisories; these are limited reporting signals |
| Reader reviews | No reviews yet. Write a review | No reviews yet. Write a review | No reviews yet. Write a review | No reviews yet. Write a review |
All four are free terminal programs. Work on a copy of the archive, open it read-only where the client allows, keep the original untouched, and compare a recovered file with any checksum or second copy you have. None of these sources measures failure rates or speed on large archives. Mutt and NeoMutt evidence dates to October 19, 2026; costs, mblaze and mu were checked November 7, 2026.
mu sources, checked November 7, 2026: project and licence, releases, extraction manual, Debian security record and GitHub security page. mblaze sources: body search, extraction and extraction source, checked November 7, 2026. Separate shell commands add work to one recovery.
All features and sources 11 criteria
Open the groups that matter to you. They compare the same selected tools. “Planned” means future work, not an available feature. Sources include the published conditions.
Finding the message and saving the attachment
Show 4 criteria
| Feature | Mutt | NeoMutt | mblaze | mu |
|---|---|---|---|---|
| Opening a Maildir already on disk | mutt -R -f with the folder path opens it read-only; no account or configuration file needed | neomutt -R -f with the folder path opens it read-only; no account needed | Reads local Maildir messages directly; no account or database required | Configure a local Maildir root and build a separate Xapian index for search; extraction alone needs no index |
| Finding one message among similar ones | Limit the list with ~b (body), ~B (whole message), ~s or ~d patterns; body patterns read every message, so they slow down on large folders | The same ~b and ~B patterns; can also open a notmuch search as a read-only folder | magrep searches headers or plain-text body parts using regular expressions | Query body text and message fields in the index, then pass the message file to mu extract |
| Saving the attachment | Attachment menu saves the decoded part to a file you name | Attachment menu saves the decoded part to a file you name | mshow -t lists MIME parts; mshow -x extracts selected part bytes without rendering conversion; refuses existing output files | mu extract lists MIME parts and saves selected parts into a separate directory; refuses overwriting by default |
| Leaving the archive unchanged | Read-only mode with -R; without it, quitting can mark messages old or read and rename their files | Read-only mode with -R; same defaults as Mutt without it | Search and extraction read source messages; use a separate output directory; flag changes and moving mail are separate commands | Keep its index outside the archive; searching and extracting read message files, while moving or flagging is a separate action |
These selected tools have matching answers in this group. Turn off “Show differences only” to see them.
Sources for finding the message and saving the attachment
Documentation read October 19, 2026: the Mutt manual (version 2.4.3), NeoMutt command line, patterns and notmuch pages manuals. mblaze: body search, extraction manual and source, November 7, 2026. Documented behaviour, not measured reliability.
Security and maintenance
Show 4 criteria
| Feature | Mutt | NeoMutt | mblaze | mu |
|---|---|---|---|---|
| Release: Mutt and NeoMutt checked October 19; mblaze and mu November 7, 2026 | 2.4.3, October 9, 2026; eight releases in 2026 | 20260616, June 16, 2026; later fixes not yet released | 1.4, January 17, 2026 (checked October 19, 2026); human source commits October 20; inspected source checked November 7, 2026 | 1.14.4, October 14, 2026; checked November 7, 2026 |
| Security record | 2026 flaws fixed in 2.3.2 (April) and 2.4.3 (October), all with CVE numbers; most are in network, signature-checking or encryption code; one involves reusing a crafted message as a template | 2026 fixes released in May and June, mainly in network and authentication code; no CVE numbers or advisories published; attachment file-name fix merged October 19, unreleased | Debian lists no package advisories; GitHub has no detected policy or published advisories; limited reporting, not proof of safety | Debian lists no package advisories; GitHub has no detected security policy or published advisories; these are limited reporting signals |
| What distributions ship | Debian 13 carries every 2026 fix; Ubuntu 24.04 and 26.04 (2.2.12, 2.2.13) had not triaged them | Debian 13: 20250510; Ubuntu 24.04: 20231103, with security fixes only through Ubuntu Pro; Ubuntu 26.04: 20260105 | Debian carries older 1.1; inspected extraction source is current development code, not every historical package | Debian 13: 1.12.9; the project maintains 1.12 for critical fixes; checked November 7, 2026 |
| Who maintains it | One lead maintainer, Kevin McCarthy, who makes every release | A team led by Richard Russon; reports go to him by email | Leah Neukirchen and contributors | Dirk-Jan C. Binnema and contributors |
These selected tools have matching answers in this group. Turn off “Show differences only” to see them.
Sources for security and maintenance
Read October 19, 2026: Mutt news, the 2.4.3 and 2.3.2 announcements and the Debian security tracker; NeoMutt releases, security policy and pull request 5055; Ubuntu notice USN-7204-1 and Ubuntu’s CVE records; the OSV vulnerability database. mblaze: Debian security record and GitHub security page, November 7, 2026.
Setup and cost
Show 2 criteria
| Feature | Mutt | NeoMutt | mblaze | mu |
|---|---|---|---|---|
| Cost and licence | $0; GPL; no account | $0; GPL; no account | $0; public domain; no account | $0; GPLv3 or later; no account |
| Setup and documentation | One command, no configuration file; complete manual for the current version | One command, no configuration file; online reference marked “Under Development” | Separate shell tools, regex search and MIME part selection; manual pages and public source; limited packaging | Maildir root and index setup, then separate search and extraction commands; README and manual pages |
These selected tools have matching answers in this group. Turn off “Show differences only” to see them.
Sources for setup and cost
All four are free programs with public source that need no account or subscription to read a Maildir on your own disk, checked November 7, 2026. Backup, storage and your time are separate costs.
Earlier hands-on check, October 3, 2026
Show 1 criteria
| Feature | Mutt | NeoMutt | mblaze | mu |
|---|---|---|---|---|
| Earlier hands-on check, October 3, 2026 (historical) | Not part of that check | Ubuntu 20231103 package: body pattern found the message; saved attachment matched its SHA-256; 50-message synthetic archive unchanged | Not part of that check | Not part of that check |
These selected tools have matching answers in this group. Turn off “Show differences only” to see them.
Sources for earlier hands-on check, october 3, 2026
Historical observation from a small Linux check on October 3, 2026, before Practical Picks adopted its research-only method later that day. The NeoMutt observation used a copy of a 50-message synthetic Maildir and an older Ubuntu package. The attachment was UTF-8 text only; these observations did not decide any recommendation here. Earlier check record, October 3, 2026.
What matters when choosing
Mutt is our Preferred Pick for finding one message in a Maildir archive already on your disk and saving its attachment, but its lead over NeoMutt is narrow. Start it with mutt -R -f and the folder’s path. That opens the folder read-only, with no account, server or configuration file, and read-only mode stops Mutt marking messages as read or renaming their files when you quit. In the message list, a limit pattern such as ~b finds a message by words in its body even when dozens share a subject, and the attachment menu saves the decoded file under a name you choose. NeoMutt does all of this the same way. Maintenance decided it. Mutt’s 2026 security fixes came with CVE numbers, which let Linux distributions track them; they arrived in releases 2.3.2 (April 26) and 2.4.3 (October 9), and Debian 13 already ships them all. On our five-point scale Mutt scored 4.50 and NeoMutt 4.25, a narrow lead that one changed score on security and maintenance could reverse. Mutt is free under the GPL. Mutt, manual
Keep Mutt up to date. Most of its 2026 flaws sit in network, signature-checking or encryption code, but the one fixed in 2.4.3 is a heap overflow that a crafted Content-Type header triggers when you reuse a message as a template for a new one. Never do that with recovered mail. Ubuntu 24.04 ships Mutt 2.2.12 and Ubuntu 26.04 ships 2.2.13, and as of October 19, 2026, Ubuntu had not yet triaged the 2026 fixes for either; Debian 13’s security updates include them all. Work on a copy of the archive, keep the original untouched, and compare a recovered file with any checksum or second copy you have. 2.4.3 announcement, Debian security tracker
Also consider NeoMutt if you already use it, or if your archive is large enough to index with notmuch first. It started as a home for Mutt patches and became a separate fork, and for this job it works the same way: neomutt -R -f, the same body patterns and the same attachment menu. It can also open the results of a notmuch search as a read-only folder, which helps when searching every message file in turn would be too slow. It lost on maintenance, not features. Its team released four versions in 2026, the last on June 16, but it publishes no advisories or CVE numbers for its fixes, so Debian 13 and Ubuntu’s free archive ship versions without them, and fixes merged since June, including one for attachment file names, are not yet in a release. NeoMutt, June 2026 release, notmuch support
No Rising Star selected. The newer-looking clients we could check do not qualify: Himalaya first appeared in 2021 and meli was publicly available by 2020. A new version does not make either a new product. Himalaya 2.2.1 also still changes the encoding of text attachments and can print control characters from a message to your terminal; its fixes remain unreleased as of November 7, 2026. Himalaya changelog, releases, meli releases (checked November 7, 2026).
Mutt
Preferred Pick · manual recovery from a local Maildir
Choose Mutt to find one message in an archive on your disk and save its attachment. Open the folder read-only with mutt -R -f, keep Mutt updated, and do not reuse a recovered message as a template.
Reasons to choose it
- Opens a Maildir read-only with one command and no configuration file
- Body and header patterns pick one message out of many with the same subject
- 2026 security fixes released promptly with CVE numbers that distributions track
What to watch
- Keyboard-driven; the patterns and menus take some learning
- Body searches read every message, so they slow down on very large folders
- One lead maintainer; Ubuntu had not triaged its 2026 fixes by October 19
Mutt reads Maildir, mbox, MMDF and MH folders and recognises the format by itself. mutt -R -f followed by the folder’s path opens it read-only; without -R, quitting can mark unread messages as old or read, which renames their files in a Maildir. In the message list, l limits the view to messages matching a pattern. ~b searches message bodies, ~B whole messages including headers, ~s subjects and ~d a date range, so a few words you remember from the message can pick it out of many with the same subject. The manual warns that body patterns read every message in, so on a very large folder they are slow. Press h to see the full headers, including the date and message ID. In the attachment menu (v), s saves the selected part, decoded, to a file you name, and $attach_save_dir sets a default folder for it. Manual
Mutt is the oldest client here and, in Debian’s records, the most widely installed. It is free under the GPL, and Ubuntu carries it in its main archive. Kevin McCarthy, its lead maintainer, made eight releases in 2026, from 2.3.0 in January to 2.4.3 on October 9. Release 2.3.2 (April 26) fixed five reported problems, later given six CVE numbers, in IMAP login code, URL decoding and the code that checks signed and encrypted mail. Release 2.3.3 (June 12) fixed a crash on deeply nested messages. Release 2.4.3 fixed CVE-2026-107570, a heap overflow triggered by a crafted Content-Type header when a message is reused as a template through resend-message; Ubuntu rates it medium priority and notes that it needs that user action. Mutt has said it will not change how it handles three 2024 reports about headers that signing and encryption do not protect, which its manual documents instead; they concern trusting the headers of signed or encrypted mail, not opening a folder or saving a file. Mutt news, Debian note on the 2024 reports, 2.3.2 announcement, 2.4.3 announcement
Read the full Mutt analysis and sources
What you get depends on your distribution. Debian 13’s security updates contain every 2026 fix. Ubuntu 24.04 (2.2.12) and 26.04 (2.2.13) still listed them as needing triage on October 19, 2026, so on Ubuntu you are running a version with known flaws. Choose a patched build where you can, and follow the safe path either way: read-only mode, no template reuse, and no network accounts configured. Every release depends on one lead maintainer, which is the main continuity risk. Mutt was not part of our earlier hands-on check. Debian security tracker
Used Mutt? Share your experience to help other readers choose.
NeoMutt
Also consider · very large archives or existing NeoMutt users
Choose NeoMutt if you already use it, or if you will index a very large archive with notmuch and want to browse the search results read-only. It recovers a message the same way Mutt does.
Reasons to choose it
- Same read-only mode, body patterns and attachment menu as Mutt
- Can open a notmuch search as a read-only folder
- Active team; four releases in 2026 to June
What to watch
- No CVE numbers or advisories, so distributions often lack its fixes
- Fixes merged since June 16, 2026, including one for attachment file names, are not yet released
- Ubuntu 24.04’s package gets security fixes only through Ubuntu Pro
NeoMutt describes itself as a mail reader based on Mutt that began as a place to gather patches against Mutt and became a fork. For this recovery job it behaves the same way: neomutt -R -f opens a folder read-only, ~b and ~B patterns search bodies and whole messages, and the attachment menu saves a decoded part. It adds support for notmuch, a separate search index. Once you have indexed an archive with notmuch, which writes a database, NeoMutt can open the results of a query as a read-only virtual folder instead of searching every message file in turn. It is free under the GPL. Command line, patterns, notmuch support
NeoMutt is actively maintained by a team led by Richard Russon, with releases on January 5, April 6, May 4 and June 16, 2026. The May and June releases fixed security problems, almost all in network code (IMAP, POP, GSSAPI login and certificate checks) and the message cache, which a local archive does not use. NeoMutt publishes no security advisories, its 2026 fixes carry no CVE numbers, and its security policy asks for reports by email to its lead developer. As a result, distribution security teams have little to track. Debian 13 ships 20250510, Ubuntu 26.04 ships 20260105, and Ubuntu 24.04 ships 20231103, whose 2025 security update (USN-7204-1) is available only with Ubuntu Pro. Since June 16, the development code has gained more hardening fixes. On October 19, 2026 it merged one that keeps an attachment’s sender-chosen file name from placing the saved file outside your save folder when the non-default $attach_save_without_prompting option is set. That fix is not yet in a release, so leave the save prompt on. June 2026 release, security policy, USN-7204-1, pull request 5055
Read the full NeoMutt analysis and sources
In an earlier hands-on check on October 3, 2026, before we adopted our research-only method later that day, Ubuntu 24.04’s NeoMutt package 20231103 opened a 50-message synthetic Maildir, a ~b pattern picked the target out of 25 messages, several with identical subjects, and the attachment menu saved its UTF-8 text attachment with the expected SHA-256 checksum. Afterwards every message file still had its original bytes and name. That package predates the security fixes described above, so read it as a dated observation, not a version to use. Earlier check record, October 3, 2026
Used NeoMutt? Share your experience to help other readers choose.
mblaze
Evaluated alternative · direct recovery with shell commands
Choose mblaze if you prefer separate shell commands for body search and extracting selected MIME parts. Save into a separate directory; Mutt is simpler for one recovery.
Reasons to choose it
- Searches message bodies and headers without an index
- Extraction writes part bytes without rendering conversion
- Strips directory components and refuses existing output files
What to watch
- Separate commands, regular expressions and MIME part numbers take learning
- Debian carries an older 1.1 package; inspected source is current development code
- No detected GitHub security policy or published advisories; hostile-mail reliability is unmeasured
mblaze is a collection of command-line tools that reads Maildir messages directly, without an account or a search database. magrep searches headers or plain-text body parts with a regular expression; mshow -t lists MIME parts and mshow -x extracts a selected part. Choose it if you already work comfortably with shell pipelines. Mutt is simpler for one recovery because its search and attachment menu sit in one interface. Project, body search manual, extraction manual (checked November 7, 2026).
Use a separate output directory and select the attachment by part number. The published extraction code writes the part’s bytes without the character-set conversion used by its text renderer, strips directory components from output names and refuses to overwrite an existing file. These search and extraction commands read the source messages; other tools in the collection can change flags or move mail. Avoid raw attachment output to the terminal. This is documentation and source-code evidence, not a measured recovery success rate. Extraction source (checked November 7, 2026).
Read the full mblaze analysis and sources
mblaze is in the public domain and maintained by Leah Neukirchen and contributors. Release 1.4 is dated January 17, 2026 (checked October 19, 2026); source commits remained active on October 20. Debian carries the older 1.1 package, while the inspected extraction code is the current development source, so we have not established that every older package behaves identically. Debian lists no package advisories, and GitHub has no detected security policy or published advisories; neither proves safety with hostile mail. It scored 4.00, behind Mutt and NeoMutt, with its separate commands and package differences adding work. Releases, Debian security record, GitHub security page (checked November 7, 2026).
Used mblaze? Share your experience to help other readers choose.
mu
Evaluated alternative · repeated searches across a large archive
Choose mu if you expect to search this archive repeatedly and prefer commands to a full-screen client. Build its index outside the archive, then extract the selected attachment to a separate folder.
Reasons to choose it
- Searches body text and message fields through a local index
- Extracts attachments without needing Emacs or even an index for that step
- Refuses to overwrite existing output files by default
What to watch
- Indexing and query setup add steps to a one-off recovery
- A separate index needs disk space and upkeep
- No published GitHub security policy or advisories; absence of reports does not prove safety
mu is a set of command-line tools for Maildir messages, with an optional Emacs client called mu4e. It searches body text and message fields after building a Xapian index. You can then list a message’s MIME parts with mu extract and save the selected attachment into a separate output directory. Extraction itself does not require an index; finding a message by its contents does. No Emacs client is needed for this command-line route. The extra indexing and query setup make it less convenient than Mutt for recovering one known message. Project, extraction manual (checked November 7, 2026).
Keep the index outside the archive and save recovered files elsewhere. mu extract refuses to overwrite existing files unless explicitly asked. These commands read the message files; moving or flagging messages is a separate operation. mu is free under GPLv3 or later, and its source remains available independently of any mail provider. Dirk-Jan C. Binnema and contributors maintain it; release 1.14.4 is dated October 14, 2026. Debian 13 carries the older 1.12.9 line, which the project still maintains for critical fixes. Debian’s security tracker lists no advisories for the package, and GitHub has neither a detected security policy nor published advisories; that is limited reporting evidence, not proof that parsing hostile messages is safe. We scored mu 3.70, behind Mutt, NeoMutt and mblaze. Releases, security reporting, Debian record (checked November 7, 2026).
Used mu? Share your experience to help other readers choose.
Which product are we missing?
Know a product that belongs in this article? Tell us what it does differently and why it deserves a closer look. Newcomers welcome.
Readers and product teams can suggest candidates. Suggestions inform our research; they do not guarantee inclusion or a recommendation.
Opens an email draft with this article attached as a link. Nothing is sent until you send it.
No email app? Send the product name, website, and this article’s title to admin@practicalpicks.guide.
What people are saying
We have no Practical Picks reader reviews for these tools yet.
Package records give a rough sense of use. In Debian’s opt-in popularity contest on October 19, 2026, about 23,700 reporting systems had Mutt installed, 850 NeoMutt and 270 aerc; Debian does not package Himalaya. Homebrew counted about 8,000 installs of Mutt, 5,400 of NeoMutt and 1,800 of aerc in the year to October 19. It counted about 114,000 of Himalaya, but AI-agent tools such as OpenClaw list it as a Homebrew install step for handling mail, so that figure says little about recovering an archive. None of these numbers is a market share. Debian popularity contest for Mutt, Homebrew: Mutt, NeoMutt, aerc, Himalaya, OpenClaw mail skill
Individual reports are sparse. A NeoMutt user reported in December 2025 that a newer version no longer let them browse down through folders when saving a whole message into another Maildir; the issue was still open on October 19, 2026, and it does not affect saving an attachment. These are single reports, not failure rates. NeoMutt issue 4740
How we researched
This is public-source research. For this review we did not install, run or test any of these programs, create accounts or contact the projects. Our sources were each project’s manual and documentation, release notes and changelogs, security announcements and the Debian, Ubuntu, CVE and OSV vulnerability records, issue trackers, package records from Debian, Ubuntu and Homebrew, and the projects’ licence and funding statements, read on October 19, 2026, with costs, candidate coverage and release histories revisited on November 7, 2026. No project supplied access or payment, and our links carry no affiliate tracking.
This article first appeared on October 3, 2026, and then rested on a small hands-on check run earlier that day, before we adopted our research-only method. We keep that check as a dated observation. On Ubuntu 24.04, NeoMutt 20231103 and Himalaya 2.2.1 each found one message in a 50-message synthetic Maildir and saved its UTF-8 text attachment with the expected checksum, and aerc 0.17.0 crashed during its body search. It shows what happened once with those builds and that archive, not how the clients handle real or hostile mail, and it did not decide any recommendation here. Earlier check record, October 3, 2026
We wrote this for a Linux user who works in a terminal and has a Maildir archive on disk, perhaps restored from a backup or copied from an old server, and needs to find one known message and save its attachment intact, without an account, a network connection or changes to the archive. Before scoring, we fixed four criteria and their weights: finding the message and saving the attachment exactly (30%), leaving the archive unchanged (20%), security and maintenance (30%), and setup and documentation (20%). Cost carries no weight in those criteria. The four compared tools are free for this use. Mutt scored 4.50 on our five-point scale, NeoMutt 4.25, mblaze 4.00 and mu 3.70. Mutt’s 0.25 lead over NeoMutt is smaller than the 0.30 that one full point on either of the heaviest criteria is worth, and it rests on our medium-confidence judgment of how each project’s security fixes reach users, so we call it narrow. Mutt stayed ahead when we weighted the four criteria equally, and when we moved weight from security to finding and saving. If NeoMutt released its pending fixes and distributions picked them up, Mutt’s lead would shrink to 0.10.
We revisited terminal mail clients on November 7, 2026 using the Terminal Email directory, the ArchWiki application list, project repositories and release histories. Terminal Email is made by Forward Email and promotes its own client, so we used it to find candidates, not to establish quality. Mutt and NeoMutt lead for one-command recovery, followed by mblaze for shell workflows and mu for repeated indexed searches.
aerc scored 3.50. Its body search and attachment saving are documented, but it has no read-only mode: disable auto-mark-read before opening an archive. Its fixed CVE and older Ubuntu packages remain maintenance limits. notmuch scored 3.50. It can search and extract attachments without a front end: notmuch show with a selected part writes decoded bytes without changing their character set. Its index can live outside the archive, but you must configure that and disable Maildir flag synchronization to prevent tag changes renaming message files. Its extra setup puts it behind aerc on finding and extracting when their totals tie. bower scored 3.30: it adds a full-screen interface to notmuch, with documented commands for saving a highlighted part, but its configuration and package or Mercury build requirements add work. notmuch-emacs and alot add interfaces too, but the available guides do not establish their exact received-attachment output. Configuration, extraction, bower documentation (checked November 7, 2026).
meli’s current documentation provides a read_only account option and a save-attachment command, but does not establish whether saving text preserves its decoded bytes without character-set conversion. Sup documents how to disable global and per-source flag synchronization, but its exact attachment output remains uncertain. Cone’s local Maildir and attachment-download descriptions do not establish exact output or source-write defaults; its price is unknown. GNU Mailutils documents saving selected message parts and readonly mode, but the interaction between saving and output character-set settings is unclear. The mu4e overview does not establish its attachment-save or archive-write defaults. meli manual, Sup synchronization, Cone library overview, GNU Mailutils manual, mu4e (checked November 7, 2026).
S-nail’s manual says saving text parts converts their character set, so it does not establish exact recovery of arbitrary text attachments. Himalaya scored 2.95: release 2.2.1 converts text attachments to UTF-8, and its changelog still lists terminal-output, symlink and overwrite fixes as unreleased. Neither is recommended for this task. Alpine’s stock release lacks documented Maildir support; desktop programs such as Thunderbird, Evolution and KMail are outside this Linux terminal comparison. For a desktop window, see our Windows email client comparison. Forward Email’s terminal client requires an account, and we found no in-place Maildir recovery evidence for Matcha or nmail. Gnus, Mew, MH-E, Rmail, Wanderlust and nmh could not be checked in enough depth to establish this exact recovery route; the directory descriptions do not settle exact output and source-write behaviour. No checked candidate both meets the task and establishes a first public release within the past two years. S-nail manual, Himalaya changelog, Terminal Email (checked November 7, 2026).
| Tool | Public sources | What remains uncertain |
|---|---|---|
| Mutt | Manual for version 2.4.3, project news, the 2.3.2 and 2.4.3 announcements, Debian and Ubuntu CVE records, OSV, Debian and Homebrew package records. | When Ubuntu will ship the 2026 fixes, how long one lead maintainer can carry the project, behaviour with very large folders. |
| NeoMutt | Command-line, pattern and notmuch documentation, 2026 release notes, security policy, recent pull requests and issues, Ubuntu USN-7204-1, Debian and Ubuntu package records. | When the fixes merged since June 16, 2026 will be released, whether NeoMutt shares Mutt’s template flaw (no public record either way), which fixes distributions carry. |
| mblaze | Body-search and extraction manuals, extraction source, project history, Debian and GitHub security records. Checked November 7, 2026. | Correspondence of older packaged versions to current source; hostile-message failure rates and dependency audit. |
| mu | Project README, release history, extraction manual, Debian package and security record. Checked November 7, 2026. | Failure rates on hostile messages; a complete dependency security audit. |
| Other candidates | November 7, 2026 directory, repository and manual research. | Exact attachment output for meli, Sup, Cone, GNU Mailutils and additional interfaces; frontend source-write defaults and Emacs/MH recovery routes. |
None of these sources measures failure rates, speed on large archives or how each client handles hostile mail. Next substantive review is due December 18, 2026, or sooner if Himalaya or NeoMutt publishes a release with the fixes described here, or Ubuntu ships Mutt’s. Found a change? Contact the editors.
Sources and evidence
Checked October 19, 2026: Mutt project news and releases, manual, 2.3.2 announcement, 2.4.3 announcement and Debian security tracker for CVE-2026-107570; NeoMutt project site, June 2026 release, command line, patterns, notmuch support, security policy, pull request 5055, issue 4740 and Ubuntu USN-7204-1; aerc project site, changelog, search, command and configuration manuals, CVE-2025-49466, its fix and Debian record; Himalaya project README, changelog, 2.2.1 release, search help, configuration sample, security policy and issue 711; Other recovery sources: notmuch configuration, mblaze, Alpine and ImportExportTools NG; use signals: Debian popularity contest, Homebrew records for Mutt, NeoMutt, aerc and Himalaya, and the OpenClaw mail skill; and the earlier check record, October 3, 2026, with its synthetic archive. No project supplied access or influenced the conclusion. No affiliate links were used. Recheck versions, Ubuntu’s CVE status and Himalaya’s next release before any public release.
No screenshots are shown: these are terminal programs, and this review is based on public sources. The earlier check record, October 3, 2026 describes the synthetic Maildir used in a small check before our research-only method.