Avast WEBforum

Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: plangway on October 24, 2003, 12:46:46 PM

Title: Not able to protect outgoing mail
Post by: plangway on October 24, 2003, 12:46:46 PM
I'm getting Error: 10048 which states "Not able to protect Outgoing mail (SMTP Protocol). Port 25 is already in use, specify another port value

I'm using Outlook 2000 on Windows 2000 Prof operating system. I did a netstat -an and port 25 shows in listening mode, not open??

Can you give me any suggestions?

Paul L.
Title: Re:Not able to protect outgoing mail
Post by: whocares on October 24, 2003, 12:54:58 PM
Hi,
these Links might help you:

http://www.avast.com/forum/index.php?board=2;action=display;threadid=1535
http://www.avast.com/forum/index.php?board=2;action=display;threadid=1519;start=msg9305#msg9305
 ;)
Title: Re:Not able to protect outgoing mail
Post by: plangway on October 24, 2003, 01:20:10 PM
I can send e-mails with attachments no problem. I looked at both the reference post, but could not find a solution. Port 25 appears to be in listening mode, but Avast is reporting that it is in use?

Paul L.
Title: Re:Not able to protect outgoing mail
Post by: igor on October 24, 2003, 01:23:21 PM
I may be wrong, but when it is in listening mode, doesn't it mean that it actutally is in use? (i.e. some other program is listening there)?
Or are you sure that it's avast that is listening?
Title: Re:Not able to protect outgoing mail
Post by: Vlk on October 24, 2003, 01:26:51 PM
If you use Outlook 2K there is no need to use the Internet Mail plugin at all. Please see e.g. http://www.avast.com/forum/index.php?board=2;action=display;threadid=1441#msg8414 for details.
Title: Re:Not able to protect outgoing mail
Post by: vojtech on October 24, 2003, 02:00:04 PM
You can disable the Internet Mail scanner if you use only Outlook 2000: start the Mail Protection Wizard (menu Start->Programs->avast! Antivirus) and choose to remove protection. The Outlook protection will remain active and the warning will not be displayed.
Title: Re:Not able to protect outgoing mail
Post by: plangway on October 26, 2003, 06:22:40 PM
I disabled internet mail in avast, but I'm still receiving the following error meesage upone start up of win 2000 Prof:


"Avast will not be able to protect outgoing mail (SMTP protocol) Error 10048. Port 25 is already in use, specifiy another port value (see section Cooperation with other software in manual setting of mail protection in help)'

I'm using Outlook 2000 and have run the avast mail wizard. I also ran a port scan on my desktop and Port 25 does not indicate being open. In addition, I disabled "Internet Mail" in avast.

Can anyone give me a clue as to why this message is coming up?

Thank You,

plangway
Title: Re:Not able to protect outgoing mail
Post by: Vlk on October 26, 2003, 06:30:30 PM
You need to start the avast Mail Protection Wizard (in the avast group in the Start Menu) and select 'Remove the protection'.

Your Outlook 2K will still be protected.

Vlk
Title: Re:Not able to protect outgoing mail
Post by: Lisandro on October 27, 2003, 01:27:53 AM
You need to start the avast Mail Protection Wizard (in the avast group in the Start Menu) and select 'Remove the protection'.

Your Outlook 2K will still be protected.

Vlk

I cannot believe the user must choose between Outlook 2k and Outlook Express (Internet Mail)  >:(
And what happens if the user want to use both?  ::)
I think that must be another solution  :(
Title: Re:Not able to protect outgoing mail
Post by: Vlk on October 27, 2003, 08:08:25 AM
Quote
I cannot believe the user must choose between Outlook 2k and Outlook Express (Internet Mail)  
And what happens if the user want to use both?  
I think that must be another solution  


Of course it works together, it's just that on plangways' computer the Internet Mail module cannot work without reconfiguration because some other program is already listening on port 25 (i.e. plangway already has a similar program installed on the machie).

Since plangway is only using Outlook 2000 to access his mail, I suggested to prevent the Internet Mail module at all (since it's unnecessary in his Outlook-only scenario, anyway). If he was using some other e-mail client, I'd suggest reconfiguring the SMTP ports of the Internet Mail module instead...

I hope this makes things clearer.

Vlk
Title: Re:Not able to protect outgoing mail
Post by: Lisandro on October 27, 2003, 01:42:05 PM
I hope this makes things clearer.
Vlk

For me, complete clear. Thanks Vlk.
Btw, could you tell us the range for port numbers, I mean, what is the range (from... to...) the user can set for listening ports to use Internet Mail...
Remember I am stupid in these questions...  ;)
Title: Re:Not able to protect outgoing mail
Post by: plangway on October 30, 2003, 12:58:55 PM
As far as I can tell there is no other internet mail module open on my computer. I checked all process in task manager and ran the following Netstat report:

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    0.0.0.0:21             0.0.0.0:0              LISTENING
  TCP    0.0.0.0:25             0.0.0.0:0              LISTENING
  TCP    0.0.0.0:80             0.0.0.0:0              LISTENING
  TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:443            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:1025           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:1026           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:1028           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:1036           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:1099           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:1101           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:1107           0.0.0.0:0              LISTENING
  TCP    127.0.0.1:110          0.0.0.0:0              LISTENING
  TCP    127.0.0.1:143          0.0.0.0:0              LISTENING
  TCP    127.0.0.1:1028         127.0.0.1:1258         TIME_WAIT
  TCP    127.0.0.1:1028         127.0.0.1:1261         TIME_WAIT
  TCP    192.168.2.3:139        0.0.0.0:0              LISTENING
  TCP    192.168.2.3:1099       80.15.249.120:80       CLOSE_WAIT
  TCP    192.168.2.3:1101       80.15.249.118:80       CLOSE_WAIT
  TCP    192.168.2.3:1107       209.51.177.40:443      CLOSE_WAIT
  UDP    0.0.0.0:135            *:*
  UDP    0.0.0.0:445            *:*
  UDP    0.0.0.0:1035           *:*
  UDP    0.0.0.0:3456           *:*
  UDP    192.168.2.3:137        *:*
  UDP    192.168.2.3:138        *:*
  UDP    192.168.2.3:500        *:*
  UDP    192.168.2.3:4500       *:*
  UDP    192.168.2.3:17985      *:*

The only thing I see above is port 25 in listening mode?

plangway
Title: Re:Not able to protect outgoing mail
Post by: vojtech on October 30, 2003, 01:32:12 PM
You can use tcpview to find out what program is listening on which port.

http://www.sysinternals.com/ntw2k/source/tcpview.shtml
Title: Re:Not able to protect outgoing mail
Post by: Hornus Continuum on October 30, 2003, 01:32:56 PM
plangway,

Use the command netstat -ano to add the process IDs to the output list.  Then use Task Manager to identify the process that is listening on port 25.

Regards,
Hornus
Title: Re:Not able to protect outgoing mail
Post by: plangway on October 30, 2003, 01:59:38 PM
Thanks to all that made suggestions. I ran TCPView and found Inetinfo.exe was running as a service using port 25. I disabled it and Avast appears to know be protecting my outgoing mail

Thanks again

plangway
Title: Re:Not able to protect outgoing mail
Post by: Lisandro on October 31, 2003, 01:51:30 AM
You can use tcpview to find out what program is listening on which port.

http://www.sysinternals.com/ntw2k/source/tcpview.shtml


Vojtech, thank you for the link  ;)
Could you answer my posted question? Could you tell us the range for port numbers, I mean, what is the range (from... to...) the user can set for listening ports to use Internet Mail...  ;)
Title: Re:Not able to protect outgoing mail
Post by: vojtech on October 31, 2003, 11:06:52 AM
Port is a 2-byte number, i.e. 0-65535. Some numbers are declared as 'well-known' and some as 'registered' (see http://www.iana.org/assignments/port-numbers (http://www.iana.org/assignments/port-numbers)). But on an ordinary-user computer only few of them are used. You can choose as you like from the ports that are not already used on your computer.
Title: Re:Not able to protect outgoing mail
Post by: Lisandro on October 31, 2003, 12:16:16 PM
Port is a 2-byte number, i.e. 0-65535. Some numbers are declared as 'well-known' and some as 'registered' (see http://www.iana.org/assignments/port-numbers (http://www.iana.org/assignments/port-numbers)). But on an ordinary-user computer only few of them are used. You can choose as you like from the ports that are not already used on your computer.


Thanks again for your information ;)
What does that link do? It seems a list of ports managed by IANA but not mine, I mean, who is connecting their server at which port...  :-\
Title: Re:Not able to protect outgoing mail
Post by: Hornus Continuum on November 05, 2003, 08:11:01 AM
Technical,

The IANA port lists identify known uses for TCP/UDP ports.  "The Well Known Ports are those from 0 through 1023 and on most systems can only be used by system (or root) processes or by programs executed by privileged users."  Their use is standardized, to perform a specific task using a specific protocol.  For example, the FTP and FTP_DATA ports (ports 21 & 20 respectively) are used for FTP transfers, and all FTP servers expect FTP clients to use these ports in a standard fashion to establish connections and perform a transfer.

The Registered Ports are those from 1024 through 49151.  "The Registered Ports are listed by the IANA and on most systems can be used by ordinary user processes or programs executed by ordinary users."  Product and service developers register their products to use these ports.  Applications using these ports may use standard or proprietary protocols.  Examples are TCP/UDP ports 1214, which are registered for use by the KAZAA network.  Rights to use these ports are not exclusive evidently as IANA indicates that TCP/UDP ports 4000 are used both by Terabase and ICQ.

The Dynamic and/or Private Ports are those from 49152 through 65535.  These ports are for use in situations where the port on which a connection is made changes with each use or in private networks.  Applications using these ports may use standard or proprietary protocols.  For an example of dynamic ports, a client makes a connection to a static port, and the server examines a list of ports that it services and responds with an available port to be used for a transaction.  An example of private port usage: an equipment manufacturer provides for Internet connections using a private port for firmware updates.

Using the IANA port list won't tell you exactly what is going on with a particular connection, but it can provide a clue as to whether it is legitimate or not.  For example, if your firewall log indicates that a connection made by an application, whose executable you don't recognize, is using TCP port 1352, a check with the port list will show you that this port is registered for use with Lotus Notes.  If you are using that application, then you can probably relax, but if not, it may be an indication that your computer is infected with some malware, and you should do some investigating.

Regards,
Hornus
Title: Re:Not able to protect outgoing mail
Post by: Lisandro on November 05, 2003, 11:49:42 AM
Thanks for your time, patience and knowleagde...
I'm becoming to understand a little about ports and communications...