>There is no "by chance" about it. The MIME structure of multipart/signed
offers
>a clear indication to gateways that the data is signed. It is up to the
gateway
>to handle such material in an appropriate manner.
Your correct. However I was specifically referring to RFC 1327
gateways, which at the current time are not aware of multipart/signed
messages. This means, and implementation of RFC 1327 is perfectly
allowed to split a MIME message into its components, and then rebuild
them, but there is nothing to say the MIME headers have to be built in
the same order. If the order is different the signature fails.
The next verson of RFC 1327 - MIXER, needs to be aware of
multipart/signed messages, and pass the message through untouched. This then
leaves the X.400 User Agent with the task of interpreting the MIME
body part after signature verification. This should not be too
difficult.
The other alternative for MIXER is to push multipart/signed messages
into X.400 file transfer body parts. This makes it easier for the
X.400 user agent, and it will often use external processes for these
anyway, so in this case, it could invoke the MOSS interpretor process.
Colin