From: David Bremner <david@tethera.net>
To: Simon Hirscher <public@simonhirscher.de>, notmuch@notmuchmail.org
Subject: Re: Inline-encryption, encryption failure when storing sent mails
Date: Fri, 16 Aug 2013 10:02:27 +0200 [thread overview]
Message-ID: <878v02ysfg.fsf@maritornes.cs.unb.ca> (raw)
In-Reply-To: <CAEj42wtJzxjQKCMQKZ3354oEnW5+McxvzLaM4q9Yx19nR6H_mQ@mail.gmail.com>
Simon Hirscher <public@simonhirscher.de> writes:
> Hey there,
>
> I'm quite new to notmuch and have two questions regarding the state of
> mail encryption:
>
> 1. Support for inline-encryption As far as I can see, so far only
> encrypted mails with PGP/MIME are supported. Couldn't notmuch also
> support text/plain messages that contain PGP-encrypted messages by
> scanning for "^-----BEGIN\ PGP\ (SIGNED\ )?MESSAGE"? – as suggested in
> a previous message to this mailing list
> (id:87zl3az8mm.fsf@lillypad.riseup.net; web view:
If someone feels inspired to work on this, maybe
notmuch-wash-convert-inline-patch-to-part
(in notmuch-watch.el) might be a reasonable place to start.
> 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?
Setting the emacs variable mml2015-encrypt-to-self seems like it ought
to work, but it seems to need some other settings as well. Perhaps have
a look at the customization group 'mime-security'.
d
next prev parent reply other threads:[~2013-08-16 8:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-12 16:57 Inline-encryption, encryption failure when storing sent mails Simon Hirscher
2013-08-16 8:02 ` David Bremner [this message]
2013-08-16 11:32 ` Simon Hirscher
2013-08-20 17:03 ` Daniel Kahn Gillmor
2014-02-18 18:31 ` Daniel Kahn Gillmor
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=878v02ysfg.fsf@maritornes.cs.unb.ca \
--to=david@tethera.net \
--cc=notmuch@notmuchmail.org \
--cc=public@simonhirscher.de \
/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).