The design is extraordinarily elegant. It's almost like a purely functional email client. It never touches your messages. All it does is to alter a separate tag database. Then it's up to you how to turn tags into mailbox actions, like deleting or archiving emails. It sounds complicated, but it's trivial to setup and allows infinite flexibility in how to handle emails.
The Emacs interface is beautiful, quite similar to Magit. If Emacs is not your cup of tea, it's quite easy to use as a backend for Mutt. In fact, Neomutt already comes with Notmuch bundled and deeply integrated.
Is notmuch able to attach inline images from the clipboard, and render images in emails?
I have never attached inline images as I always compose plain text emails, so I don't know about that one.
However, I still find Mu and Notmuch TUIs quite different.
Why else use Mu?
(Looks like someone has done a minor comparison[2])
[2] https://old.reddit.com/r/emacs/comments/ebite6/mu4e_vs_gnus_...)
https://en.wikipedia.org/wiki/MH_Message_Handling_System
I'm just getting my ducks in a row for migrating to fully self-hosted e-mail and I have an idea of what I want but I'm not sure how best to achieve it. I have not yet fully settled on any part of the stack. What I want:
Catch-all e-mail addresses with dynamic filtering/folders based on address. For example, say I have the domain myemail.com. I'd like to be able to register at sketchysite.com with sketchysite@myemail.com. It should get filtered to its own inbox/folder. All these should be accessible from the same application/view/search space inside my e-mail client. I should not have to add new inboxes as they come and go (many will be ephemeral), either on client or server side.
By default, replying to an e-mail will always use the recipient address as the sender.
Has anybody set up something similar? Any particular client or server you would say is suitable/unsuitable?
Only hard requirements are FOSS, Linux, IMAP.