From: Mattias Ahnberg <mattias@ahnberg.pp.se>
Subject: Re: Gnus & GnuPG.
Date: 07 Feb 2001 00:19:37 +0100 [thread overview]
Message-ID: <m3u267flh2.fsf@paranoia.ahnberg.pp.se> (raw)
In-Reply-To: <iluae7zha0x.fsf@barbar.josefsson.org> (Simon Josefsson's message of "06 Feb 2001 20:43:58 +0100")
>> "SJ" == Simon Josefsson <sj@extundo.com> writes:
SJ> Try OGnus, and put $gnus/contrib in your load-path to make Gnus find
SJ> gpg.el. OGnus have integrated PGP/SMIME support, but make use of
SJ> external libraries (mailcrypt or, preferrably, gpg.el).
Hmm, might be working a little bit better, but at the same time not. I
might on the other hand be missing some configuration directives or
so, gpg.el isn't really to heavily documented. :)
Am I supposed to be using both mailcrypt and gpg.el? Or just gpg.el,
if I can? If I chose just to use gpg.el, what do I need to configure
to be able to sign, encrypt, verify and check stuff?
The main problem I seem to be having when using mailcrypt is that
people sending signed mails to me, using for example Mutt, seem to be
sending the mails as a multipart MIME mail, and mailcrypt doesn't seem
to figure this out.
The mails I send to him that I sign looks peachy for him though, and
the mails I send to myself works neat. But not from other
programs. Perhaps just his mutt that is wrongly configured to send it
like that? I'm pretty new to this signing/encrypting mail things, so
I am not really sure where to start digging around.
/ahnberg.
next prev parent reply other threads:[~2001-02-06 23:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-06 18:36 Mattias Ahnberg
2001-02-06 19:43 ` Simon Josefsson
2001-02-06 23:19 ` Mattias Ahnberg [this message]
2001-02-06 23:36 ` ShengHuo ZHU
2001-02-07 7:26 ` Kevin A. Burton
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=m3u267flh2.fsf@paranoia.ahnberg.pp.se \
--to=mattias@ahnberg.pp.se \
/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).