> > > Is S/MIME using the multipart/{encrypted,signed} (RFC1847), or did
> > > they cook up something different?
> >
> > I would suggest you to look at www.rsa.com for PKCS standards series.
> > Actually S/MIME is PKCS #7. Also it was decribed somewhere else. I
> > found osme traces in RFCs...
> >
> > But this standard is a basic one.
>
> I know that S/MIME is defined in a series of RFC's.
> This doesn't answer my question. PKCS#[0-9]+ has nothing to do with how
> encrypted messages are sent via MIME.
> <digging...>
> OK, FTR: It's RFC2311 and it seems to build on rfc1847. So the
> framework for rfc2015/rfc3156 that is being developed currently can be
> used for s/mime, too.

Ough, yes. If we talk about embedding PKCS #7 message in a mail - 2311 is=
 a=20
good start. But I suspect it is better to look at 2632, 2633, 2634 first.=
=20
They describe S/MIME v3. not v2.

--=20
Sincerely Yours,
Denis Perchine

----------------------------------
E-Mail: dyp@perchine.com
HomePage: http://www.perchine.com/dyp/
FidoNet: 2:5000/120.5
----------------------------------
_______________________________________________
Kmail Developers mailing list
Kmail@mail.kde.org
http://mail.kde.org/mailman/listinfo/kmail