Skip to content
mailben.ch
← All clients

NeoMutt

The NeoMutt Team·Open source·neomutt.org

Definition maintained by @wes. clients/neomutt.json

Its coordinates have never been checked by snapshot. Anyone with it installed can: ./mailbench snapshot neomutt

Reading its numbers

  • In the comparison for the floor, not the middle: a terminal client with no compositor, no layout engine and no list to virtualize is roughly the fastest a mail client can be on the hardware.

Results

Not measured yet. Run it and submit the results.

Setting it up

Install

brew install neomutt.

Add the benchmark account

Server 127.0.0.1, port 10143 (10144 for the 250k mailbox), no encryption, user bench@example.com, password bench.

  • neomutt -F harness/neomuttrc, in a Ghostty window sized to the benchmark window. No setup: the rc file points it at the server and keeps its caches in ~/mailbench/neomutt.

So it holds the whole mailbox

  • neomutt caches headers and fetches bodies when they are opened; the rc file sets both caches, so a message it has opened once is local from then on.

For a first-sync measurement

  • Quit neomutt and delete ~/mailbench/neomutt.
  • Press Enter here, then start it again.

Its window

A terminal client has no bundle of its own: the instrument finds the terminal hosting it by name, and the window title is set by neomutt. Launch and quit are not measured, because they would be the terminal's.