did something change in POP3 mail scan ?

[Goner]

hi,

i'm using MagicMailMonitor (http://mmm3.sourceforge.net/) for POP3 mailbox checking, never had a problem.
But after upgrading to Avast 4.6 yesterday, something goes wrong ; ashmaisv.exe gets activated and then my firewall (Outpost) blocks the POP3 connection due to a 'packet to closed port' ?!?! It actually blocks Avast (ashmaisv), not MMM ... ??

[Vlk]

Well ashMaiSv.exe must be granted pop3 (port 110) net access, of course... But that's probably not the problem here, is it?

[Goner]

probably not ...
as I never had the problem with 4.5 where ashmaisv.exe also had access to port 110.
I even made Avast a 'trusted application' in the firewall but still the "connection was lost" according to the mailbox checker ... ??
When I use Avast's "Stop on-access protection" (shutdown all on-access scanners), the problem goes away ... !!

could this be related to problem that was reported with some portscanners some time ago, where the scanner reported an open port 110 on the local machine ??
that was solved with :
[MailScanner]
IgnoreProcess=SuperScan4.exe

[vojtech]

It should be solved by this patch:
http://forum.avast.com/index.php?topic=11400.0#msg96848