Avast tcp port conflict

[johnnynine]

What are the fixed and dynamic tcp ports used by Avast?

I recently had a user of a software package I work on indicate that the software would not start up. We narrowed it down to Avast listening on a couple of the same tcp ports.

12993 and 12995

Are these fixed ports or can they be configured to a different port #?

Also when did these ports come into use? I was using avast with our software about a year ago and did not have any conflicts.

Thanks,
Johnny

[Hermite15]

these ports, 12995 and 12993 are virtual ports used to scan mails on POP and IMAP. Problem is they should be 12110 and 12143 instead, to allow the scanning of unencrypted data. My guess, but that's just a guess, is that your email client isn't configured properly, resulting in avast listening to virtual ssl ports.
 Solution: change your email client settings to non-ssl ports to allow avast mail scanner to do its job. Just use 143 (IMAP) or 110 (POP).

[johnnynine]

Thanks for the reply.  We are trying to assess the likelihood that other Avast users would run into the same port conflict with out software.

It sounds like the 12995 and 12993 ports are assigned based on some algorithm or somehow related to the email ports. Can you please explain this relationship or point us at any related documentation?

Thanks,
Johnny

[vojtech]

Avast uses these ports for mail scanning purposes:
- 12025, 12110, 12119, 12143
- 12465, 12563, 12993, 12995 (from avast v5, for warning about SSL)
They can be changed in EmailShield.ini file by inserting such lines under [EmailScanner]:
PopListen=127.0.0.1:12110
PopListenSSL=127.0.0.1:12995
For SMTP, NNTP and IMAP accordingly. The default is always 12000 + respective standard port, so 12993 and 12995 corresponds to ImapListenSSL and PopListenSSL. Restarting the Mail shield is needed after the change.

[johnnynine]

Thanks guys, that's the information I was looking for.

Johnny