Hi, the mailserver is running on port 125. but even if port 25 would be blocked ASSP should still create the socket on port 55555 for the web interface.
The usual mistake when both sockets cannot be created is that there is second ASSP instance running, which is no the case since there is nothing in the task manager and i cannot telnet the 25 and not telnet the 55555. thats why I focus on the perl side, because I had this setup already running like 2 months and maybe any windows or other update or something simmilar prevents perl from creating the sockets. Florian Barry Bahrami wrote: > > " > Are you sure your mail server is not listening on port 25? If assp is > listening on port 25 (it should be) then your mail server needs to be on > another port. You route the data from port 25 to the mail server port in > the assp 'network setup'. Have you done this? It sounds like your mail > server and assp are both fighting for the same port. > > Barry > > -- View this message in context: http://www.nabble.com/create-server-socket-problem-tf4289969.html#a12222867 Sent from the assp-user mailing list archive at Nabble.com. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
