* 2024-07-12 11:23:49+0200, Rainer Woitok wrote:

> While I agree in theory that the "MailDir" format is superior, this pro-
> bably would become the main show-stopper: I have zillions of "mbox" type
> mail folders  spread all over my  home directory  which I'd have to con-
> vert.  Well, I think a simple "gawk" script could do the trick, but this
> would have to be done in addition to the migration proper.

There is a tool for splitting mbox files: "formail -s".

> By the way, how does "NotMuch" choose the file names?

Notmuch doesn't name files at all. User just configures a directory
where the mails files or sub directories are. Notmuch doesn't
necessarily touch them other than opening and reading. Exception is
moving files between maildir subdirectories: usually from tmp/ to cur/
directory. Notmuch can also synchronize some maildir flags to Notmuch
tags: new, replied, flagged and probably some others.

> Is "POP3" supported?   Decades ago I opted for "POP3" because "IMAP" (at
> least then) was unable to do things the way I wanted them done. 

Notmuch doesn't do much: it doesn't do any internet protocols. It's
basically just a database and a command-line tool for that. Other tools
are needed, like "fetchmail" or some IMAP synchronizing tool for getting
the mail, Notmuch for indexing and searching the mail files, Notmuch
Emacs (or other client) for user interface and mail sending (SMTP).

Notmuch Emacs client can be configured to join the parts together but
user must write a "hook script" for getting the mail and putting the
files in the right place. The script could handle spam filtering, for
example. Mine uses "bogofilter" for spam and does some mail tagging like
adding "mute" or "follow" tags for mail I don't want or want to see.

So, from Notmuch and Notmuch Emacs user gets really nice tools for
building a custom mail system but they need other parts as well.

-- 
/// Teemu Likonen - .-.. https://www.iki.fi/tlikonen/
// OpenPGP: 6965F03973F0D4CA22B9410F0F2CAE0E07608462