Posted Jun 17, 2004 7:11 UTC (Thu) by larryr
Parent article: The Grumpy Editor's guide to mail clients: introduction
I do not have a mail client I feel ready to commit to. I have been
keeping my eye out for something which conforms to my idea of
- Standalone Application(s).
- Feature rich and configuration/interoperability friendly.
- Substantial user/developer base.
- GPL, BSD, or similar license.
- Runs on Linux/Solaris/OSX and Windows (natively or via Cygwin).
- Likely to be updated and improving for years to come.
And of the maybe a dozen which satisfy a few of those, I only
feel these are at all auspicious:
I left out Evolution because I expect it to at some point
in the not too distant future to be orphaned and not have
a community developer base to update/improve it.
Currently for my main mail handling I use standalone
programs to pull mail into Maildirs (mutt as simply a
fetchmail equivalent because I hate fetchmail), send message files (qmail-inject), view and
compose simple plain text email (vim), view HTML emails
(lynx -stdin -dump). For MIME
encoded messages I may use mimencode to unencode base64 or
quoted-printable messages, or munpack/mpack to split/join a multipart
message into its constituent parts. Of course to make this
approach efficient requires some scripting, it is not a
complete outofthebox solution to just use these programs.
To peruse my new mail, I use mutt in readonly mode. If I
want to search, I can use find, grep, xargs, etc, and produce
as output a list of filenames which I can then link to from
a temporary Maildir with symbolic links to the files which
matched, so the search results are just a plain Maildir as much as anything else, and I can just "rm -r" when I am done with them.
to post comments)