| Pre-installation Review and Notes: |
 |
| The description that follows covers the specific steps installing JSpamFilter with the graphical installation assistant.
The choices for a the non-graphical installation are the same, though you don't have to follow any particular order.
|
 |
| Keep handy the path to your JRE executable (i.e., the "server" jvm.dll) that you noted in the Pre-Installation step (e.g., C:\j2sdk1.4.2_04\jre\bin\server\jvm.dll). Note this because during the installation process you will need to confirm the location of the JRE and the installer may not "guess" the right location.
|
 |
|
If you use the non-graphical installation, note that JSpamFilter is distributed as a Java Archive (.jar)
file, and accepts one command-line parameter, which should be the full path to
its configuration file. If no file is specified on the command line, the "current"
directory will be checked for a file called "JSpamFilter.conf".
|
 |
NOTE: DURING THE INSTALLATION PROCESS, YOUR MAIL SERVER MUST NOT BE RUNNING ON THE SAME IP ADDRESS AND PORT THAT JSPAMFILTER IS TO LISTEN ON!
IF YOU HAVE QUESTIONS, SEE THE NOTES AT THE BOTTOM OF THE PREVIOUS SECTION.
|
 |
| JSpamFilter is going to be "inserted" into the mail flow and if your mail server is running, JSpamFilter will not be able to bind to port 25 during the installation process. |
 |
- JSpamFilter now has a graphical Installation Assistant for any windowing system that supports Java. The Installation Assistant speeds the installation process by ensuring that all configuration parameters are valid (e.g., verifies that a mail server is running at the talk IP and port specified, etc.).
You will need to be able to supply the following pieces of information during the installation:
IP address JSpamFilter is to listen on
IP address the Mail Server is listening on
Port Number JSpamFilter listens on (default is 25)
Port Number the Mail Server listens on (default is 26)
Please note that the talk and listen IP addresses, port numbers, or both must be different.
|
|
To complete tne installation, you will need either a permanent, non-expiring JSpamFilter license or a current, non-expired
Trial License to run JSpamFilter. Trial Licenses are fully-featured, time-limited licenses, you can request a free, no-obligation
Trial License by filling out the request form here.
|
 |
|
Step Zero: [Click here to go back to the top of the page.]
Start the graphical installer by double-clicking on the JSpamFilter_Windows.exe to begin the installation process.
The pre-installation archive decompressor will ask you to confirm the installation location.
The default location is:
c:\jspamfilter
Either accept this location by clicking yes or select a different location (note that you will need to remember where you installed JSpamFilter).
If you are installing JSpamFilter "manually", create a configuration file named "JSpamFilter.conf". See the "Configuration
Options" and "Sample Configuration" sections of this manual for
more information.
|
 |
|
Step One: [Click here to go back to the top of the page.]
After the greeting page, the Installation Assistant will begin the installation process by prompting you for the IP address
on which you want JSpamFilter to listen (this will be the IP addresses from which mail could be received).
1. What is the IP address you want JSpamFilter to listen on?
The current value is: all
 |
The JSpamFilter Configurator will give you the option of either verifying the current choice or accepting the default.
If you are not sure, use the verify function to check that the default selection (or whatever you have chosen) works.
|
The default value for the "listening" IP address is:
all
And you should leave this choice as it is.
This means that you will be listening for messages sent from any address on the Internet. If you choose to block certain
addresses or blocks of addresses, you should do so explicitly later using the block parameter, discussed in detail in Seciont
Block=(IP address or block)
 |
Additionally, while JSpamFilter can be installed on any machine in the mail flow, it
needs to be the "first link in the chain" in that it needs to be able to "see" the incoming mail as it arrives in
order to use the various DNSBL and SURBL lookup functions. That is, for JSpamFilter to determine whether a sending
server is on a DNSBL or SURBL list, JSpamFilter has to be able to "see" the IP address from which incomiing mail is
being sent.
|
|
 |
|
Step Two: [Click here to go back to the top of the page.]
2. What is the TCP Port number you want JSpamFilter to listen on?
The current value is: 25 (Simply press your key to accept the current value.)
The default value is:
25
and you should leave this value as port 25 is the standard port on which SMTP mail is sent. The mail servers
sending you mail will be sending the mail on port 25, so you should leave this value so that JSpamFilter is
listening for incoming connections.
 |
If your mail server is still listening on this port, you will receive the following error message: |
* I am unable to bind to that IP address and port number.
* This is usually because the mail server is still listening
* on that port, and only one process is allowed to.
* Please verify that the mail server is NOT listening on that port.
* (Response from socket bind was:
* java.net.BindException: Address already in use: JVM_Bind)
|
 |
THIS WILL HAPPEN IF YOUR MAIL SERVER IS RUNNING ON THE PORT TO WHICH JSPAMFILTER IS TRYING TO BIND. |
|
 |
|
Step Three: [Click here to go back to the top of the page.]
3. what is the IP address you want JSpamFilter to "talk" to?
The current value is: all (Simply press your <enter> key to accept the current value.)
The default value is:
all
This represents the IP address which the mail server is listening to. You can leave this value at all, but you may want to
change it to the specific IP address of your mail server (e.g., an internal address). See the notes in the next step.
|
 |
|
Step Four: [Click here to go back to the top of the page.]
4. What is the TCP Port number you want JSpamFilter to Talk on?
The current value is: 26
The default value is:
26
Possible error:
I am unable to connect to a mail server at the IP and port entered.
This is usually because there isn't a server there!
You can also try to connect to the mail server using the telnet command:
telnet localhost 26
Please verify that the mail server is listening on that port.
(Response from socket connect was:
java.net.ConnectException: Connection refused: connect)
Change the mail server to listen on port 26, if you'll be running JSpamFilter
on the same machine as the mail server. Notes on changing the "listen"
port on various mail servers can be found here.
 |
You may have to go back and change the "Talk" IP address of your mail server from "all" to the specific IP address of your mail server.
(Note: the IP address of the mail server is the IP address that JSpamFilter "talks" to).
|
Where XXX.XXX.XXX.XXX is the IP address of your mail server.
|
 |
|
Step Five: [Click here to go back to the top of the page.]
5.) Please paste your one- or two-line license key into the blank below.
If you license key includes an expiration, you must paste both lines.
Paste your JSpamFilter License Key into the space provided (note: window may resize after you have pasted the information;
this is harmless, just resize back and continue).
|
 |
|
Step Six: [Click here to go back to the top of the page.]
6.) What is the full host name of your mail server?
Substitute your mail server's fully qualified host name (e.g., machinename.domain.com) for the provided value.
|
 |
|
Step Seven: [Click here to go back to the top of the page.]
7.) What domains are local to your mail server?
Enter at least one domain served by, that is local to, your mail server (e.g., the primary domain name).
Step Seven, Cont'd: [Click here to go back to the top of the page.]
What is the full path to your filter file?
Make sure that the stated default path is correct or change it to the path to your filter file (e.g., this was
the directory in which JSpamFilter was installed).
Step Seven, Cont'd:
Confirmation of correct path to filter file
Step Seven, Cont'd:
Congratualations!
You have successfully completed the basic configuration!
Now, we install the network service and we're done!
Step seven, Cont'd:
The JSpamFilter Configurator asks if you would like to JSpamFilter as a service.
You should answer "yes".
|
 |
|
Step Eight: [Click here to go back to the top of the page.]
What is the path to your jvm.dll?
Click "Verify" to determine if this is the correct fully-qualified path to the server jvm.dll.
Step Eight, Cont'd:
If you see this error, it means that the JRE is not where the Configurator thinks it should be.
 |
If you recieve this error message, compare the given value of the full path to the server JRE (i.e., the "server" version of
jvm.dll) to the path you noted in the pre-installation checklist in the previous section Part 3 (Pre-Installation Checklist).
|
|
JSpamFilter uses environment variables to "guess" where your JRE is located.
Sometimes the JVM doesn't report this location correctly.
|
We've noticed that the environment variable will report that the path is:
C:\Program Files\Java\jre1.5.0_02\jre\bin\server\
When it is actually:
C:\Program Files\Java\jdk1.5.0_02\jre\bin\server\
Step Eight, Cont'd:
Substitute the correct path to the JRE

|
NOTE: When you download the installer from Sun Microsystems, make sure you download the Java "Software Development Kit"
SDK (formerly called "JDK" or "Java Development Kit") and not just the JRE as the JRE does not include the server version of jvm.dll.
|
|
 |
|
Step Nine: [Click here to go back to the top of the page.]
The Configurator confirms that it found JSpamFilter.jar
|
 |
|
Step Ten:
The Configurator confirms that it found JSpamFilter.conf
|
 |
|
Step Eleven:
The Configurator confirms that it found JavaService.exe
|
 |
|
Step Twelve:
JavaService is being installed
|
 |
|
Step Thirteen:
Woo-hoo! We're Done!
|
 |
|
Step Fourteen:
Thank you for using JSpamFilter! We do appreciate it!
|
 |
|
Addendum:
Step Fifteen:
Configure your system to start JSpamFilter when the server starts.
Instructions for this are platform-specific:
See Section 13: Platform Specific Installation Instructions.
|