>> Having said that, a situation could arise where I receive an >> infected e-mail which NOD32's IMON module does not yet recognize >> (as happened to me last week with the Fuclip.A worm). That >> infected e-mail would sit undiscovered in my inbox despite several >> NOD32 on-demand scans. Since NOD32's IMON module does not scan >> outgoing mail, I could unwittingly forward it to, and infect, an >> unsuspecting recipient.
M> 2.- You forward the message _after_ NOD32 signatures have been updated. M> Then there is nothing to worry about. Why? Even though NOD32's 'IMON M> does not scan outgoing email' and 'on-demand scanner does not scan tbb M> files', the infected email/file you are trying to send will be detected M> by AMON in the bat*.tmp file created and used by TB to compose/send the M> message. Try it out. Send a message an then take a look at AMON and see M> the name of the last file scanned. I have tested it with the EICAR test virus and AMON does not scan the temp file, and neither AMON nor IMON scan the outgoing mail. I have since installed the plug-in for The Bat! and thank heavens the plug-in forces the scan of outgoing mail. M> Finally, a note for those using NOD32 Plugin for TB. There seem to be M> two different versions running around. One at http://tinyurl.com/yuy529 M> and a different one at http://tinyurl.com/yoo2q3 It looks like the German version at http://tinyurl.com/yoo2q3 is a couple years newer than the version on the Ritlabs site (though that doesn't necessarily mean it's better). The newer version has a different user interface when it identifies infected outgoing mail. -- Code 2 :canadaflag: mailto:[EMAIL PROTECTED] The Bat! version 2.12.00 on Windows XP Service Pack 2 On a butcher's window: Let me meat your needs. ________________________________________________ Current version is 3.95.08 | 'Using TBUDL' information: http://www.silverstones.com/thebat/TBUDLInfo.html
