In this setup, greylite responds directly to clients, and forwards the TCP connection to the server for delivery when messages are passed.
tar xjvf greylite-VERSION.tar.bz2 cd greylite-VERSION
make all install
Several arguments can be appended to the command line for enabling compilation of different components. The general form is:
make all install ARGUM1 ARGUM2 ARGUM3 ...
WITH_GEOIP=yes enables support for GeoIP in suspicion rules.
WITH_DNSBLENV=yes enables the compilation of the dnsblenv module.
WITH_UCSPI2SOCKET=yes enables the compilation of the ucspi2socket module.
In greylite ≥ 3.0 the backend for storing data can be chosen. By default, SQLite is used. The following can be specified for changing this:
tcpserver -vR -x greylite.cdb BINDIP BINDPORT /usr/local/bin/greylite /usr/local/bin/ucspi2socket UPSTREAMADDR [UPSTREAMPORT]replace BINDIP and BINDPORT with the IP address greylite should respond to, respectively. Replace UPSTREAMADDR and optionally UPSTREAMPORT with the IP address and port of the upstream SMTP server that greylite should connect to.
:allow,GREYLIST=""Compile this ruleset into a CDB file with:
cat rulesfile | tcprules greylite.cdb /tmp/greylite.123
Done.