spock(_at_)RSA(_dot_)COM said:
We have once again achieved consensus:
- multipart/signed is great.
- Lot's of gateways suck because they screw up multipart/signed.
How does these "gateways" handle other multipart types?
- Email signatures using multipart/signed simply won't work until sucky
gateways are fixed.
If we fx. take multipart/alternative with 2 parts, will these 2 parts
be fu^h^hchanged by said gateways?
If these gateways are not able to deliver the original content of any
multipart/* parts, how can these gateways stay in the market?
With "original content" I mean the content protected by the MIME transfer
protection mechanisme, which (AFAIK) takes a good deal of consideration
towards protection the original content against gateways.
--
=============================================== | | ====
=============================================== _| _| _ ====
=============================================== / | / | /_\ ====
=============================================== \_| \_| \_. ====
Frederik H. Andersen, M.Sc.
Senior Software Engineer
Internet Development
Dansk Data Elektronik A/S Phone: +45 42 84 50 11
Herlev Hovedgade 199 Fax: +45 42 84 52 20
DK-2730 Herlev, Denmark Web: http://www.dde.dk
Email: fha(_at_)dde(_dot_)dk (MIME accepted)
PGP Fingerprint: 6B BC FB 45 E4 69 CE A2 63 E1 62 1F 0C 65 C2 E4
==================================================================
pgpa5iPl72Nym.pgp
Description: PGP signature