Ned:
Thanks for correcting the details.
RFC 822 defines a header, which is clearly outside the SMTP envelope. The
RFC 822 header is separated from the content by a blank line. The subject
line is before this blank line, so it cannot be protected by a content
encapsulation protocol.
Sorry for any confusion that may have resulted from the loose terminology
in my first message.
Russ
At 09:28 AM 12/18/2001 -0800, ned(_dot_)freed(_at_)mrochek(_dot_)com wrote:
The subject line issue is not a problem in the X.400 world. SMTP
carries
the subject line is in the envelope.
On the contrary, in SMTP the subject field is part of the content, not part
of the envelope. Specifically, it is part of the message header.
The corresponding X.400 protocols
(P1, P3, and P7) do not. In X.400, the subject line is part of the
content.
This part is correct, but it fails to get at the reason why X.400 and SMTP
differ in their ability to protect the entire content of a message end to
end.
============================================================================
================
This e-mail, its content and any files transmitted with it are intended
solely for the addressee(s) and are PRIVILEGED and
CONFIDENTIAL. Access by any other party is unauthorized without the express
prior written permission of the sender. If
you have received this e-mail in error you may not copy, disclose to any
third party or use the contents, attachments or
information in any way, Please delete all copies of the e-mail and the
attachment(s), if any and notify the sender.
Thank You.
============================================================================
================