alot: can't read sent emails, after encryption

[Ruben Pollan]

Quoting Jameson Graef Rollins (2013-11-17 20:43:25)
> On Sun, Nov 17 2013, Patrick Totzke  wrote:
> > 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.
> 
> You do not need to change alot, just notmuch emacs also doesn't need to
> do anything special to allow for this.  Just add an
> 
> encrypt-to 
> 
> line to your ~/.gnupg/gpg.conf, where  is your personal keyid.
> Then all encrypted data is also encrypted to your personal key, making
> it always viewable by you as well.  Then you can just open your
> encrypted sent mail as you would any other encrypted mail.

If I have to identities, with two different gpg keys (key1 and key2), and I set 
'encrypt-to key1' when I send emails with my identity of key2 it will also 
encrypt it with my key1 and will reveal to its receivers that I own key1. Isn't 
it?


-- 
Ruben Pollan  | http://meskio.net/
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
 My contact info: http://meskio.net/crypto.txt
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Nos vamos a Croatan.
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: signature
URL: 

alot: can't read sent emails, after encryption

[Patrick Totzke]

Quoting Alain-Pierre Manine (2013-11-18 08:38:33)
> Quoting Jameson Graef Rollins (2013-11-17 20:43:25)
> > On Sun, Nov 17 2013, Patrick Totzke  wrote:
> > > Quoting Jameson Graef Rollins (2013-11-16 21:47:02)
> > >> On Tue, Nov 12 2013, apmanine at 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.
> > 
> > You do not need to change alot, just notmuch emacs also doesn't need to
> > do anything special to allow for this.  Just add an
> > 
> > encrypt-to 
> > 
> > line to your ~/.gnupg/gpg.conf, where  is your personal keyid.
> > Then all encrypted data is also encrypted to your personal key, making
> > it always viewable by you as well.  Then you can just open your
> > encrypted sent mail as you would any other encrypted mail.
> > 
> > jamie.
> 
> It's working! Thanks for the explanations.


Excelent, thanks Jamie.
I wasn't aware of this setting and assumed that the stuff in the
gnupg config file only applies to gpg itself and not, as in alot,
for calls through the gpgme library.
Thanks for testing this Alain-Pierre.
/p
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: signature
URL: 

alot: can't read sent emails, after encryption

[Jameson Graef Rollins]

On Mon, Nov 18 2013, Patrick Totzke  wrote:
> Excelent, thanks Jamie.
> I wasn't aware of this setting and assumed that the stuff in the
> gnupg config file only applies to gpg itself and not, as in alot,
> for calls through the gpgme library.

Actually, bizarrely, there is no actual gpg library.  gpgme just calls
the gpg binary underneath.  Therefore all gpg settings work for gpgme as
well.

jamie.
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: 

alot: can't read sent emails, after encryption

[Alain-Pierre Manine]

Quoting Jameson Graef Rollins (2013-11-17 20:43:25)
> On Sun, Nov 17 2013, Patrick Totzke  wrote:
> > Quoting Jameson Graef Rollins (2013-11-16 21:47:02)
> >> On Tue, Nov 12 2013, apmanine at 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.
> 
> You do not need to change alot, just notmuch emacs also doesn't need to
> do anything special to allow for this.  Just add an
> 
> encrypt-to 
> 
> line to your ~/.gnupg/gpg.conf, where  is your personal keyid.
> Then all encrypted data is also encrypted to your personal key, making
> it always viewable by you as well.  Then you can just open your
> encrypted sent mail as you would any other encrypted mail.
> 
> jamie.

It's working! Thanks for the explanations.

alot: can't read sent emails, after encryption

[Daniel Kahn Gillmor]

On 11/18/2013 05:17 AM, Ruben Pollan wrote:
> If I have t[w]o identities, with two different gpg keys (key1 and key2), and 
> I set 
> 'encrypt-to key1' when I send emails with my identity of key2 it will also 
> encrypt it with my key1 and will reveal to its receivers that I own key1. 
> Isn't 
> it?

It won't formally *prove* that you own key1 (no one will be able to say
for sure that the public key encrypted session key packet actually is
decryptable by key1, it just has the 64-bit keyid embedded in the PKESK,
and even if it did, it could arguably have been added as a Bcc: to
another independent person), but it will certainly imply to anyone who
gets more than a single message from you that there is this other key
involved somehow.

If you have multiple identities, there are other approaches you could
take without changing alot itself, for example:

You could have two separate ~/.gnupg directories, and you could launch
alot differently, with "GNUPGHOME=~/.gnupg-key1 alot" or
"GNUPGHOME=~/.gnupg-key2 alot" to make these responses.

If you really care deeply about keeping the identities distinct, you
might even want to split your notmuch dataset into two places as well,
so that you don't accidentally reply from one identity to another
identity's message:

 NOTMUCH_CONFIG=~/.notmuch-config-key1 GNUPGHOME=~/.gnupg-key1 alot

and so forth.

or you could use two distinct user accounts or virtual machines so that
the data as even fewer possibilities of being mixed (e.g. ensuring that
the outbound SMTP path, and/or the message-IDs generated when sending
each message don't share any features that might leak their common
provenance).

None of this is particularly convenient; maintaining separate identities
that are difficult for an adversary to re-correlate is a serious challenge.

That said, i can imagine that alot (and other notmuch frontends) could
be improved to support this use case directly without forcing users to
go through the extra hoops i've envisioned above.

--dkg

-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 1027 bytes
Desc: OpenPGP digital signature
URL: 

Re: alot: can't read sent emails, after encryption

[Patrick Totzke]

Quoting Alain-Pierre Manine (2013-11-18 08:38:33)
 Quoting Jameson Graef Rollins (2013-11-17 20:43:25)
  On Sun, Nov 17 2013, Patrick Totzke patricktot...@gmail.com wrote:
   Quoting Jameson Graef Rollins (2013-11-16 21:47:02)
   On Tue, Nov 12 2013, apman...@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.
  
  You do not need to change alot, just notmuch emacs also doesn't need to
  do anything special to allow for this.  Just add an
  
  encrypt-to keyid
  
  line to your ~/.gnupg/gpg.conf, where keyid is your personal keyid.
  Then all encrypted data is also encrypted to your personal key, making
  it always viewable by you as well.  Then you can just open your
  encrypted sent mail as you would any other encrypted mail.
  
  jamie.
 
 It's working! Thanks for the explanations.


Excelent, thanks Jamie.
I wasn't aware of this setting and assumed that the stuff in the
gnupg config file only applies to gpg itself and not, as in alot,
for calls through the gpgme library.
Thanks for testing this Alain-Pierre.
/p


signature.asc
Description: signature
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch

Re: alot: can't read sent emails, after encryption

[Ruben Pollan]

Quoting Jameson Graef Rollins (2013-11-17 20:43:25)
 On Sun, Nov 17 2013, Patrick Totzke patricktot...@gmail.com wrote:
  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.
 
 You do not need to change alot, just notmuch emacs also doesn't need to
 do anything special to allow for this.  Just add an
 
 encrypt-to keyid
 
 line to your ~/.gnupg/gpg.conf, where keyid is your personal keyid.
 Then all encrypted data is also encrypted to your personal key, making
 it always viewable by you as well.  Then you can just open your
 encrypted sent mail as you would any other encrypted mail.

If I have to identities, with two different gpg keys (key1 and key2), and I set 
'encrypt-to key1' when I send emails with my identity of key2 it will also 
encrypt it with my key1 and will reveal to its receivers that I own key1. Isn't 
it?


-- 
Ruben Pollan  | http://meskio.net/
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
 My contact info: http://meskio.net/crypto.txt
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Nos vamos a Croatan.


signature.asc
Description: signature
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch

Re: alot: can't read sent emails, after encryption

[Daniel Kahn Gillmor]

On 11/18/2013 05:17 AM, Ruben Pollan wrote:
 If I have t[w]o identities, with two different gpg keys (key1 and key2), and 
 I set 
 'encrypt-to key1' when I send emails with my identity of key2 it will also 
 encrypt it with my key1 and will reveal to its receivers that I own key1. 
 Isn't 
 it?

It won't formally *prove* that you own key1 (no one will be able to say
for sure that the public key encrypted session key packet actually is
decryptable by key1, it just has the 64-bit keyid embedded in the PKESK,
and even if it did, it could arguably have been added as a Bcc: to
another independent person), but it will certainly imply to anyone who
gets more than a single message from you that there is this other key
involved somehow.

If you have multiple identities, there are other approaches you could
take without changing alot itself, for example:

You could have two separate ~/.gnupg directories, and you could launch
alot differently, with GNUPGHOME=~/.gnupg-key1 alot or
GNUPGHOME=~/.gnupg-key2 alot to make these responses.

If you really care deeply about keeping the identities distinct, you
might even want to split your notmuch dataset into two places as well,
so that you don't accidentally reply from one identity to another
identity's message:

 NOTMUCH_CONFIG=~/.notmuch-config-key1 GNUPGHOME=~/.gnupg-key1 alot

and so forth.

or you could use two distinct user accounts or virtual machines so that
the data as even fewer possibilities of being mixed (e.g. ensuring that
the outbound SMTP path, and/or the message-IDs generated when sending
each message don't share any features that might leak their common
provenance).

None of this is particularly convenient; maintaining separate identities
that are difficult for an adversary to re-correlate is a serious challenge.

That said, i can imagine that alot (and other notmuch frontends) could
be improved to support this use case directly without forcing users to
go through the extra hoops i've envisioned above.

--dkg



signature.asc
Description: OpenPGP digital signature
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch

Re: alot: can't read sent emails, after encryption

[Jameson Graef Rollins]

On Mon, Nov 18 2013, Patrick Totzke patricktot...@gmail.com wrote:
 Excelent, thanks Jamie.
 I wasn't aware of this setting and assumed that the stuff in the
 gnupg config file only applies to gpg itself and not, as in alot,
 for calls through the gpgme library.

Actually, bizarrely, there is no actual gpg library.  gpgme just calls
the gpg binary underneath.  Therefore all gpg settings work for gpgme as
well.

jamie.


pgpCf2XT8bChV.pgp
Description: PGP signature
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch

alot: can't read sent emails, after encryption

[apman...@idaaas.com]

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 at 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

alot: can't read sent emails, after encryption

[Patrick Totzke]

Quoting Jameson Graef Rollins (2013-11-16 21:47:02)
> On Tue, Nov 12 2013, apmanine at 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
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: signature
URL: 

alot: can't read sent emails, after encryption

[Jameson Graef Rollins]

On Sun, Nov 17 2013, Patrick Totzke  wrote:
> Quoting Jameson Graef Rollins (2013-11-16 21:47:02)
>> On Tue, Nov 12 2013, apmanine at 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.

You do not need to change alot, just notmuch emacs also doesn't need to
do anything special to allow for this.  Just add an

encrypt-to 

line to your ~/.gnupg/gpg.conf, where  is your personal keyid.
Then all encrypted data is also encrypted to your personal key, making
it always viewable by you as well.  Then you can just open your
encrypted sent mail as you would any other encrypted mail.

jamie.
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: 

Re: alot: can't read sent emails, after encryption

[Patrick Totzke]

Quoting Jameson Graef Rollins (2013-11-16 21:47:02)
 On Tue, Nov 12 2013, apman...@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


signature.asc
Description: signature
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch

Re: alot: can't read sent emails, after encryption

[apmanine]

Quoting Patrick Totzke (2013-11-17 19:57:54)
 Quoting Jameson Graef Rollins (2013-11-16 21:47:02)
  On Tue, Nov 12 2013, apman...@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
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch

Re: alot: can't read sent emails, after encryption

[Alain-Pierre Manine]

Quoting Jameson Graef Rollins (2013-11-17 20:43:25)
 On Sun, Nov 17 2013, Patrick Totzke patricktot...@gmail.com wrote:
  Quoting Jameson Graef Rollins (2013-11-16 21:47:02)
  On Tue, Nov 12 2013, apman...@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.
 
 You do not need to change alot, just notmuch emacs also doesn't need to
 do anything special to allow for this.  Just add an
 
 encrypt-to keyid
 
 line to your ~/.gnupg/gpg.conf, where keyid is your personal keyid.
 Then all encrypted data is also encrypted to your personal key, making
 it always viewable by you as well.  Then you can just open your
 encrypted sent mail as you would any other encrypted mail.
 
 jamie.

It's working! Thanks for the explanations.


___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch

alot: can't read sent emails, after encryption

[Jameson Graef Rollins]

On Tue, Nov 12 2013, apmanine at 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
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: 

Re: alot: can't read sent emails, after encryption

[Jameson Graef Rollins]

On Tue, Nov 12 2013, apman...@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


pgpLrxyGbIk1J.pgp
Description: PGP signature
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch

alot: can't read sent emails, after encryption

[apman...@idaaas.com]

Quoting Ruben Pollan (2013-11-13 00:01:21)
> 
> Same problem here, I think what is stored is the email that was send. It will 
> be 
> great if alot stores it as you say with your own public gpg key.
> 
> I think we should open an issue about in the alot github tracker:
> https://github.com/pazz/alot/issues
> Can you do it?

Thank you for your answer.
I'm going to open an issue.


Alain-Pierre

alot: can't read sent emails, after encryption

[Ruben Pollan]

Quoting apmanine at idaaas.com (2013-11-12 15:27:42)
> 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?

Same problem here, I think what is stored is the email that was send. It will 
be 
great if alot stores it as you say with your own public gpg key.

I think we should open an issue about in the alot github tracker:
https://github.com/pazz/alot/issues
Can you do it?


-- 
Ruben Pollan  | http://meskio.net/
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
 My contact info: http://meskio.net/crypto.txt
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Nos vamos a Croatan.
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: signature
URL: 

alot: can't read sent emails, after encryption

[apman...@idaaas.com]

Hi,

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?

Thanks,

Alain-Pierre

alot: can't read sent emails, after encryption

[apmanine]

Hi,

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?

Thanks,

Alain-Pierre


___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch

Re: alot: can't read sent emails, after encryption

[Ruben Pollan]

Quoting apman...@idaaas.com (2013-11-12 15:27:42)
 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?

Same problem here, I think what is stored is the email that was send. It will 
be 
great if alot stores it as you say with your own public gpg key.

I think we should open an issue about in the alot github tracker:
https://github.com/pazz/alot/issues
Can you do it?


-- 
Ruben Pollan  | http://meskio.net/
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
 My contact info: http://meskio.net/crypto.txt
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Nos vamos a Croatan.


signature.asc
Description: signature
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch

Re: alot: can't read sent emails, after encryption

[apmanine]

Quoting Ruben Pollan (2013-11-13 00:01:21)
 
 Same problem here, I think what is stored is the email that was send. It will 
 be 
 great if alot stores it as you say with your own public gpg key.
 
 I think we should open an issue about in the alot github tracker:
 https://github.com/pazz/alot/issues
 Can you do it?

Thank you for your answer.
I'm going to open an issue.


Alain-Pierre
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch