oreilly.comSafari Books Online.Conferences.


Using Qpsmtpd
Pages: 1, 2, 3, 4

Replacing Your Current SMTP Server

The simplest (and least scary, for those who worry about those kinds of things) strategy for installing qpsmtpd is to change your current SMTP server to run on a different port, and simply have qpsmtpd forward to that SMTP server after its spam filtering. That way you get the best of all worlds--you keep your current stable email environment, and you get all the spam-filtering goodness that qpsmtpd brings.

First, create a qpsmtpd configuration file for the plugins that you want to load. In your qpsmtpd directory, edit the file config/plugins to contain the following lines:

count_unrecognized_commands 4

# this plugin needs to run after all other "rcpt" plugins

# we'll turn this on later

# deliver to localhost:2525
queue/smtp-forward localhost 2525

If you are not currently running Qmail, you will also need to create the file config/rcpthosts, containing a list of domains for which you currently receive email. Qmail users can relax, as qpsmtpd will read /var/qmail/control/rcpthosts by default.

# rcpthosts - who I receive email for
# put your domain name in here

Make sure you do a simple test of this new configuration as shown above.

Next, convince your current SMTP server (qmail, postfix, exim, or whatever you currently use) to run on a port 2525. I'll leave that up to you to work out, as every SMTP server configures this differently. If you get stuck, ask on the qpsmtpd mailing list for help.

To run qpsmtpd on port 25, pass that option on the command line:

$ ./qpsmtpd-forkserver -u $USER -p 25

That's all there is to it, so test it. The best testing tool for SMTP servers is swaks (though it needs the swaks TLS debugging patch if you intend to test TLS). To use it, try the following command:

$ swaks -t -f -h \
    foo -s localhost

If everything is successful, you should see:

<-  250 Queued! 
 -> QUIT
<-  221 closing connection. Have
a wonderful day.
=== Connection closed by foreign host.

Now, if you have a working installation of SpamAssassin and a running spamd daemon, feel free to enable the SpamAssassin plugin in config/plugins and restart the server. By default this will just add headers to the email, but see perldoc plugins/spamassassin for details on how you can get it to reject mail over a certain threshold.

Pages: 1, 2, 3, 4

Next Pagearrow

Sponsored by: