From: Nicolas Kowalski <Nicolas.Kowalski@imag.fr>
Cc: ding <ding@gnus.org>
Subject: smime setup [was: Re: nnimap + mailcrypt]
Date: Thu, 11 Apr 2002 15:55:32 +0200 [thread overview]
Message-ID: <vqolmbupcff.fsf@astazou.imag.fr> (raw)
In-Reply-To: <Pine.LNX.4.44.0204111509560.15526-100000@yxa.extundo.com>
Simon Josefsson <jas@extundo.com> writes:
> On Thu, 11 Apr 2002, Nicolas Kowalski wrote:
>
>> Ah ! I think I found what the problem is : the messages I am unable to
>> decrypt come from M$ Outlook :
>
> Gnus does not support Outlook-PGP yet. C-d on the message may be a
> workaround.
Ok.
> The reason is that the Outlook PGP plugins do not support either of the
> two IETF standards on how PGP in mail should look like. Outlook supports
> S/MIME correctly and natively though (and so do Gnus), so perhaps you will
> have better luck with it. S/MIME seem to interop a magnitude or so better
> than PGP today... a few years ago, the reverse was true.
I have no luck :-(. See below. I followed the instructions from smime.el.
Excerpt from my .emacs:
(smime-CA-file "\"~/perso/certs/cacert.pem\"")
(canlock-password "4de89211c1a1f5ac8dca322797c2cb38f36f2018")
(smime-keys (quote (("Nicolas.Kowalski@imag.fr" "\"~/perso/certs/niko.pem\"" nil))))
And when I try to send a smime signed message, I have (sorry for the
long lines) :
Signaling: (wrong-number-of-arguments #<compiled-function (prompt table &optional predicate require-match initial-contents history) "...(37)" [table predicate require-match t nil last-exact-completion minibuffer-completion-confirm minibuffer-completion-predicate minibuffer-completion-table read-from-minibuffer prompt initial-contents minibuffer-local-completion-map minibuffer-local-must-match-map history] 6 748493> 7)
completing-read("Sign using which signature? (default Nicolas.Kowalski@imag.fr) " (("Nicolas.Kowalski@imag.fr" "\"~/perso/certs/niko.pem\"" nil)) nil nil nil nil "Nicolas.Kowalski@imag.fr")
smime-sign-buffer(nil)
mml-smime-sign((part (sign . "smime") (tag-location . 549) (contents . "\n\nnklnklgf\ngfkflknglf\n")))
mml-smime-sign-buffer((part (sign . "smime") (tag-location . 549) (contents . "\n\nnklnklgf\ngfkflknglf\n")))
mml-generate-mime-1((part (sign . "smime") (tag-location . 549) (contents . "\n\nnklnklgf\ngfkflknglf\n")))
mml-generate-mime()
message-encode-message-body()
message-send-mail(nil)
message-send-via-mail(nil)
message-send(nil)
message-send-and-exit(nil)
call-interactively(message-send-and-exit)
next prev parent reply other threads:[~2002-04-11 13:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-11 8:19 nnimap + mailcrypt Nicolas Kowalski
2002-04-11 12:04 ` Simon Josefsson
2002-04-11 12:13 ` Nicolas Kowalski
2002-04-11 12:24 ` Simon Josefsson
2002-04-11 12:40 ` Nicolas Kowalski
2002-04-11 13:16 ` Simon Josefsson
2002-04-11 13:55 ` Nicolas Kowalski [this message]
2002-04-11 15:03 ` smime setup [was: Re: nnimap + mailcrypt] Simon Josefsson
2002-04-11 15:13 ` Nicolas Kowalski
2002-04-11 15:42 ` Simon Josefsson
2002-04-11 15:59 ` Nicolas Kowalski
2002-04-11 19:23 ` Simon Josefsson
2002-04-11 19:27 ` Simon Josefsson
2002-04-11 20:05 ` Nicolas Kowalski
2002-04-11 20:10 ` Simon Josefsson
2002-04-11 19:56 ` Nicolas Kowalski
2002-04-11 20:25 ` Simon Josefsson
2002-04-12 7:41 ` Nicolas Kowalski
2002-04-12 10:51 ` Kai Großjohann
2002-04-12 12:45 ` [SOLVED: openssl issue] " Nicolas Kowalski
2002-04-12 20:47 ` Simon Josefsson
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=vqolmbupcff.fsf@astazou.imag.fr \
--to=nicolas.kowalski@imag.fr \
--cc=ding@gnus.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).