Hello Code,
> NOD32 is incapable of scanning (like .tbb) will do nothing. NOD32 is
> still incapable of peaking inside the file.
I know. But even if it was capable, I wouldn't let NOD32 (or any other
antivirus) fiddle with my mail folders.
--
Best regards,
Miguel A. Urech (El Escorial - Spain
>> 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
Hello MAU,
Tuesday, January 30, 2007, 5:41:10 PM, you wrote:
M> In the 'Extensions Editor', try deselecting the 'Analyse all files' tick
M> box at the bottom and it will now list the extensions to scan.
Thanks. Ticked "Analyse all files" again though...
--
Best Wishes,
Mark
Hello Mark,
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...
In the 'Extensions Editor', try deselecting the 'Analyse all files' tick
box at the bottom and it will n
Hello MAU,
Sunday, January 28, 2007, 1:00:38 PM, you wrote:
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...
--
Best Wishes,
Mark
using The
Hello MFPA,
> 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.
And that was a big surprise to me because I was sure (without actually
testing it) that AMON would detect it. But no, you are right, I have
been testing
Tuesday, January 30, 2007, 12:47:29 PM, you wrote:
>> FWIW, I appear to have v2.51.26 of NOD32.
> I have 2.50.25 and clicking on "update now" tells me my
> installation is up to date and no update is required.
Latest version is 2.70.23 - however at this point you still have to
download this man
Hi
On Saturday 27 January 2007 at 1:06:07 AM, in
, George Mitchell
wrote:
> FWIW, I appear to have v2.51.26 of NOD32.
I have 2.50.25 and clicking on "update now" tells me my
installation is up to date and no update is required.
--
Best regards,
MFPA
Consistency i
Hi
On Tuesday 30 January 2007 at 1:25:04 AM, in
, MFPA wrote:
> Hi
> On Sunday 28 January 2007 at 12:00:38 PM, in
> , MAU wrote:
>> Check you AMON configuration. Either you have some excluded directories
>> or *.tmp is not in the list of file extensions to scan.
> I just checked mine and added
Hi
On Sunday 28 January 2007 at 12:00:38 PM, in
, MAU wrote:
> Check you AMON configuration. Either you have some excluded directories
> or *.tmp is not in the list of file extensions to scan.
I just checked mine and added TMP. I believe it was not there by
default, as I don't recall previously
Hello all,
Saturday, January 27, 2007, Code 2 wrote:
> You're right, George, we can use the plug-in to scan outgoing mail. I
> notice that the plug-in is a test version (version 0.1) and appears to
> have been developed several years ago for NOD32 version 1. The
> plug-in seems to work with NOD32
Hello Code,
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 wil
>> 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
Hello Code,
> 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.
>
Code 2 wrote:
C2> You're right, George, we can use the plug-in to scan outgoing
C2> mail. I notice that the plug-in is a test version (version 0.1)
C2> and appears to have been developed several years ago for NOD32
C2> version 1. The plug-in seems to work with NOD32 version 2.7
C2> except it gene
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
Code 2 wrote:
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. S
Here's a heads-up for users of NOD32 anti-virus and The Bat!. NOD32's
technical support people confirmed to me that NOD32's on-demand
scanner cannot scan inside The Bat's messages.tbb data files and
therefore cannot spot infected e-mails. However, NOD32's IMON module
s
20 matches
Mail list logo
