From: James Cloos <cloos@jhcloos.com>
To: Greg Troxel <gdt@work.lexort.com>
Cc: ding@gnus.org
Subject: Re: best approach to S/MIME?
Date: Fri, 15 Mar 2013 20:47:39 -0400 [thread overview]
Message-ID: <m3ehfgnpa3.fsf@carbon.jhcloos.org> (raw)
In-Reply-To: <smua9q4qupb.fsf@linuxpal.mit.edu> (Greg Troxel's message of "Fri, 15 Mar 2013 16:22:40 -0400")
>>>>> "GT" == Greg Troxel <gdt@work.lexort.com> writes:
GT> I am trying to get set up with S/MIME.
I customized this:
'(smime-CA-directory "/etc/ssl/certs")
to get gnus to verify smime-signed incoming messages.
I haven't needed to use smime for outgoing mail, and so haven't tested
that aspect at all.
-JimC
--
James Cloos <cloos@jhcloos.com> OpenPGP: 1024D/ED7DAEA6
next prev parent reply other threads:[~2013-03-16 0:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 20:22 Greg Troxel
2013-03-16 0:47 ` James Cloos [this message]
2013-03-18 9:34 ` Daiki Ueno
2013-03-18 11:22 ` Greg Troxel
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=m3ehfgnpa3.fsf@carbon.jhcloos.org \
--to=cloos@jhcloos.com \
--cc=ding@gnus.org \
--cc=gdt@work.lexort.com \
/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).