Avast! 4 does not work with Kerio v4.0

[MrPuddles]

I have the latest version of Avast! installed and the regular email scanner does not work with Kerio Personal Firewall V4.0 RC3.  I am 100% sure that this is on fault of Kerio's part and does not have to do w/ Avast!.  I am just getting the work out so that the Avast community knows about this bug.  My email client will load and will pause and not check email.  If I unload the firwall, it will retrieve email.

Thanks,
~Derek

[whocares]

Hi,

I guess you will have to adjust either some of the (predefined?) rules in Kerio, or change ports in your MailClient and/or avast mailchecker
I think on the latter there were some threads here in the Board already.; use the Board search..  

Have you set Kerio to "Ask me first" ?

To enable logging of all blocking operations in Kerio might help finding out where it "hangs"

 

[MrPuddles]

I have modified the rules and even deactivated the firewall and the Avast! virus scanner will still not work.  When I unload the firewall from memory, it will work again.  I had the rules set to work with previous releases of the Kerio firewall. I am pretty sure this is a bug in the latest version of kerio b/c they have been fixed a lot of bugs related to the loopback rule (127.0.0.1).  I have reported the bug to Kerio support for review.  Has anyone else experienced this problem with RC3?

[whocares]

even deactivated the firewall

Hi,
I don't know about Kerio 4, but some PFWs  (like ZoneAlarm, at least earlier Versions) imho block network Completely!!   if you deactivate (exit?) them.
But you checked that, I assume, by trying to access the inet/WWW with deactivated Wall ?



 

[MrPuddles]

I have disabled the firewall, but not blocked traffic.  I can still browse the internet, use IM, access FTP, ect.  Kerio 4.0 RC3 seems to block the traffic between the email scanner no matter if it is temporarily disabled or functional.  Closing Kerio makes it work.  However, updating the virus scanner works.  Something is wrong with the loopback.  Hopefully, they will fix this soon or someone will discover a workaround.

[whocares]

what happens if you explicitly allow loopback 127.0.0.1 for all apps and set it "on top" of the ruleset, .i.e. make it first priority rule ?
 

[RJW]

It is a Kerio problem because Kerio 2.1.5 works correctly with Avast mail scanning, but I have not been able to get any of the Kerio 4 beta's and Kerio 4 RC's to work with Avast mail scanning.

Bob

[Vlk]

I'll try to ask the Kerio folks -- I know them pretty well...
I'm pretty sure we'll sort this out as we absolutely need to have these two progs work together...

Vlk

[RJW]

I'll try to ask the Kerio folks -- I know them pretty well...
I'm pretty sure we'll sort this out as we absolutely need to have these two progs work together...

Vlk

Thanks Vlk,

Here is some more information on this issue -

With Windows 2000 Pro SP4, Outlook Express 6 SP1, and Kerio 2.1.5 I use the following rules and mail scanning works -

The rule for OE is as follows -

Description = OE
Protocol = TCP
Direction = Outgoing
Local Port = any
Application = c:\program files\outlook express\msimn.exe
Remote Address = 127.0.0.1
Remote Port = List of ports (25,110)
Action = Permit


The rule for Avast is as follows -

Description = Avast mail scan
Protocol = TCP
Direction = Outgoing
Local Port = any
Application = c:\program files\alwil software\avast4\ashmaisv.exe
Remote Address = any
Remote Port = List of ports (25,110)
Action = Permit

But like I said above I cannot get Outlook Express/Avast Mail Scanning to work with Kerio 4 Beta's/RC's.  

Thank You
Bob

[lukor]

Bob, it seems to me you are missing a rule to allow Avast to accept incomming connections (from localhost) at POP3 and SMTP port numbers. Something like this might work (cannot verify that right now).

Description = Avast Mail - scanning server
Protocol = TCP
Direction = Incomming
Application = c:\program files\alwil software\avast4\ashmaisv.exe
Local Port: List of ports (25,110)
Local Address: 127.0.0.1
Remote Port: any
Remote Address: 127.0.0.1
Action: Permit

Lukor.

[MrPuddles]

I have tried manually setting the rules for my email client (Mozilla Thunderbird) and Avast, but that doesn't work either.  I have even set up rules to open up all ports just to see if it was me.  I have pretty much ruled this as a bug on kerio's part.  It's still a beta client and they should update it sometime in the next beta release.  I have sent a couple of emails detailing everything.  For those who like Kerio, keep using the 2.1.5 client.  It works like a charm.

[tosbsas]

Any news on that one?? Kerio 4 is out as 402

Ruben

[Vlk]

Yes they're working on it. I've talked to them on Friday and they confirmed the fix will be ready very soon.

Vlk

[vojtech]

As a workaround, try inserting this line to file C:\Program Files\ALWIL Software\Avast4\Data\Avast4.ini into section [MailScanner]:
UseWSAAccept=0
then terminate process ashMaiSv.exe and start it again.

[joanlui]

Hey! I am using Agnitum Outpost 2.0 and Avast 4! No problem with it!  

However, KPF4 is not a final version...