On Thu, 01 Sep 2005 11:15:40 +0100, Karl Kashofer said:
Well the way Werner describes it, he just advises not to use a Subject.
What I mean is that a subject you need to decrypt first is not very
usable for the purpose a subject line is commonly used, i.e. to
quickly decide what messages belong together and whether to read them.
With a slow connection and POP3 and with IMAP in general many people
just look at the subject to decide whether to retrieve the entire
message. Requiring to decrypt it first make no sense then.
So, my suggestion is to use a non-sense subject line to merely help
visualizing a theread.
Could you by any means describe this in more detail ?
Something like this:
From: me(_at_)example(_dot_)org
To: you(_at_)example(_dot_)com
Subject: none
Content-Type: multipart/encrypted;
protocol=application/pgp-encrypted;
boundary="xxxxxx"
--xxxxxx
Content-Type: application/pgp-encrypted
Version: 1
--xxxxxx
Content-Type: application/octet-stream
& Content-Type: message/rfc822; boundary="yyyyy"
&
&
& --yyyyyy
& From: me(_at_)example(_dot_)org
& To: you(_at_)example(_dot_)com
& Subject: Don't tell anyone that PGP/MIME just works
& Content-Type: text/plain
&
& Proposal on how to gain world domination of PGP/MIME
& and to abolish any use of S/MIME.
&
& --yyyyyy--
--xxxxxx--
Where the lines marked by "&" are actually encrypted.
Salam-Shalom,
Werner