"Running as service" mode breaking. : MAS,SpamFilter does not use registry...

Sat, 10 Nov 2007 16:37:46 +0000

Author: LogSat
Subject: 6289
Posted: 10 November 2007 at 4:37pm

MAS,

SpamFilter does not use registry entries (other than the one to make it appear in the "Add/Remove Programs" and the one for the Windows Service). All of the files used by SpamFilter are contained within the "SpamFilter" installation directory. For this reason, uninstalling/reinstalling usually has no effect, and there are usually other problems that are lingering if that procedure *appears* to have solved the issue.

The most common problem consists in running multiple versions of SpamFilter concurrently (usually running the service and the standalone version at the same time), or in having another SMTP application (either a mail server or an antivirus server that also protects emails) running along with SpamFilter.

Please the following section of our manual for some things to consider when running SpamFilter, and possible problems with Terminal Services.

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.

IfSpamFilter is already running as a service, subsequently running thestandalone application (SpamFilter.exe) will open a new instance ofSpamFilter, 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 servicedoes show display a GUI (launched from an icon in the tray bar), but ifyou are accessing a Windows 2000 server remotely using TerminalServices will not be able to display the GUI. This is because TerminalServices in Windows 2000 is not able to display the server's physicalconsole.

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

Microsoft fixed this limitation in Windows2003. In this version of the operating system, Terminal Services allowsRDP clients to connect to the server's console.

Some Terminal Services clients have a checkbox in their settings thatforces them to connect to the console. In the Remote Desktop clientthat ships with Windows XP, Microsoft (in)conveniently decided to notmake this checkbox available. In this case, to view the server'sphysical console, you'll need to invoke Remote Desktop from the commandline as follows:

mstsc -console

"Running as service" mode breaking. : v.3.5.4.718 standard version,...

Fri, 09 Nov 2007 12:53:14 +0000

Author: MAS
Subject: 6289
Posted: 09 November 2007 at 12:53pm

v.3.5.4.718 standard version, On the settings tab, service mode would keep breaking and thereby causing the mail flow to quit unless logged into the console.

Several service restarts and mode changes occurred to fix it, yet would keep reverting back to stand alone and not running as a service.

Finally, it took a complete uninstall and reinstall to fix. Seems to be running smooth for the last 12 hours. Problem cropped up yesterday, have been running this version since it's release with no problems.

Anyone else had this happen?

Spam Filter ISP Forums : "Running as service" mode breaking.

"Running as service" mode breaking. : MAS,SpamFilter does not use registry...

"Running as service" mode breaking. : v.3.5.4.718 standard version,...