Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: Reiner on March 29, 2010, 02:27:37 PM
-
High,
I've noticed, that Avast seems to have changed the TCP Ports listening for mail communication. Is this correct?
On my system:
3949 seemt to be the POP3 proxy
3950 seems to be the IMAP proxy
3951 seems to be the NNTP proxy
Is this correct?
I need the ports to (re)configure my personal firewall.
Thanks
-
Avast! 5 uses the same TCP ports as 4.8-see attachment. Those look like the random ports used at the other end of the internal proxy.
-
On my system, the ports 12110, 12143 and 12119 are no longer listed as listening ports. 12080 is still there!
Instead of the 12xxx ports, I see the 39xx ports...
The 39xx ports are listed as listening on my system...
I've realized the port change the first time about 3 or 4 days ago...
-
What OS are you using? How are you identifying the ports? You can use something like currports (http://www.nirsoft.net/ ) to confirm you are using something different, but the attachment is taken directly from my OA firewall for 5.0.462 Pro under Vista.
-
I'm using XP pro SP3. I used CurrPorts to identify the listening ports.
-
Haven't seen other reports of it. And I don't have new ports. ??? Are you using build 462?
-
I'm a bit puzzled myself. On my wife's system, 12110, 12119 and 12143 are used.....
Yes, I use 5.0.462
-
Could you be using anything else that incorporates a local proxy in your system? What is your firewall and other security software? email client?
-
I'm a bit puzzled myself. On my wife's system, 12110, 12119 and 12143 are used.....
Yes, I use 5.0.462
strange...??? did u eventually block the other ports b4, so avast is just trying 2 get around that?
asyn
-
I don't think, that it is something else, as a telnet to localhost on port 3949 shows up as: +OK avast! POP3 proxy ready. Same for 3950 (IMAP) and 3951 (NNTP).
I made no changes to the firewall, so the firewall can't be the problem...
-
very strange, indeed... ???
never experienced a similar behavior on any sys with avast, so sorry can't really help with that one.
only guess would b as posted b4 that u blocked the original avast ports, but as u didn't - strange. ???
but at least it works, if i get u right...?!! :)
asyn
-
yes, it seems as Avast scans incoming email on POP and IMAP.
But it is really strange, as I can't figure out, why avast uses 39xx ...
-
is there maybe some other prog using the usual avast ports or is there no traffic/connection at all?
-
Nothing...
12110, 12143 and 12119 seems not to be used...thats what is really strange
-
Maybe time to try an uninstall and reinstall. You seem to have a unique configuration. ::)
-
more than that...!!! at least 4 me... ;)
nice day, anyways! :) maybe someone stumbles over with better ideas...
i would b really interested in solving that puzzle. ;D
asyn
-
what puzzles me is that until a few days ago, avast used 12xxx. Then i realized, that avast was not running. After i pressed repair/update, avast was running ok, but the ports had changed...
-
so, that's a starting point.
maybe the repair moved the ports, as they were maybe just in use at time of repair...?!!?
asyn
-
Very strange... I did, what everybody does, when something is not longer working as expected (remove / reinstall) and Avast uses again ports 12xxx.
Now it would be interesting, what caused Avast to abort using 12xxx and start using 39xx. It seems as Avast just used new ports for the whole mail-sacnning-subsystem (12080 stayed!).
Maybe one of the Avast developers could bring some light into this issue...