Gnus development mailing list
 help / color / mirror / Atom feed
From: Hrvoje Niksic <hniksic@srce.hr>
Subject: Re: MIME and mailcrypt
Date: 04 Dec 1998 17:32:13 +0100	[thread overview]
Message-ID: <kigzp93amwi.fsf@jagor.srce.hr> (raw)
In-Reply-To: Stainless Steel Rat's message of "04 Dec 1998 10:35:59 -0500"

Stainless Steel Rat <ratinox@peorth.gweep.net> writes:

> "SZ" == Stephen Zander <gibreel@pobox.com> writes:
> 
> Rat> - --==-=-=
> 
> SZ> Was this supposed to be a well-formed MIME message or did mailcrypt
> SZ> mangle it?
> 
> PGP armored it.
> 
> Do you begin to see some of the problems with mixing PGP and MIME?

Wouldn't this work right if Message knew about multipart/signed,
described in rfc2015?  Then Gnus could, at least in theory, call the
correct mailcrypt hooks to check the signature, and then display the
second part of the multipart as usual MIME stuff.

Or, am I missing something?

-- 
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
A radioactive cat has eighteen half-lives.


  parent reply	other threads:[~1998-12-04 16:32 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <x7yaortjhy.fsf@peorth.gweep.net>
1998-12-02 17:06 ` Lars Magne Ingebrigtsen
     [not found]   ` <x7pva21h57.fsf@peorth.gweep.net>
1998-12-02 23:57     ` Kai.Grossjohann
     [not found]       ` <x71zmixan9.fsf@peorth.gweep.net>
1998-12-03  2:21         ` Hrvoje Niksic
1998-12-03  8:46         ` Jari Aalto+list.ding
1998-12-03 10:38         ` Kai.Grossjohann
1998-12-03 11:35     ` Lars Magne Ingebrigtsen
     [not found]       ` <x767btkll7.fsf@peorth.gweep.net>
1998-12-04  2:09         ` Lars Magne Ingebrigtsen
     [not found]           ` <x7n25462fl.fsf@peorth.gweep.net>
1998-12-04  4:08             ` Lars Magne Ingebrigtsen
1998-12-09 22:48           ` Dave Love
1998-12-04  2:49         ` Stephen Zander
     [not found]           ` <x71zmfapi8.fsf@peorth.gweep.net>
1998-12-04 16:10             ` Karl Kleinpaste
1998-12-04 16:32             ` Hrvoje Niksic [this message]
     [not found]               ` <x7r9ufzv38.fsf@peorth.gweep.net>
1998-12-04 18:22                 ` Hrvoje Niksic
1998-12-04 18:49                   ` David S. Goldberg
     [not found]                   ` <x7af13hbfs.fsf@peorth.gweep.net>
1998-12-04 21:03                     ` Hrvoje Niksic
     [not found]                       ` <x7zp93fv0f.fsf@peorth.gweep.net>
1998-12-04 22:53                         ` Colin Rafferty
     [not found]                           ` <x7ogpj5tyv.fsf@peorth.gweep.net>
1998-12-05 16:09                             ` Lars Magne Ingebrigtsen
1998-12-06 19:47                               ` Dave Love
     [not found]                                 ` <x7u2z9ni5s.fsf@peorth.gweep.net>
1998-12-09 22:43                                   ` Dave Love
1998-12-04 22:54                         ` Hrvoje Niksic
1998-12-04 23:08                           ` Colin Rafferty
     [not found]                             ` <x7yaon5vtv.fsf@peorth.gweep.net>
1998-12-08  2:10                               ` Stephen Zander

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=kigzp93amwi.fsf@jagor.srce.hr \
    --to=hniksic@srce.hr \
    /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).