On Fri, 2010-07-30 at 12:57 -0400, Bowie Bailey wrote: > On 7/30/2010 12:14 PM, Adam Moskowitz wrote: > > 3) While I could fire up a non-standard spamd, throw messages at it, > > then close it down when I'm done, I'd rather not add the complication of > > managing the start-up/shut-down of a daemon. > Also: if you're not doing your analysis on the main mail handling server, install a copy of SA where you're working, configure it to suit and do as Bowie says to start and stop it. I use a similar setup to develop rules without interfering with the 'live' SA.
If you have to do your analysis on the main mail server, do the following to prevent to two copies of spamd from clashing: cd /etc/init.d cp spamd spamd_nonstd # # make changes to spamd_nonstd so it gets configurable values # from /etc/sysconfig/spamassassin_nonstd rather # than /etc/sysconfig/spamassassin_nonstd and edit # /etc/sysconfig/spamassassin_nonstd to suit. # # Now use the command: # service spamd_nonstd start|stop|status # # to control your private non-standard spamd # > I still say the simplest thing to do -- and the thing that would make > the most difference is to use spamd. > Agreed. Setting it up this way is fairly easy to do (dead simple if you can run your SA on a different computer) and, once done, is pretty much a 'done and dusted' thing. Martin
