On Fri, Sep 24, 2004 at 06:12:53PM +0100, Anthony Edwards wrote: > On Fri, Sep 24, 2004 at 03:04:58AM +0100, Anthony Edwards wrote: > > > I removed all SpamAssassin files earlier this evening and re-installed > > using cpan. With hindsight, I believe I could have simply done what > > you have suggested above. I run a SuSE 8.2 system, and persuading > > manual configuration of startup script changes to co-exist with SuSE's > > YaST tool created configurations is far from trivial, so I shall be > > sticking with /usr/bin/spamassassin for the time being. > > In fact, it's easy, or would be if the script at: > > http://kmail.kde.org/unsupported/spamd > > Actually worked properly on SuSE 8.2. Unfortunately, it doesn't seem > to, quite. If it did, it would be a simple matter of downloading and > copying it to the /etc/init.d directory, changing file permissions, > then running YaST and configuring spamd to start in runlevels 3 & > 5 using the Runlevel Editor. The answer to this, of course (on a SuSE 8.2 system at least) was to download:
ftp://ftp.suse.com/pub/suse/i386/8.2/suse/src/spamassassin-2.50-14.src.rpm Then, do: [EMAIL PROTECTED]:~/software> rpm2cpio spamassassin-2.50-14.src.rpm | cpio -iv init.spamd Next, edit init.spamd to change the line: SPAMD_BIN=/usr/sbin/spamd To read: SPAMD_BIN=/usr/bin/spamd Then, copy the resultant changed file [1] to /etc/init.d/spamd, and next use the YaST Runlevel Editor to start spamd in runlevels 3 & 5. Working perfectly now. [1] http://www.805.org.uk/spamd.txt -- Anthony Edwards [EMAIL PROTECTED]
