OpenMacNews wrote: > hi matt, > > thx for the reply :-) > > >>>>is this an RDJ or SA issue? >>> >>> >>>Well, RDJ is probably running spamassassin --lint. No --siteconfigpath, no >>>--configpath, because those are rare things to do. Most of us run with our >>>config files in directories that SA can auto-detect. >>> >>>(ie: /usr/share/spamassassin for config and /etc/mail/spamassassin for >>>siteconfig) >>> >>> >>>--configpath is extraordinarily rare to use unless you're a developer. >>> >>> >>>You'll probably have to hack RDJ to use those paths, if that's where your >>>real >>>rulesets are.. (although I do wonder why they are there..) > > > they are where they're supposed to be, i.e. i pointed my SA build to: > > perl Makefile.PL \ > PREFIX=/usr/local/spamassassin-dev \ > DATADIR=/var/MailServer/Conf/SA/Dist \ > CONFDIR=/var/MailServer/Conf/SA/Local \ > ...
Interesting. Questions: 1) does spamassassin --lint (without the specifiers) fail? Based on your build parameters it should not. 2) if it does fail, try spamassassin --lint -D. What's it detecting as the site rules dir and default rules dir? I suspect your problem might be that something created one of SA's default rule directories, and SA is auto-detecting it, in preference over the specified DATADIR and CONFDIR. In theory SA should check your build-time specified directory first, unless something got screwed up in the build process and SpamAssassin.pm is looking in the wrong places.
