Randy,

SpamFilter is a very *simple* application. It uses no registry entries, and no DLLs placed in obscure directories. You can literally copy and paste SpamFilter's directory from one server to another and the program will run.

This said, if you can zip and email us your SpamFilter's activity logfile for today at support at logsat dot com we'll take a look.

If you wish to perform some troubleshooting yourself, first ensure that no other application on the server is using port 25. Only one Windows application can use one port at a time, so if the port's taken, SpamFilter won't be able to use it. To check, stop SpamFilter (and ensure you do not have multiple instances of SpamFilter running, check the Task Manager to ensure there are no SpamFilter processes running). Then from an MSDOS prompt type

telnet aaa.bbb.ccc.ddd 25

where aaa.bbb.ccc.ddd is the IP address SpamFilter should be listening on. If you get a connection, or even just a black screen, then there is "something" using port 25, and you'll need to make sure that this "something" is not running before SpamFilter starts.

Next, start SpamFilter, and issue the same command. You should be receiving SpamFilter's welcome banner, and in the activity windows in SpamFilter you should see your connection attempt. If this does happen, then SpamFilter is working and is receiving connections correctly. If you do not see any other traffic in the activity window in SpamFilter, I'd recommend you check your network infrastructure to ensure SMTP traffic is indeed being routed from the internet to SpamFilter's server, as it would not seem to be the case here.