[Top] [All Lists]

Re: The subject line leakage problem

2001-12-18 13:32:12


I have had a lot of experience in this area, and I am glad to hear that new 
product releases have repaired this major shortcoming.  I have personally 
been bit by this by more than one product.

I do not think that MTA architectures are the main point of this thread, so 
lets see if we can get back to the S/MIME and CMS issues...


At 06:24 PM 12/18/2001 +0000, Jim Craigie wrote:
Now, in theory X.400 MTAs only deal with the envelope and are able to
arbitrary content types around, making it possible to introduce new 
ones at any
time. Howevr, I've found that sometimes this works in practice and often
doesn't. Support for this in real world X.400 implementations is far
uniform. At least part of the reason why this is so is because this 
is rarely used, and rarely used capabilities are bound to have bugs, 
given that most X.400 implementations are rarely updated these days.

I don't know what X.400 systems you are basing the above comment on. I've 
been involved with interoperability testing STANAG 4406 PCT (just CMS 
really), and we have not seen a single problem with an X.400 MTA being 
unable to relay the new content type.

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.