Gnus development mailing list
 help / color / mirror / Atom feed
From: Josh Huber <huber@alum.wpi.edu>
Subject: Re: Crypto-MIME in GNUS
Date: 10 Apr 2001 10:19:48 -0400	[thread overview]
Message-ID: <87elv0kfaz.fsf@mclinux.com> (raw)
In-Reply-To: <m3k84szxyd.fsf@reason.gnu-hamburg>

"Georg C. F. Greve" <greve@gnu.org> writes:

>  sj> Right, `message-options-set-recipient' only look at the To:
>  sj> header.
> 
> Exactly. Which is stupid. Unless the others are also you (which is not
> the standard case, imho), they won't be able to read the mail then. So
> why bother sending it to them at all?

I consider this a bug...

> ...does pretty much the same. But only almost. It only encrypts the
> following part, not the whole message. When I encrypt I normally want
> the whole thing encrypted... otherwise you run a high chance to
> insert another part and accidentally lose encryption that way.

I think this is a bug as well?  If I select that I want the message
signed or encrypted, it should wrap the entire message (with mime
parts included) as an encrypted or signed part.

does your code do this properly, or is this just a bug in mml2015?

> ...which requires much more action on the receiving part to import the
> key. With a proper MIME part, a good mailreader can import that key
> with a single keystroke. 

This is a nice thing that should be included in Gnus IMHO.  both the
sending of keys and importing.

-- 
Josh Huber


  parent reply	other threads:[~2001-04-10 14:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-10  8:52 Georg C. F. Greve
2001-04-10 10:50 ` Simon Josefsson
2001-04-10 13:27   ` Georg C. F. Greve
2001-04-10 13:23     ` Simon Josefsson
2001-04-12 10:33       ` Georg C. F. Greve
2001-04-12 11:27         ` Florian Weimer
2001-04-10 14:19     ` Josh Huber [this message]
2001-04-13 13:10   ` Georg C. F. Greve

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=87elv0kfaz.fsf@mclinux.com \
    --to=huber@alum.wpi.edu \
    /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).