From: Carl Worth <cworth@cworth.org>
To: Jameson Graef Rollins <jrollins@finestructure.net>,
notmuch@notmuchmail.org
Subject: Re: OpenPGP support
Date: Thu, 26 Nov 2009 10:41:36 -0800 [thread overview]
Message-ID: <87zl69qgbj.fsf@yoom.home.cworth.org> (raw)
In-Reply-To: <20091123130009.GA31695@finestructure.net>
On Mon, 23 Nov 2009 08:00:09 -0500, Jameson Graef Rollins <jrollins@finestructure.net> wrote:
> Hi, folks. I know it's a hairy problem, but has anyone started
> looking into OpenPGP support for notmuch?
I definitely want this.
I've got message-mode setup to sign my messages automatically when I
start a new compose from within notmuch with 'm'. I did this with the
following in my .emacs:
; sign messages by default
(add-hook 'message-setup-hook
(lambda ()
(mml-secure-message-sign)))
I'm not sure how to make sure that I also get that when doing a reply
within notmuch. Keith, I think you worked this out, right? What did you
do?
I'm also interested in automating things like this as much as
possible. I'd much rather people flip one Boolean notmuch-sign-messages
variable then have to code up multiple lambda's within .emacs.
Meanwhile, the other pieces still needed are automatic signature
verification for multipart/signed messages, and then support for
decrypting GPG-encrypted messages.
I'm certain that the various mail-handling modes within emacs already
have support for these things, so it's really just a matter of finding
and hooking into that support.
Of course, if we code some of this up at the library or command-line
level, then the non-emacs interfaces could automatically benefit from it
as well.
And that same argument applies for viewing of MIME-encoded message
parts---I definitely want support at the command-line interface of
notmuch to at least extract a specific MIME part from a message.
In one sense, it's unfortunate that I figured out a way to let me view
these parts within emacs without that support in the notmuch
command-line. That definitely took the pressure off me to finish up
coding this piece, (which actually wouldn't be hard at all).
-Carl
next prev parent reply other threads:[~2009-11-26 18:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-23 13:00 OpenPGP support Jameson Graef Rollins
2009-11-26 6:01 ` Jameson Graef Rollins
2009-11-26 7:08 ` Aneesh Kumar K. V
2009-11-26 18:31 ` Jameson Graef Rollins
2009-11-26 19:12 ` Carl Worth
2010-01-08 2:56 ` indexing encrypted messages (was: OpenPGP support) martin f krafft
2010-01-08 8:09 ` Mike Hommey
2010-01-08 9:12 ` martin f krafft
2010-01-08 9:21 ` Ruben Pollan
2010-01-08 10:24 ` martin f krafft
2010-01-08 19:41 ` micah anderson
2010-01-10 12:42 ` Ruben Pollan
2010-01-08 10:37 ` James Westby
2010-01-14 10:03 ` Olly Betts
2009-11-26 18:41 ` Carl Worth [this message]
2009-11-26 23:01 ` OpenPGP support Keith Packard
2009-11-28 4:06 ` Carl Worth
2009-11-29 19:44 ` Jameson Graef Rollins
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zl69qgbj.fsf@yoom.home.cworth.org \
--to=cworth@cworth.org \
--cc=jrollins@finestructure.net \
--cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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).