Gnus development mailing list
 help / color / mirror / Atom feed
From: Andreas Fuchs <asf@void.at>
Subject: mml-sec is a little brittle
Date: Mon, 19 Nov 2001 15:31:43 +0100	[thread overview]
Message-ID: <E165pSZ-0000p3-00@eris.ath.cx> (raw)

[-- Attachment #1: Type: text/plain, Size: 635 bytes --]

Hi!

Using my version of bbdb-pgp.el (http://asf.void.at/emacs/bbdb-pgp.el -
a slightly modified version of Fabien Penso's bbdb-pgp), I would love to
have it generate signed/encrypted messages automatically.

IIRC, this should work with mml-secure-{sign,encrypt}-pgp. Yet, it only
marks the last part of the message as signed/encrypted, even
though the message is marked as multipart.

Would it be possible to have mml-secure-part prefer the multipart tag to
the other ones (mml, external, part), or is it an intentional feature
that only the last part gets secured?

Thanks,
-- 
Andreas Fuchs, <asf@acm.org>, asf@jabber.at, antifuchs

             reply	other threads:[~2001-11-19 14:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-19 14:31 Andreas Fuchs [this message]
2001-11-19 16:11 ` Josh Huber

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=E165pSZ-0000p3-00@eris.ath.cx \
    --to=asf@void.at \
    /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).