5 minutes to scan 4 mails........ :-(

[eric37200]

yep  
wait & see

[Lisandro]

I do understand that proxy setting can affect updates, but once again it is not the question. Neither Eric nor me have problem with updates. No offense there, you answer to so many questions and your devotion to help users is priceless.

Thanks and sorry to mess my answers...  
Eric, in fact, when a virus is found avast could enter in paranoid behavior, I mean, all security levels are set to high in order to avoid infection spread.
Anyway, it should not freeze or take that time to process the emails... you're right.

Can't anybody from Alwil say anything about this?  

[farfouille]

I think I've solved the problem...

What I did :
- uninstall avast 4.5.536 + reboot + delete remaining files/directories
- install avast 4.5.523 (the last official release) + avast automatically updates the vps to 0448-1
- test with the eicar stuff : OK :  no time delay to deal with the infected mail
- I then restore avast parameters : silent mode + send alert mail on infection
- reboot
- test with aicar stuff : KO : long delay (3min.) to handle infected mail
- I then removed the send alert mail on infection and everything  run smooth again
(all test using dialup connection)

Conclusion : It seems that the send alert mail is the problem...

[Lisandro]

Thanks for debugging it, Farfouille.

What is set for your default smtp server into avast4.ini file?

[eric37200]

I think I've solved the problem...

What I did :
- uninstall avast 4.5.536 + reboot + delete remaining files/directories
- install avast 4.5.523 (the last official release) + avast automatically updates the vps to 0448-1
- test with the eicar stuff : OK :  no time delay to deal with the infected mail
- I then restore avast parameters : silent mode + send alert mail on infection
- reboot
- test with aicar stuff : KO : long delay (3min.) to handle infected mail
- I then removed the send alert mail on infection and everything  run smooth again
(all test using dialup connection)

Conclusion : It seems that the send alert mail is the problem...

maybe maybe....
for me when i test my smtp...."unknown error"...
i dont know why...i used always same smtp server (smtp.free.fr)...
i prefer this...actually avast work well...

[farfouille]

Thanks for debugging it, Farfouille.

What is set for your [/i]default[/i] smtp server into avast4.ini file?

Technical, it is very cute to thank me but I have to confess that I'm a software developper and that kind of problem always ring my professional bell...  

Well the laptop I used to make the test is now far away from home (it is not mine, i had it to ... install avast). So I can't look into the avast4.ini but I remember well that when I configured the smtp alert avast asked me for the smtp server and the originator mail. I entered the same smtp server as the ISP which is  'free' (smtp.free.fr).

If you guess that it can be a configuration problem with the smtp server or mail adresses set up for the alert, let me tell you that you are right to think of such a problem but  I've double checked that and it was ok. Btw when an infected mail was detected (and take a long time to be processed), I received the alert (I am the receiver). If I can find some time I will make some further test with my adsl connection using the smtp alert.

Eric do you use the smtp alert feature of avast when an infected mail is received ?

Farfouille

[eric37200]

yep i used smtp alert....but now as i say in my lat message, i cant...
...its not very important....but i cant : when i test, i've got error message....

...but avast work well actually...

[farfouille]

Thank you Eric.

It appears that we both have problem with stmp alert.

I think we can reasonably pass the baby to alwil team.  


Farfouille

[Vlk]

Thanks, acknowledged, will fix asap. Good work guys!

[eric37200]

Just another little thing : when i re-installed avast, i made a boot scan (avast found nothing...like always...  .
when i've got problems, the other time, i do not made a boot scan...
...maybe another reason...      

[Vlk]

Oddly enough, this was only problem on single-processor machines. Dual or more (or hyperthreading-enabled) machines did not have this problem

Anyway, we've isolated and fixed the problem now.

Thanks!
Vlk

[farfouille]

Anyway, we've isolated and fixed the problem now.

Good news for all of us

[eric37200]

to close this topic....  
i've clean my registry with avast bart demo version and after that my problem re-appeared.....  
...i made update for my preferred antivirus  
....and my problem is solved !
great !
thanx !  

cheers
ERIC

[Lisandro]

...i made update for my preferred antivirus  
....and my problem is solved !

Which one (antivirus) are you talking about?  

Did you have time to test the last program update (official release, not a beta) is 4.5.542 and fixes many of the earlier problems  

[eric37200]

...i made update for my preferred antivirus  
....and my problem is solved !

Which one (antivirus) are you talking about?  

AVAST of course !!!