From: apmanine@idaaas.com
To: Patrick Totzke <patricktotzke@gmail.com>,
"Jameson Graef Rollins" <jrollins@finestructure.net>,
notmuch@notmuchmail.org
Subject: Re: alot: can't read sent emails, after encryption
Date: Sun, 17 Nov 2013 21:51:43 +0100 [thread overview]
Message-ID: <20131117205143.15503.76684@localhost.localdomain> (raw)
In-Reply-To: <20131117185754.31928.60825@brick>
Quoting Patrick Totzke (2013-11-17 19:57:54)
> Quoting Jameson Graef Rollins (2013-11-16 21:47:02)
> > On Tue, Nov 12 2013, apmanine@idaaas.com wrote:
> > > I have recently switched to notmuch. Thank you for it!
> > > I'm using "alot" as a frontend (thank you for it, too!). Everything
> > > works smoothly, apart from one problem: with alot, I can't figure out how
> > > to read encrypted emails I previously sent: they appear to be encrypted
> > > using the addressee's key.
> > >
> > > Is there some way to store encrypted sent emails with my own public gpg
> > > key?
> >
> > What you really want is to tell gpg to always encrypt messages to your
> > personal key as well, which will always make them viewable by you. This
> > way you don't have to worry about saving unencrypted versions of the
> > message to disk, or there being two distinct versions of the message
> > (one encrypted to the recipient and a different one encrypted to you).
> >
> > See the "encrypt-to" gpg option [0].
> >
> > jamie.
> >
> > [0] http://www.gnupg.org/documentation/manuals/gnupg-devel/GPG-Key-related-Options.html
>
> Is this how notmuch emacs does it? I mean, is there some option to tell
> emacs to always call gpg with --encrypt-to=me ?
> I wonder if I need to change alot in any way or if one can simply globally configure
> gnupg.. alot does not call the gpg binary but uses pygpgme.
> cheers,
> /p
I didn't have time to test yet, but this thread suggest that
the --encrypt-to option is the recommended way for notmuch-emacs:
> 2. This is not necessarily related to notmuch itself but rather to
> message-mode: Why are the mails that are fcc'ed to my sent-folder
> encrypted with the recipient's key (instead of my own or simply no
> key)? I.e. why can't I read my own mails? Is there any way to make
> this work?
What about setting this on the gpg level with the "encrypt-to" option?
source: http://notmuch.198994.n3.nabble.com/Inline-encryption-encryption-failure-when-storing-sent-mails-td4028572.html
Alain-Pierre
prev parent reply other threads:[~2013-11-17 20:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 14:27 alot: can't read sent emails, after encryption apmanine
2013-11-12 23:01 ` Ruben Pollan
2013-11-13 7:49 ` apmanine
2013-11-16 20:47 ` Jameson Graef Rollins
2013-11-17 18:57 ` Patrick Totzke
2013-11-17 19:43 ` Jameson Graef Rollins
2013-11-18 7:38 ` Alain-Pierre Manine
2013-11-18 9:21 ` Patrick Totzke
2013-11-18 17:59 ` Jameson Graef Rollins
2013-11-18 13:17 ` Ruben Pollan
2013-11-18 15:52 ` Daniel Kahn Gillmor
2013-11-17 20:51 ` apmanine [this message]
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=20131117205143.15503.76684@localhost.localdomain \
--to=apmanine@idaaas.com \
--cc=jrollins@finestructure.net \
--cc=notmuch@notmuchmail.org \
--cc=patricktotzke@gmail.com \
/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).