Appendix C. Connecting to SpamSpector Remotely
SpamSpector is designed as a personal mail filter that will run on same local machine as your email client. It contains many features that specifically tailored to this way of working.
However, some people have expressed a wish to run SpamSpector as a service for a local network. Although this isn't advised, it is now possible. But before doing it, please consider:
- SpamSpector has a GUI, and pops up error boxes in various circumstances.
- The auto-whitelist has privacy implications if SpamSpector has more than one user.
- Tagging mail on retrieval (which SpamSpector does) is not the most efficient way of doing it. A far better solution is to tag mail when it is received by your mailserver. If you're at the stage of running SpamSpector on a local network, you probably have a mailserver; investigate the spamfilters that can be installed on it.
If after reading this you still want to be able to connect to SpamSpector from a remote machine, here's what to do. Go the advanced pane of the Options dialog and choose "I.P. configuration" - a window will pop up. Change the I.P. address setting from 127.0.0.1 to the I.P. address of the machine on which SpamSpector is running. Now, in the box below this, type the I.P. addresses of the machines that will be permitted to connect to SpamSpector, one on each line. You can specify a range of I.P. addresses using either the network prefix notation (e.g. 127.0.0.1/24) or by giving the start and end of the range (e.g. 127.0.0.1-127.255.255.255). But be careful if you do this - you don't want to accidentally allow external machines to connect to SpamSpector!!!
Future versions of SpamSpector will be able to run as a service on Windows NT/2000/XP. For now, SpamSpector can be made to run as a service using a third-party application called FireDaemon.
| Next Chapter: Adding Extra DNSBL Lists | Table of Contents | Previous Chapter: Command-Line Switches |