nmh vs Notmuch Emacs interface
nmh: The MH message handling system: separate shell commands to read, file, search and send mail stored one file per message.
Notmuch Emacs interface: Emacs front end for notmuch that reads, searches, tags and composes mail from a local Maildir.
Differences
- nmh is a command-line program; Notmuch Emacs interface is a mail client that runs inside Emacs.
- Only nmh has built-in POP3 and mbox.
- Only Notmuch Emacs interface has built-in notmuch.
- Notmuch Emacs interface has mouse support; nmh does not.
- Notmuch Emacs interface has OpenPGP; nmh does not.
- Notmuch Emacs interface has S/MIME; nmh does not.
- Notmuch Emacs interface has OAuth2 sign-in; nmh does not.
- Notmuch Emacs interface has threaded views; nmh does not.
- nmh is written in C; Notmuch Emacs interface in Emacs Lisp.
- Configuration: nmh uses ~/.mh_profile and mts.conf text files, and Notmuch Emacs interface uses Emacs Lisp in init.el plus the notmuch config file.
Side by side
| nmh | Notmuch Emacs interface | |
|---|---|---|
| Interface | Command-line tools and prompts | Runs inside Emacs |
| Language | C | Emacs Lisp |
| License | BSD 3-Clause | GPL 3.0 or later |
| Latest version | 1.8 | 0.40 |
| Linux | Native | Native |
| macOS | Native | Native |
| Windows | Through WSL | Through WSL |
| BSD | Native | Native |
| Android | Through Termux | Through Termux |
| IMAP | Through a separate tool | Through a separate tool |
| POP3 | Yes | Through a separate tool |
| SMTP | Yes | Yes |
| JMAP | No | No |
| Maildir | Yes | Yes |
| mbox | Yes | No |
| notmuch | No | Yes |
| OpenPGP | No | Yes |
| S/MIME | No | Yes |
| OAuth2 sign-in | No | via script |
| Threads | No | Yes |
| Search | pick command matches header fields and message text | notmuch Xapian full-text search with tags |
| HTML mail | via mhshow with an external converter such as w3m | built-in, rendered with the Emacs shr library |
| Mouse | No | Yes |
| Multiple accounts | via per-command switches or separate profiles | Yes |
| Offline use | full; messages are stored as local files | full; reads a local Maildir synced by mbsync or OfflineIMAP |
| Calendar | replies to invitations with mhical | shows text/calendar parts; no invitation replies |
| Contacts | aliases via MailAliases and the ali command | address completion from the notmuch index |
| Vim-style keys | No | No |
| Configuration | ~/.mh_profile and mts.conf text files | Emacs Lisp in init.el plus the notmuch config file |
Which to choose
Choose nmh for
- Every action is a shell command, so mail handling is easy to script.
- One file per message lets grep, find and other Unix tools work on mail.
- Built-in POP3 and SMTP with TLS and SASL; reads mbox and Maildir drops.
Watch out for
- No IMAP; IMAP mail must be synced to a Maildir first and then incorporated.
- No built-in OpenPGP or S/MIME, and no thread view.
- SMTP authentication needs nmh built with Cyrus SASL and its PLAIN or LOGIN plugin.
Choose Notmuch Emacs interface for
- Tag-based organization with fast full-text search over all local mail.
- Shows a whole thread in a single buffer.
- Handles PGP/MIME and S/MIME signatures and decryption through notmuch.
Watch out for
- No built-in IMAP; needs mbsync or a similar sync tool.
- Custom tags stay in the local index; only standard flags such as unread and replied reach the IMAP server.
- Requires Emacs and some Emacs Lisp to configure.
Questions
What is the difference between nmh and Notmuch Emacs interface?
nmh is a command-line program; Notmuch Emacs interface is a mail client that runs inside Emacs. Only nmh has built-in POP3 and mbox. Only Notmuch Emacs interface has built-in notmuch.
Which runs on Windows, nmh or Notmuch Emacs interface?
On Windows, nmh runs through WSL. On Windows, Notmuch Emacs interface runs through WSL.
See also: nmh alternatives, Notmuch Emacs interface alternatives.