From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: David Bremner <david@tethera.net>,
Jameson Graef Rollins <jrollins@finestructure.net>,
Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: decryption error for signed+encrypted messages
Date: Mon, 06 May 2019 17:09:54 -0400 [thread overview]
Message-ID: <875zqnmgrh.fsf@fifthhorseman.net> (raw)
In-Reply-To: <87eh3yrf84.fsf@zancas.localnet>
[-- Attachment #1: Type: text/plain, Size: 473 bytes --]
blast from the past (cleaning up the bugtracker a bit).
On Thu 2014-01-23 09:37:47 -0400, David Bremner wrote:
> This bug seems to be (some time ago) marked fixed upstream
>
> https://bugzilla.gnome.org/show_bug.cgi?id=677088
This was definitely a bug in gmime, and it was resolved by gmime moving
entirely to gpgme. I've cleared the notmuch::moreinfo tag on this
report and added notmuch::fixed (even though it was not notmuch which
did the fixing.
--dkg
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
prev parent reply other threads:[~2019-05-06 21:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-04 18:00 decryption error for signed+encrypted messages Jameson Graef Rollins
2014-01-23 13:37 ` David Bremner
2019-05-06 21:09 ` Daniel Kahn Gillmor [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=875zqnmgrh.fsf@fifthhorseman.net \
--to=dkg@fifthhorseman.net \
--cc=david@tethera.net \
--cc=jrollins@finestructure.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).