At 6:15 PM 2/12/96, Kisong Yoon wrote:
1. How can I implement incoming and outgoing encryption MOSS message of
multiple
recipients?
- For outgoing, in which order do I have to put Recipient-ID and Key-Info
of each recipient? Is it the order where they appear in to:, cc: and bcc:?
There is no required relationship between the 822 headers (TO, CC, BCC) and
the MOSS (or PEM, for that matter) recipient and key headers. There is
also no defined order. You may put them in whatever order suits you.
- For incoming, how can I find the corresponding Recipient_ID and Key-Info
among multiple Recipient-ID and Key-Info? If the key identifier is not the
email address, can I assume the order is in to:, cc: and bcc:?
You need to look at all the recipient-id fields to find the one which
matches yourself. Presumably, the application knows the identity for which
it is searching. It may even have a short list of identities in which it
is interested. Therefore, locating known recipient-ids is just a matter of
a string comparison.
2. How can I handle bcc? I think I have to prepare multiple bodies?
For recipients of to: and cc:, the body should not show the Recipient-ID and
Key-Info of bcc: recipients. For each recipint for bcc:, the body should
only show the corresponding Recipient-ID and Key-Info. Am I correct?
There is no standard way to handle BCC. In fact, different email user
agents do different things, independent of MOSS.
In my opinion, the TO and CC recipients should not see the BCC recipients,
BCC recipients should not see other BCC recipients, and the BCC recipients
should see the TO and CC recipients. To accomplish this you must create a
separate message for each BCC recipient in addition to the message for the
set of TO and CC recipients.
Jim
----------------------------------------------------------------------------
James M. Galvin
galvin(_at_)eit(_dot_)com
VeriFone/EIT, PO Box 220, Glenwood, MD 21738 +1 410.795.6882