From: Milan Glacier <news@milanglacier.com>
To: Gottfried <gottfried@posteo.de>
Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: package for Email
Date: Wed, 18 Jan 2023 13:03:48 -0500 [thread overview]
Message-ID: <20230118180348.gzwvy6iztok45ko3@zoho.com> (raw)
In-Reply-To: <f2f6c7ae-dfc1-6761-bede-42290f517cae@posteo.de>
On 01/18/23 13:56, Gottfried wrote:
>Hi everybody,
>
>I am using thunderbird for emails.
>My question:
>
>1. Which Email package do you use?
>Can you tell your experience with your email package?
I have experience with 3 email clients, mu4e, notmuch, and neomutt.
My personal experience suggests that overall I like neomutt best, but
the others have their own merits. And all of them they are very good.
YMMV.
>
>2. Does it make sense for me as an emacs-newbie to change from using
>thunderbird to an emacs email package?
It depends on your usage. If you use emails primarily just for reading
HTML emails from advertisement. Then no. But other than that, yes.
>3. There are
>Rmail, GNU, Wanderlust, Mu4e etc...
>
>4. I prefer to habe folders because I like to have an overview.
>Mu4e doesn't have folders.
What do you mean by "mu4e doesn't have folders"? Mu4e can read emails
from folders ad move emails between folders. What else do you need?
>
>5. I want IMAP.
>Do all of them provide IMAP? (does Rmail now provide IMAP)?
You probably need offlienimap or isync(mbsync) as a mail synchronization
(fetch emails from server and push local changes to the server) backend.
All of notmuch, mu4e, and neomutt are just just frontends that
read/change your local maildir.
>6. Wanderlust seems to be more difficult to set up, and I still have
>trouble because I am an Emacs-newbie.
I don't use wanderlust but I have read some other's feedback. They
suggests that wanderlust is implemented in pure elisp and has very fast
IMAP sync speed (in comparison with Gnus). If you are using Windows
where mbsync is not possible to use. Then wanderlust may be a good
choice.
As for configuration, yes, the configuration syntax for wanderlust is a
bit complex, it uses DSL rather than elisp to configure.
>7. Which one is easier to use?
Notmuch, neomutt, and mu4e are all easy to use. LMO. But again YMMV. My
personal configuration steps include:
- configure mbsync to fetch/push emails changes.
- configure msmtp to send emails.
- configure mu4e/neomutt/notmuch to read the local maildirs.
>8. Should I start with Rmail? and later switch to GNU?
>
>At the moment I don't need GNU for reading news etc...
>
>9. Or is it useful to start with GNU because it has more options and I
>have to learn it anyhow? and I can use it with org-mode?
>
>10. Do all of them have the same or similar keybindings or do I have
>to learn for each one separate keybindings?
I don't use gnus.
>11. What are the benefits compared to thunderbird?
>A. Only the keybindings of Emacs I can use and in knowing them it will
> be easier in future to handle it?
>B. It is within emacs and uses less CPU
>C......
I don't use thunderbird. But emacs/cli based emails clients generally
have common merits over GUI client:
- They are keyboard centric.
- You can manipulate emails buffers just like normal text buffers.
- Integration with other emacs facilities like orgmode, pdftools,
xwidget stuff.
- They offer you more flexible and powerful way to manipulate, search
and index your emails.
Let me show my feedback on all of three emails client I used:
* Neomutt
- It is a standalone cli app. You can use emacs to compose your emails
and use emacs to read/edit your inbox emails with some very simple
configuration.
- It is folder-based.
- It has pretty decent integration with notmuch (that is: you can index
your emails efficiently).
- It can fold threads, which is very useful for reading mailing list.
- When reading HTML emails (especailly advertisement emails), typically
you do two steps:
+ using w3m/lynx like terminal based termianl to dump the renderd HTML
emails into text. And neomutt shows you the text in the reading
page. And for advertisement emails, w3m/lynx generally gives you
rendered output that is not ideal.
+ If you are not satisfied with the rendered plain text by w3m/lynx,
you can directly open the HTML using your GUI browser in neomutt
(two keystrokes "v RET").
* mu4e
- It has decent integration with orgmode. (store links to email in
orgmode, open email links in orgmode, and compose html emails by
orgmode).
- It **can't** fold threads. If you are reading mailing list, you
probably will get overwhelmed by the incoming flood of emails. This is
the only cons I have with mu4e.
- It renders html emails pretty decent (Say thanks to shr.el). In case
you are not satisfied, you can also open the HTML emails by GUI
browser or even emacs' xwidget.
* notmuch
- It has a conversation view (show all emails within a thread in one
text buffer).
- HTML emails rendering is decent (also say thanks to shr.el).
- It cannot **manipulate** emails. That is: notmuch doesn't provide you
an official way to delete emails and move emails between folders.
However you can do that with some "hack" scripts.
>
>Kind regards
>
>Gottfried
>
next prev parent reply other threads:[~2023-01-18 18:03 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 13:56 package for Email Gottfried
2023-01-18 14:44 ` Eric Brown
2023-01-18 15:15 ` Jean Louis
2023-01-19 7:31 ` Tomas Hlavaty
2023-01-19 7:55 ` Jean Louis
2023-01-18 15:51 ` Tassilo Horn
2023-01-18 17:17 ` Eli Zaretskii
2023-01-18 17:58 ` andrés ramírez
2023-01-19 3:55 ` Jean Louis
2023-01-18 16:28 ` Andreas Eder
2023-01-18 18:03 ` Milan Glacier [this message]
2023-01-19 4:02 ` Jean Louis
2023-01-19 5:06 ` Debunking Emacs merits over GUI - " Jean Louis
2023-01-19 5:41 ` Emanuel Berg
2023-01-19 13:00 ` Jean Louis
2023-01-19 15:34 ` Marcin Borkowski
2023-01-20 8:27 ` Jean Louis
2023-01-19 16:10 ` Milan Glacier
2023-01-19 16:52 ` Jude DaShiell
2023-01-20 9:32 ` Jean Louis
2023-01-19 21:10 ` Bob Newell
2023-01-20 9:47 ` Jean Louis
[not found] ` <877cxgrc3e.mmmtqrm@thhcbmmmd.mijofcrcc.org>
2023-01-21 7:05 ` Jean Louis
2023-01-21 7:20 ` Emanuel Berg
2023-01-21 7:21 ` Eli Zaretskii
2023-01-21 7:28 ` Emanuel Berg
2023-01-21 14:29 ` Jean Louis
2023-01-21 14:28 ` Jean Louis
2023-01-21 15:31 ` Eli Zaretskii
2023-01-21 17:30 ` Bob Newell
2023-01-22 15:40 ` Jean Louis
2023-01-20 9:07 ` Jean Louis
2023-01-20 15:52 ` Milan Glacier
2023-01-21 6:04 ` History " David Masterson
2023-01-21 7:10 ` Eli Zaretskii
2023-01-21 7:21 ` Emanuel Berg
2023-01-21 7:34 ` tomas
2023-01-21 17:38 ` Bob Newell
2023-01-22 3:16 ` David Masterson
2023-01-22 15:48 ` Jean Louis
2023-01-22 3:08 ` David Masterson
2023-01-22 6:23 ` Eli Zaretskii
2023-01-22 19:33 ` David Masterson
2023-01-22 19:57 ` Eli Zaretskii
2023-01-22 7:45 ` Po Lu
2023-01-22 19:35 ` David Masterson
2023-01-21 14:35 ` Jean Louis
2023-01-22 3:33 ` David Masterson
2023-03-10 17:16 ` Emanuel Berg
2023-03-13 8:32 ` Po Lu
2023-01-18 18:10 ` Filipp Gunbin
2023-01-19 2:15 ` Emanuel Berg
2023-01-19 12:40 ` Jean Louis
2023-01-19 14:10 ` Martin Steffen
2023-01-19 16:20 ` Eric S Fraga
2023-01-19 16:39 ` Jude DaShiell
2023-01-20 10:05 ` Jean Louis
2023-01-19 17:00 ` Leo Butler
2023-01-19 17:35 ` Eric S Fraga
2023-01-20 6:48 ` Milan Glacier
2023-01-19 3:53 ` Jean Louis
2023-01-19 6:08 ` John Haman
2023-01-19 11:52 ` Emanuel Berg
2023-01-21 13:57 ` Jean Louis
2023-01-21 15:08 ` Jude DaShiell
2023-01-21 17:47 ` Bob Newell
2023-01-22 3:46 ` David Masterson
2023-01-22 19:52 ` Bob Newell
2023-01-22 3:34 ` David Masterson
2023-01-31 5:46 ` Emanuel Berg
2023-01-20 4:09 ` Milan Glacier
2023-01-20 7:31 ` Emanuel Berg
2023-01-20 10:26 ` Jean Louis
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=20230118180348.gzwvy6iztok45ko3@zoho.com \
--to=news@milanglacier.com \
--cc=gottfried@posteo.de \
--cc=help-gnu-emacs@gnu.org \
/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).