Byteplant Forum

Home » CleanMail Support » CleanMail Server Talk » extra port usage?
extra port usage? [message #889] Thu, 04 November 2004 17:42
tiger1vic
Messages: 9
Registered: November 2004
Junior Member
What does the following log entry mean when NST is started:

Nov 4, 2004, 08:29:44 No Spam Today! Service V2.0.1.1 Freeware listening on :25
Nov 4, 2004, 08:29:44 No Spam Today! Service V2.0.1.1 Freeware listening on :8086

Is NST doing something else on port 8086? If so, what is it used for?
Re: extra port usage? [message #890 is a reply to message #889] Fri, 05 November 2004 14:06 Go to previous message
support
Messages: 919
Registered: April 2004
Senior Member
> Is NST doing something else on port 8086? If so, what is it
> used for?

This is the monitoring port. The admin application connects to this port to receive monitoring data. See chapter 5 of the manual.



Customer Support
Byteplant GmbH
Re: extra port usage? [message #891 is a reply to message #890] Sun, 24 April 2005 10:57 Go to previous message
ninad
Messages: 4
Registered: April 2005
Junior Member
I am evaluating this software. However we use the Helm control panel software which uses Port 8086 for administration. It is not possible to change the port of Helm at this stage, since it is actively used by a number of our users.

Moreover, Nospamtoday tries to bind to all the interfaces of the server. If an option was available to selectively bind to a particular interface, the problem could have been avoided, by not letting Helm use other interfaces.

Is there a way to change the port number or interface setting in Nospamtoday?

Ninad
Re: extra port usage? [message #892 is a reply to message #891] Mon, 25 April 2005 10:54 Go to previous message
support
Messages: 919
Registered: April 2004
Senior Member
At present, this setting is not accessible using the admin app. But to change the IP address and port number of monitoring, you can edit the nospamtoday.cf file (located in the installation directory) with a text editor.

To use port 8087, add the following line in the [.../MonitornigPort] section:

IncomingPort="8087"

In the default setting, monitoring binds to the localhost interface, port 8086.



Customer Support
Byteplant GmbH
Re: extra port usage? [message #893 is a reply to message #892] Mon, 25 April 2005 11:12 Go to previous message
ninad
Messages: 4
Registered: April 2005
Junior Member
Thanks, will do that. But I am not sure who/what monitors this port.

Is it safe to change this port without causing any side effects in the operation of NST?

Regards,
Ninad
Re: extra port usage? [message #894 is a reply to message #893] Mon, 25 April 2005 11:25 Go to previous message
support
Messages: 919
Registered: April 2004
Senior Member
A TCP connection to the service's monitoring port is used by the admin app, to fetch statistics data from the service.

If you change the port, the service will bind to the other port. Once you restart the admin app, it reads the same cf file and knows that is should use some other port, not the default port, to get statistics data. So everything is the same, only the port actually used is different.



Customer Support
Byteplant GmbH
Re: extra port usage? [message #895 is a reply to message #892] Mon, 25 April 2005 17:25 Go to previous message
ninad
Messages: 4
Registered: April 2005
Junior Member
The given steps worked fine. However I noticed that after I edited settings of Proxy Port / Filters from the Admin tool, the Port setting done by me manually disappeared, and NST tried to open the default 8086 port again.

Regards,
Ninad
Re: extra port usage? [message #896 is a reply to message #895] Tue, 26 April 2005 11:40 Go to previous message
support
Messages: 919
Registered: April 2004
Senior Member
This can happen if you don't close and restart the admin app after you edited the config file with the editor. So, in the future, it shouldn't happen.



Customer Support
Byteplant GmbH
Previous Topic: inconsistent header info
Next Topic: No Spam Today! Slowness
Goto Forum:
  


Current Time: Wed Dec 07 13:26:13 CET 2016