[TriLUG] SpamAssassin as a daemon

[Rick DeNatale]

On Fri, 2004-07-16 at 09:44 -0400, Jeremy Portzer wrote:

> So, the developers invented the spamc/spamd combination.  In order to
> reduce the processing time for each message, much of the spamassassin
> code is kept loaded in memory at all times, through the spamd binary. 
> Then, the spamc binary is the "client" used to connect to spamd.  But
> this isn't a daemon like httpd or ftp that provides services to other
> computers on your network, it's simply an internal thing that makes
> spamassassin run better. 

Well, actually spamd is a daemon pretty much like httpd or xinetd. It
listens for requests via a socket, by default on port 783. Out of the
box it only allows requests from localhost, but it's perfectly happy to
serve spamc either on your computer or another, as long as you tell it
to allow access from those ip addresses using the option -allowed-ips.
The default for spamc is to connect to spamd on localhost, but by using
the -d option you can point it to spamd running somewhere else.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://www.trilug.org/pipermail/trilug/attachments/20040716/3284138d/attachment.pgp>