> Looks like you really need to go back and actually read the docs, and > readme file etc, and come back and have another go. spamassassin is > spamassassin. spamc is spamc.
That's actually part of the problem. I've had a hard time finding anything I can read except the readme's and the perldoc. If you can point me at some good URL's for reading I'll gladly do that. > In particular check out the man pages for spamassassin, spamc, and spamd. Checked out spamassassin before. It doesn't really explain the roles of spamc or spamd or how they relate. Perhaps a good candidate for a future whitepaper? > To use spamd you need to have spamd running all the time - usually by > starting it in one of your system init scripts. I use redhat so I copied > the sample redhat init script over, customized it, and use that to make > sure spamd starts when the server boots. Yep, it does that. > Then you'll want to change your procmail file to call spamc instead of > spamassassin. (It's faster to include the full path to spamc by the way) OK, so by calling spamc does it call the running spamd in the background? Can someone explain the relationship of them or point me in a direction of good reading. ------------------------------------------------------- This SF.net email sponsored by: Enterprise Linux Forum Conference & Expo The Event For Linux Datacenter Solutions & Strategies in The Enterprise Linux in the Boardroom; in the Front Office; & in the Server Room http://www.enterpriselinuxforum.com _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
