Return-Path: X-Original-To: notmuch@notmuchmail.org Delivered-To: notmuch@notmuchmail.org Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 6D6AC431FC2 for ; Fri, 16 Aug 2013 01:02:41 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none] autolearn=disabled Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BOmNG7DTTLUc for ; Fri, 16 Aug 2013 01:02:36 -0700 (PDT) Received: from yantan.tethera.net (yantan.tethera.net [199.188.72.155]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id B0D23431FAF for ; Fri, 16 Aug 2013 01:02:36 -0700 (PDT) Received: from remotemail by yantan.tethera.net with local (Exim 4.80) (envelope-from ) id 1VAEzR-0007FA-4h; Fri, 16 Aug 2013 05:02:33 -0300 Received: (nullmailer pid 29721 invoked by uid 1000); Fri, 16 Aug 2013 08:02:27 -0000 From: David Bremner To: Simon Hirscher , notmuch@notmuchmail.org Subject: Re: Inline-encryption, encryption failure when storing sent mails In-Reply-To: References: User-Agent: Notmuch/0.16 (http://notmuchmail.org) Emacs/24.3.1 (x86_64-pc-linux-gnu) Date: Fri, 16 Aug 2013 10:02:27 +0200 Message-ID: <878v02ysfg.fsf@maritornes.cs.unb.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Aug 2013 08:02:41 -0000 Simon Hirscher 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"? =E2=80=93 as suggest= ed 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=20 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