le>> The point is, that it is possible to download a Trojan/seeder,
le>> and simply the act of downloading it, NOT taking ANY direct
le>> action to launch it, puts the system at risk. 
RC> In exactly the same way as downloading an infected file to a DOS
RC> system.  The "system is at risk" because the file is _there_, and
RC> _may_ be executed.  This is not a "MAC-specific" problem.
NOT in exactly the same way. In the situation I described it is possible for 
the attachment to be launched by opening unrelated document files which were 
previously safe to open.
The analogous situation (as I think I already said) would be if you 
downloaded something in Windows, and this "something" changed the default 
association for "*.txt" from whatever it was, to the executable you just 
downloaded.
-- Lewin A.R.W. Edwards [Team OS/2]  Tel 0412809805 * http://www.zws.com/
--- MsgedSQ/2 3.35
---------------