On 8/14/2007 2:46 PM, Gene Heskett wrote:
On Tuesday 14 August 2007, Daryl C. W. O'Shea wrote:
On 8/14/2007 6:31 AM, Kai Schaetzl wrote:
Gene Heskett wrote on Tue, 14 Aug 2007 00:15:24 -0400:
Ok, is there a quick & dirty way to determine which .pre file (or
local.cf, there are 3 of those too) is actually running the show?
all the files in /etc/mail/spamassassin
No, that is something you put yourself there.
Sorry Kai, the comment string inserted in front of the loadplugin
statements (all of them) specifically said that sa-update had disabled
them because the --allowplugins wasn't being passed to sa-update.
Hm. Can just say I don't have it here, never seen it and sa-update is run
from cron.daily and without any addition to the command line.
The "openprotect" SARE rules sa-update channel includes a pre file that
loads just about every plugin known to man for some (unknown to me)
reason. If you don't use the --allowplugins options with their channel
sa-update will comment out the plugins they try to load to protect you
from the channel running any code.
Daryl
Nother Q here. I went to the site and updated my crontab entry for the 3.20+
specs, then ran that from the cli with a copy-paste, added a -D when it came
back in half a second, silently the first time, and got this, striping the
usual preamble:
[...]
[18342] dbg: gpg: adding key id [deleted by me]
[18342] dbg: gpg: Searching for 'gpg'
[18342] dbg: util: current PATH
is: /usr/lib/qt-3.3/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/lib/ccache:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin
[18342] dbg: util: executable for gpg was found at /usr/bin/gpg
[18342] dbg: gpg: found /usr/bin/gpg
[18342] dbg: gpg: release trusted key id list:
[deleted by me]
[18342] dbg: channel: attempting channel saupdates.openprotect.com
[18342] dbg: channel: update
directory /var/lib/spamassassin/3.002003/saupdates_openprotect_com
[18342] dbg: channel: channel cf
file /var/lib/spamassassin/3.002003/saupdates_openprotect_com.cf
[18342] dbg: channel: channel pre
file /var/lib/spamassassin/3.002003/saupdates_openprotect_com.pre
[18342] dbg: dns: query failed: 3.2.3.saupdates.openprotect.com => NXDOMAIN
[18342] dbg: channel: no updates available, skipping channel
[18342] dbg: diag: updates complete, exiting with code 1
So, we're back to my subject line, sa-update doesn't [Big Grin]
Whose NXDOMAIN error is this?
NXDOMAIN isn't an error (at least not a DNS error), the record simply
does not exist. For some, again unknown, reason (although I've
speculated about why it's this way [1]) "openprotect" is always way
behind in publishing the needed DNS record for each new release of SA.
Just use my channels [2] and be done with the hassle once and for all.
Daryl
[1]
http://daryl.dostech.ca/blog/2007/02/15/apache-spamassassin-318-released/
[2] http://daryl.dostech.ca/sa-update/sare/sare-sa-update-howto.txt
