Mime Type for Encrypted Attachments

[Patrick Brunschwig]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

| On Fri, 23 May 2003 00:56:38 +0200, Ingo Kl=F6cker said:
|
|> Are you not confusing something? The encrypted and armored message is
|> not in the application/pgp-encrypted but in the
|> application/octet-stream message part. Typical message (the same as in
|
| Oops.  You are of course right.
|
|> And using pgp-keys is IMO also wrong because this will confuse MUAs
|> which provide an Import Key functionality for pgp-keys attachments and
|
| Of course only for message containing a key.
|
|> The correct content-type is application/octet-stream with
|> Content-Description: encrypted data. But that's what I already wrote i=
n
|
| If you use MIME, use it correctly: rfc3156 ;-) If you don't want that,
| don't indicate that it is a MIME message.  If attachments are to be
| encrypted separately, use text/plain and let the user check whether he
| can figure out what to do when noticing the BEGIN PGP line.

Thanks for all the answers! In fact I'm quite aware of PGP/MIME and what
is correct there. I think I will use application/octet-stream as
suggested, and which many other mail clients use anyway if you attach
pre-encrypted files. The point is that I would like mail clients to be
able to detect the PGP encrypted attachments (and possibly act
accordingly), but this will usually fail if I'd use text/plain.

- -Patrick

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE+zjsz2KgHx8zsInsRAtqTAJ9m0IrCfTALFitcXfkUJUVSNe1wBACeLnt0
23J6dz0su1Zo1bAF8XrXdtw=3D
=3DWFSs
-----END PGP SIGNATURE-----