le>> So simply the act of decoding a MIME attachment, not /directly/
le>> executing it nor /directly/ loading it into any other program,
le>> can be directly hazardous. 
RC> Thanks for the explanation.  Now, tell me how "reading" the file
RC> _executes_ it.  The whole point was something has to be "executed" to
RC> cause a virus infection - and you've said the same thing.  Your "the
RC> next time Word is called could cause execution of the (phony)
RC> handler" [words to that effect] makes it clear that _something_ has
RC> to be executed.
The point is, that it is possible to download a Trojan/seeder, and simply the 
act of downloading it, NOT taking ANY direct action to launch it, puts the 
system at risk.
The situation is roughly equivalent to having a PC email program which will 
automatically change the Windows shell association for "*.doc" to 
"C:\EUDORA\INBOX.FOL\MIME123.EXE" when it receives an executable attachment.
-- Lewin A.R.W. Edwards [Team OS/2]  Tel 0412809805 * http://www.zws.com/
--- MsgedSQ/2 3.35
---------------