From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] [OT] Using mutt instead of kmail
Date: Sun, 8 Jan 2012 18:32:07 +0000 [thread overview]
Message-ID: <201201081832.18571.michaelkintzios@gmail.com> (raw)
[-- Attachment #1: Type: Text/Plain, Size: 2837 bytes --]
Hi All,
There are a few mutt users here so I thought of asking here first.
I've tried setting up mutt to use as a mail client instead of kmail.
Having spent some time now I am not sure it will do what I expect of a mail
client, at least not with the ease that I hoped.
The basic requirements for my typical use cases are to be able to handle
gpg/pgp and s/mime signed and occasionally encrypted messages and to auto-
complete addresses.
I have several different s/mime certificates and gpg keys for two different mail
accounts. Of course only one certificate for each account is valid at any time
(the others are expired or revoked) and only one gpg public/private key pair.
However, the old keys are still necessary and available in my system to be
able to decrypt old emails that I have received over the years.
With kmail I do not have to specify gpg keys, or certificate IDs, to be able to
decrypt messages. The mail client itself reads the key/certificate and calls
gpgsm/kgpg which asks for my passphrase.
Also, when I want to send an encrypted message it knows from the Crypto
settings of the recipient in the Address Book which public key/certificate to
use to encrypt a message. if the recipient has both gpg and s/mime
certificates available in the Address Book it asks me which to use on each
occasion.
Finally, kmail has an auto-completion feature for the recipient address and it
suggests as I type the person to send to. Down arrow and enter is all that I
need to press.
Unlike kmail, with mutt I can't even start using certificates because I am
getting errors importing SSL certs like these:
3075245704:error:0D0680A8:asn1 encoding routines:ASN1_CHECK_TLEN:wrong
tag:tasn_dec.c:1319:
3075245704:error:0D07803A:asn1 encoding routines:ASN1_ITEM_EX_D2I:nested asn1
error:tasn_dec.c:381:Type=PKCS12
Mutt asks for s/mime ID Nos, on each message, which with the number of
certificates that I have amassed over the years I do not happen to have at hand
and it is a pain to type manually each time.
Mutt also does not seem to auto-complete any addresses. It uses aliases, but
that implies that I must set up such aliases and use these every time I want
to enter a particular address. This creates the problem of having to remember
each and every alias, rather than typing "fre" and getting a list of Freds,
Freddies, Frederics, etc. or part of the Surname, or part of the email
address itself.
The other difficulty is the key shortcuts in mutt do not behave as I would like
them to, but this is that something I could recode so less of a problem.
Is there anything that I could do to automate the digital signing and
encryption to a level similar to kmail and the auto-completion of email
addresses?
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2012-01-08 18:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-08 18:32 Mick [this message]
2012-01-09 0:48 ` [gentoo-user] [OT] Using mutt instead of kmail Walter Dnes
2012-01-09 3:17 ` Frank Steinmetzger
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201201081832.18571.michaelkintzios@gmail.com \
--to=michaelkintzios@gmail.com \
--cc=gentoo-user@lists.gentoo.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