From: Gregor Zattler <telegraph@gmx.net>
To: notmuch <notmuch@notmuchmail.org>
Subject: Re: Emacs: Crypto: How to get automatic encryption?
Date: Thu, 12 Jan 2012 20:05:14 +0100 [thread overview]
Message-ID: <20120112190514.GA15301@shi.workgroup> (raw)
In-Reply-To: <87k44wlq5g.fsf@servo.finestructure.net>
Hi Jameson,
* Jameson Graef Rollins <jrollins@finestructure.net> [12. Jan. 2012]:
> On Tue, 03 Jan 2012 13:45:14 -0800, Jameson Graef Rollins <jrollins@finestructure.net> wrote:
>> Unfortunately, auto encrypting of replies to encrypted emails is not yet
>> implemented. It is desperately needed, though, obviously. So this is a
>> good excuse to start a discussion about how we could achieve this.
[...]
> There is a set of patches in the queue to add a JSON output format for
> reply, with the emacs UI then consuming that to construct the reply
> template [0]. This will make it very easy to communicate to the emacs
> UI that the original message was encrypted, and that the reply should be
> similarly encrypted. I'm going to wait until that patch set makes it
> through, and then build this functionality on top of that.
> [0] id:"1326009162-19524-3-git-send-email-awg+notmuch@xvx.ca"
That would be really great.
But how about not only replying encrypted but encrypting every
email if possible? "Possible" could mean different things,
though:
1) encrypt if fully trusted suitable public keys for all
recipients are GnuPG key ring.
2) encrypt if suitable public keys for all recipients are in
GnuPGs key ring.
3) try to fetch suitable public keys from server in order to to
check 2).
I for instance fiddled with my mutt configuration to achieve 1).
But I have no clue about how to do this with notmuch/Emacs.
Ciao, Gregor
--
-... --- .-. . -.. ..--.. ...-.-
next prev parent reply other threads:[~2012-01-12 19:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 19:56 Emacs: Crypto: How to get automatic encryption? Gregor Zattler
2012-01-03 21:45 ` Jameson Graef Rollins
2012-01-04 0:08 ` Gregor Zattler
2012-01-04 8:36 ` David Edmondson
2012-01-04 8:48 ` David Edmondson
2012-01-15 22:27 ` Gregor Zattler
2012-01-17 4:48 ` Antoine Beaupré
2012-01-17 9:19 ` David Edmondson
2012-01-17 16:12 ` Antoine Beaupré
2012-01-24 21:34 ` micah anderson
2012-01-25 0:10 ` Jameson Graef Rollins
2012-01-25 6:23 ` David Edmondson
2012-01-25 9:26 ` Jameson Graef Rollins
2012-01-25 10:20 ` David Edmondson
2012-01-25 17:45 ` Jameson Graef Rollins
2012-01-25 19:09 ` Daniel Kahn Gillmor
2012-01-26 8:53 ` David Edmondson
2012-01-17 15:39 ` David Edmondson
2012-01-12 18:41 ` Jameson Graef Rollins
2012-01-12 19:05 ` Gregor Zattler [this message]
2012-01-12 19:28 ` Jameson Graef Rollins
2012-01-12 19:29 ` Darren McGuicken
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=20120112190514.GA15301@shi.workgroup \
--to=telegraph@gmx.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).