HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
karelzak
mutt-kz
C2012–2017
karelzak / mutt-kz

mutt-kz

mutt-kz is DEPRECATED in favor of neomutt project.

7Distinct people
10Mentions
0Explicit recommenders
297GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

mutt-kz is DEPRECATED in favor of neomutt project.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year10 dated mentions

Observed mentions: 2012-08-01 05:21:32 UTC to 2017-12-26 17:12:29 UTC.

01232012-01-01 00:00:00 UTC to 2013-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments20122013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments20142015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2017

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20122012-01-01 00:00:00 UTC2013-01-01 00:00:00 UTC303
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC000
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC303
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC101
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC202
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC101

What Hacker News says

10 sources
There's always Mutt, of course. Easily beats the ones you listed, especially when handling larger volumes of mail. Development picked up some steam again in recent years, with forks like mutt-kz[1] (now deprecated and folded into neomutt[2]) integrating awesome search functionality. Claws Mail has some fans, too, and might be more accessible to Thunderbird users. [1] https://github.com/karelzak/mutt-kz [2] https://www.neomutt.org
In Security warning for Thunderbird users and Enigmail users
https://github.com/karelzak/mutt-kz is another active fork of mutt with a whole bunch of improvements that haven't made it upstream yet. It's been accepting patches for most of the time mutt upstream had been asleep (years). For example mbox parsing in mutt-kz is about 50% faster
In Mutt 1.6
I've used mutt for ages, but a couple of years ago I switched to Karel Zak's mutt-kz branch (https://github.com/karelzak/mutt-kz), which integrates notmuch into mutt. The setup is a little fussy (although well documented), but the results are spectacular. Mutt's search was never horrible but with notmuch its nutty fast, and the tagging feature makes dealing with search and mailing lists very convenient.
In Why Some Security Experts Use Mutt
Hm, we're too deep it seems. So replying to myself. > You must be aware that notmuch is only the search backend, and for a full MUA you need frontends. Absolutely. I tried to imply that with my wry parenthesis; but it's absolutely worth pointing out clearly to unwary readers. In no way is it fair to either notmuch or sup to compare the two as equals. I'd probably lean towards mutt-kz[mk] for an out-of-box "notmuch" mua (but... mutt. Meh ;-) There's also "alot"[a]. > Another contender in the space (label- and search-centric) is mu and its ui, mu4e [1]. Something else to have in mind. Right. See also: http://dev.gentoo.org/~tomka/mail.html Recently discussed on hn: https://news.ycombinator.com/item?id=8519643 > Now if you want something that works on desktop and mobile, something worth a look would be using SQLite and its built-in full-text
Read the rest
search... see how far you can go with that. SQLite is available pretty much everywhere, Android even allows full-text search. Now what you have to do is synchronize SQLite dbs. It "shouldn't" be too hard to remove old emails from the db so you can keep X MB worth of it. You can even shoehorn it into couchbase-lite [3][4] so that sync is automagically taken care of. I've considered sqlite for some of these reasons. But couchbase-lite != sqlite, right? (Or does it use sqlite in a meaningful way; ie: can/should one use sql to interface with the stored data?). Btw, looks like you're off-by-one, in your references ;-) If using sqlite, there are a couple of schemas one might use for inspiration, such as dbmail: http://dbmail.org/dokuwiki/lib/exe/fetch.php/dbmail-er-model... Or archiveopteryx: http://archiveopteryx.org/db/schema The main sticking point, is do we really want(need) to re-index everything everywhere, how do we transparently do search local-first, while supporting hits from the server along with fetching hits/mails that are missing locally (what k9 calls "cloud search") - how do we consolidate/sync data (the two hard things in computer science is caching and naming things...). I'm not entirely convinced sqlite+built-in full text search is the best approach (I envision a useful search across some gbs of mailing list threads -- not convinced about the ranking -- but I could very well be the victim of premature optimization. And I'm a little wary of abandoning maildir for storage (on the server) -- but that might be useful anyway. > JMAP looks cool (definitely more interesting to implement than IMAP) but it seems to be more a query API than a sync API, although there are facilities to "get changes since last time" (a HUGE improvement from IMAP as deployed everywhere). Yes, that's pretty much what I gathered from the heliotrope story, that syncing was a bit of a mess. > OTOH if you can shoehorn it into couchbase-lite, you can use a generic sync protocol that can be used for other things too (caldav/carddav). Exactly. All the hard work done! For free! But seriously, couchdb was born from the ashes of lotus notes, and at least in spirit it was made for this kind of stuff... so couchdb sync, and some kind of half-assed search might be the way to go (on the server, elastic-search would probably work fine... not sure about on something like Android). > Heck, you've piqued my curiosity, I see something doable here. I'd love to hear more. I might even hack something just for fun. Great :-) If you do, please feel free to drop me an email (see profile). [mk] https://github.com/karelzak/mutt-kz [a] https://github.com/pazz/alot
In FastMail app for iOS and Android now available
$ find ~/Maildir/inbox -type f | wc -l 31439 That's after filtering out bulk mail and mailing lists. I'm a gmail user multiple times over, but use mutt + IMAP instead of webmail, which I visit once in a blue moon to do a tricky search. Yeah, I should probably practice Real Inbox Zero, but mutt's new message flag is usually good enough. It's nice having new messages in full threaded context. To get Inbox Zero in mutt, with full threads for each new message, I guess I'd have to switch to something like mutt-kz [1]. (If anyone has pointers here, I'm all ears.) Also: $ find ~/Maildir/read -type f | wc -l 53774 I've got archived mail dating back to 2006. Every once in a while I take old messages from 'inbox' and move them to 'read' to make things more manageable. It's a pretty low-tech setup. There are surely lots of fancy things
Read the rest
I'm missing out on. Having all your mail locally and in a hackable format inside Maildirs lets you do some pretty interesting stuff though. For example, here's a shell one-liner that generates a time series of my mail volume (gnuplot tail not included): https://twitter.com/alangrow/status/448965593564078080 [1] https://github.com/karelzak/mutt-kz
In Poll: How many emails do you have in your inbox right now?
I used sup for many years (and contributed some very minor patches). sup is no longer maintained and it's difficult to get running with ruby 1.9. Some good people that weren't happy with sup created notmuch (http://notmuchmail.org/) with similar goals. There is a mutt fork that uses morning called mutt-kz (https://github.com/karelzak/mutt-kz/wiki). I'm not as satisfied with mutt-kz as I was with sup, but it's probably even better if you have invested a lot of time configuring mutt just so.
In Introducing Outlook.com - Modern Email for the Next Billion Mailboxes

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.