Print Page | Close Window


Printed From: LogSat Software
Category: Spam Filter ISP
Forum Name: Spam Filter ISP Support
Forum Description: General support for Spam Filter ISP
Printed Date: 20 October 2017 at 6:53am

Topic: InstallProblems
Posted By: Heinrich
Subject: InstallProblems
Date Posted: 28 July 2009 at 3:55am
Good day I am writing from Germany. I am your software SPAMFILTERISP to test this on my mail server only. My system runs x32 System Microsoft Server 2003 without error. On a server running Windows Server 2003 Standard x64 Edition, I have a problem. Your software does not start the service. Can you help me. Sorry, I hope my English is understandable, but I write too little.

Posted By: LogSat
Date Posted: 28 July 2009 at 4:07pm

SpamFilter will work on 64bit platforms. If you can please zip and email us at support at SpamFilter's activity logfile for a day this happened, along with an export of the Windows "Application" and "System" Event Viewer logs, we'll try to see what is going on. Please also include a copy of your SpamFilter.ini file.

Roberto Franceschetti" rel="nofollow - LogSat Software" rel="nofollow - Spam Filter ISP

Posted By: LogSat
Date Posted: 29 July 2009 at 6:11pm

We see errors similar to the following in your logs:

07/28/09 22:57:21:506 -- Exception occurred during PerformPostStartupTasks: Could not bind socket. Address and port are already in use.

The error indicates that SpamFilter is not able to listen for traffic on port 25 (the SMTP port), as another application is already using that port. This will indeed cause problems, as SpamFilter will not be able to receive emails properly. A common cause of this is running SpamFilter's service, and then also opening another instance of the "Standalone" SpamFilter application, which is what is happening in your case (we verified this from your screenshot).

I'm including a section of our manual below, which explains how SpamFilter can be executed. 


SpamFilter Service / Console Application

SpamFilter can run in two different ways.
  • As a Windows service (the most common - SpamFilterSvc.exe).
  • As a standalone application using SpamFilter.exe. This is mostly used for troubleshooting and testing purposes.
If SpamFilter is already running as a service, subsequently running the standalone application (SpamFilter.exe) will open a new instance of SpamFilter, it will not be the GUI for the service. This will most likely create a conflict, as two applications cannot bind to the same port on a server.

Please note that the SpamFilter service does show display a GUI (launched from an icon in the tray bar), but if you are accessing a Windows 2000 server remotely using Terminal Services will not be able to display the GUI. This is because Terminal Services in Windows 2000 is not able to display the server's physical console.

Looking at the physical server's screen, or using a product like PCAnywhere, DameWare, VNC etc that displays the actual screen will reveal the console.

Microsoft fixed this limitation in Windows 2003. In this version of the operating system, Terminal Services allows RDP clients to connect to the server's console.

Some Terminal Services clients have a checkbox in their settings that forces them to connect to the console. In the Remote Desktop client that ships with Windows XP, Microsoft (in)conveniently decided to not make this checkbox available. In this case, to view the server's physical console, you'll need to invoke Remote Desktop from the command line as follows:

mstsc –/console

Please note that some newer versions of the Terminal Services client and in Microsoft Vista, the command is:
mstsc /admin

Roberto Franceschetti" rel="nofollow - LogSat Software" rel="nofollow - Spam Filter ISP

Posted By: Heinrich
Date Posted: 30 July 2009 at 1:42am
Smile Thanks for your help

The system is now working flawlessly !


Print Page | Close Window