haertig,

Things just get confuseder and confuseder don’t they? :o ??? ::slight_smile:
I noticed that, in your Kerio popup dialog that the description refers to aswquick.exe and the application refers to ashquick.exe. This had me thinking that, perhaps, you had a trojan copy, but when I examined ashquick.exe I see references to aswquick.exe throughout. I guess Alwil must have done a last-minute name change or something. Still, I have no idea why you’re seeing these additional apps looking for internet access.

Technical,

I probably wasn’t as clear as I could have been about ashquick.exe vs ashserv.exe. What I meant was that if an on-demand scan (which uses ashquick.exe, I believe) finds a virus, perhaps ashquick.exe would attempt the email connection itself thereby triggering Kerio’s popup. I doubt it, but could ashquick’s calling of ashserv.exe for the email processing somehow be read by Kerio as an attempt by ashquick? Anyway, my thought was that if Kerio is configured for ashquick.exe and ashserv.exe is not, then the standard shield and other providers might not be able to get ashserv to send the alert via email. (Wow, I think may be even less clear than my first post! :-\

I suppose that haertig could go for the safest/surest option and, as he suggested, configure all the Avast *.exe’s for SMTP access. What could it hurt, as they say?

I love a mystery.