On Thu, Sep 23, 2004 at 09:12:18PM +0000, Brian L. Gentry wrote: > The fix is obvious and simple: Shut down spamd, start it from the command > line: /usr/bin/spamd -c -d . Test it. Once you've verified that it's > working > again, modify your spamd startup script to use the new location for spamd. I > also removed /usr/sbin/spamd for good measure, since it's not used any more. > > This took a while to track down and caused us some grief here. I hope this > helps save someone else the hassle. Any chance this could be put into the > upgrade notes file ?
This is an excellent idea, and thanks for your note earlier today. That is indeed it seems the cause of the issue, which must be causing a good deal of scratching of heads, I would have thought. 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. Incidentally, a co-worker who runs a Debian system tells me that the Debian package maintainer has overcome the issue by creating the Debian SpamAssassin 3.0.0 package in such a way that spamd is installed in /usr/sbin/ rather than /usr/bin, as with previous versions. -- Anthony Edwards [EMAIL PROTECTED]
