>> A test message with Eicar string attached in a txt file is sent
>> without AMON shouting about it but picked up by IMON on receipt.
M> And that was a big surprise to me because I was sure (without actually
M> testing it) that AMON would detect it. But no, you are right, I have
M> been testing
M>>> or *.tmp is not in the list of file extensions to scan.
>>
>> Where do you have a list of file extensions to scan? I only see a(n empty)
>> list of extensions NOT to be scanned...
M> In the 'Extensions Editor', try deselecting the 'Analyse all files' tick
M> box at the bottom and it will now
>> 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.
ASK>
>> 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 NO
C2>> ...a situation could arise where I receive an infected e-mail
C2>> which NOD32's IMON module does not yet recognize (as happened to
C2>> me last week with the Fuclip.A worm). That infected e-mail would
C2>> sit undiscovered in my inbox despite several NOD32 on-demand
C2>> scans. Since NOD32's
5 matches
Mail list logo
