Using and installing the original
The current versions of
The modification is actually quite simple (as in not a lot of code) and elegant (IMHO). Since the IP address, host name and host info were already gathered by tcp_env (required by original
Yes. It is step 2 of the installation procedure outlined below.
This version of
Since the original ucspi-tcp is known valid code, if you have any problems compiling that, you will need to make the required adjustments to your server before you will be able to compile my source code. Configuring your server to be able to compile programs is beyond the scope of this FAQ. However, you may want to start with the following web site to get help on configuring your server to compile the ucspi-tcp programs (which should be enough to compile the modified
http://cr.yp.to/ucspi-tcp.html (opens in a new window)
First, we change to our work directory, download the original ucspi-tcp, expand it and change to the directory that was created:
Then compile the original
Note: Do not install the ucspi-tcp files (i.e. do not follow the ucspi-tcp instructions to setup or check).
If the files compiled without error swap out the original
If that compiled without error you should get something like:
Now, in order to proceed with the install steps above, we will replace the binary that was downloaded with the newly compiled program:
Proceed to verify that everything worked and install the program starting with Step 2 in the install process above.
Below are the two test entries generated by the test e-mails sent in Step 4 of the install procedure.
This is what each part represents:
In the examples above both hosts include their ID but do not include any info when they connect and attempt to transmit the message. You will find that many SPAM servers do not include either the ID or the info. In the event that the ID or info are not submitted, a single hyphen is inserted to allow for easy reporting (i.e. each entry is a fixed number of columns).
Additional notes on log entries:
If relaying is allowed on your server (not advised), all messages received directly from the mail client is also put through the RBL tests (it is just another smtp connection as far as the server is concerned). So, if your clients/users start to complain about excessively long smtp delays, or possibly even time-outs, you may need to remove one or more of the RBL servers.