--On Tuesday, December 01, 2015 2:57 PM -0800 John Hardin
<[email protected]> wrote:
On Tue, 1 Dec 2015, Filippo Carletti wrote:
2. verify everything it's working, SA runs with default rules from
/usr/share
Where did those default rules come from? SA *does not ship* with rules
in the install set.
$ rpm -qf /usr/share/spamassassin/50_scores.cf
spamassassin-3.4.1-8.el6.x86_64
(Note: a packager may add a static rules snapshot to the standard SA
install set; this might have been done by whoever packaged up the RPM.)
Right.
https://git.centos.org/blob/rpms!spamassassin/6c4364e0c267abccbafcaaa3ed
79b2fe4d8e54b2/SPECS!spamassassin.spec;jsessionid=mc5igseasal0axkra6qhd4
it Line 229:
# Default rules from separate tarball
cd $RPM_BUILD_ROOT%{_datadir}/spamassassin/
tar xfvz %{SOURCE1}
sed -i -e 's|\@\@VERSION\@\@|%{saversion}|' *.cf
Are you saying that running sa-update without network access *deletes*
existing rules?
No. If the first time sa-update runs there's no network access, rules
are never downloaded.
"Never", because the centos cron job runs sa-update only if spamd or
amavisd are running (and they stop when there are no rules).
Ah, ok, that sounds like the problem to me: the RH/Centos sa-update cron
job should not depend on whether or not spamd/amavisd are currently
running.
I don't think this is a problem in base SA, it sounds more like a problem
in the packaging addon code provided by RH/Centos.
Agreed. :P That's a failed installation/logic issue.
--Quanah
--
Quanah Gibson-Mount
Platform Architect
Zimbra, Inc.
--------------------
Zimbra :: the leader in open source messaging and collaboration
