From: Nils Gillmann <niasterisk@grrlz.net>
To: info-gnus-english@gnu.org
Subject: possible emacs 24.5 + Gnus problem when using pgpmime and signencrypt (was: Re: Trouble with GnuPG 2.1)
Date: Mon, 14 Mar 2016 17:55:55 +0100 [thread overview]
Message-ID: <8760wp6lt0.fsf_-_@grrlz.net> (raw)
In-Reply-To: <8737rub177.fsf@grrlz.net>
So it looks like this problem occurs when I try to /signencrypt/
and it works when I just ignore the fact that I can't sign.
Untested:
- just sign and not encrypt
It is not necessarily Gnus related, but appears to me in the
context of using Gnus.
Sources to get a 2016 relevant default of a working config for
gpg with epa are too many and too many outdated, so it's hard to
get this working, but this is progress.
--
ng
personal contact: http://krosos.sdf.org
EDN: https://wiki.c3d2.de/Echt_Dezentrales_Netz/en
next prev parent reply other threads:[~2016-03-14 16:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-13 15:16 Trouble with GnuPG 2.1 Nils Gillmann
2016-03-13 15:48 ` Jens Lechtenboerger
2016-03-13 16:21 ` Nils Gillmann
2016-03-13 17:17 ` Jens Lechtenboerger
2016-03-13 19:57 ` Nils Gillmann
2016-03-14 16:55 ` Nils Gillmann [this message]
2016-03-14 17:41 ` possible emacs 24.5 + Gnus problem when using pgpmime and signencrypt Jens Lechtenboerger
2016-03-14 9:39 ` Trouble with GnuPG 2.1 Nils Gillmann
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8760wp6lt0.fsf_-_@grrlz.net \
--to=niasterisk@grrlz.net \
--cc=info-gnus-english@gnu.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.
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 NNTP newsgroup(s).