From: Teemu Likonen <tlikonen@iki.fi>
To: Dr Rainer Woitok <rainer.woitok@gmail.com>, Jon Fineman <jon@fineman.me>
Cc: Help-Gnu-Emacs@Gnu.Org
Subject: Re: Is anybody using "NotMuch" as an email client?
Date: Fri, 12 Jul 2024 13:08:56 +0300 [thread overview]
Message-ID: <87ed7y9b2f.fsf@iki.fi> (raw)
In-Reply-To: <6690f627.050a0220.125f4.51f3@mx.google.com>
[-- Attachment #1: Type: text/plain, Size: 2050 bytes --]
* 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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 251 bytes --]
next prev parent reply other threads:[~2024-07-12 10:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-11 12:33 Is anybody using "NotMuch" as an email client? Dr Rainer Woitok
2024-07-11 13:35 ` Jon Fineman
2024-07-11 13:44 ` Joel Reicher
2024-07-12 9:23 ` Dr Rainer Woitok
2024-07-12 9:45 ` Jon Fineman
2024-07-12 10:08 ` Teemu Likonen [this message]
2024-07-12 18:08 ` Teemu Likonen
2024-07-13 23:46 ` Björn Bidar
2024-07-14 9:52 ` Andreas Eder
2024-07-14 17:25 ` Björn Bidar
2024-07-15 9:13 ` Is anybody using "NotMuch" as an email client?, " James Thomas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ed7y9b2f.fsf@iki.fi \
--to=tlikonen@iki.fi \
--cc=Help-Gnu-Emacs@Gnu.Org \
--cc=jon@fineman.me \
--cc=rainer.woitok@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).