From: David S Goldberg <david.goldberg6@verizon.net>
Subject: bad default for signencrypt with smime?
Date: Tue, 22 Jul 2003 15:04:58 -0400 [thread overview]
Message-ID: <u8zsmoyv0v9.fsf@verizon.net> (raw)
According to C-h v, mml-signencrypt-style-alist now defaults to
combined for smime. However when I just tried to send a signed and
encrypted message to a colleague, I got the message that
Combined sign and encrypt S/MIME not support yet
which suggests that the default is broken.
Or is there a newer version of openssl available that supports it.
Thanks,
--
Dave Goldberg
david.goldberg6@verizon.net
next reply other threads:[~2003-07-22 19:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-22 19:04 David S Goldberg [this message]
2003-07-31 1:05 ` 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=u8zsmoyv0v9.fsf@verizon.net \
--to=david.goldberg6@verizon.net \
/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).