R P Herrold a écrit :
> On Fri, 8 Jan 2010, mouss wrote:
>
>> you can query DNS to get the "version" of the rules. for example:
>>
>> $ host -t txt "*.2.3.updates.spamassassin.org"
>> *.2.3.updates.spamassassin.org descriptive text "895075"
>>
>> (2.3 is the "reverse" of 3.2, which corresponds to
R P Herrold wrote on Sun, 10 Jan 2010 00:13:33 -0500 (EST):
> Looks like 3.3 is not so behaving
it is, a wildcard is missing, You have to use 0.3.3.
Btw, I'm not getting NXDOMAIN on the wildcard but the SPF entry.
Kai
--
Get your web at Conactive Internet Services: http://www.conactive.com
On Fri, 8 Jan 2010, mouss wrote:
you can query DNS to get the "version" of the rules. for example:
$ host -t txt "*.2.3.updates.spamassassin.org"
*.2.3.updates.spamassassin.org descriptive text "895075"
(2.3 is the "reverse" of 3.2, which corresponds to the SA version you use).
Looks like 3.
> "MG" == Martin Gregorie writes:
MG> I run this script as a weekly cron job:
I just use one line in my crontab:
33 2 * * * sa-update
If something goes wrong I'll get a mail with the errors. Else nothing
will interrupt my leisure yacht cruise.
Here's a script correction for an obvious mistake that I managed not to spot.
In summary, it is:
s/$chkd/$sau/
IOW the script should read:
==
#!/bin/bash
#
# Update the Spamassassin rules
#
sau=/usr/bin/sa-update
if [ -x $sa
clem...@dwf.com a écrit :
> How do I tell if sa-update is actually running?
> I mean, yes, I can run it by hand and get no error messages, and with -D
> I dont see any problems, still I feel that my stuff isnt current, and that
> there
> should be an update.
>
> Should I be getting a message in /
On Thu, 2010-01-07 at 19:14 -0700, clem...@dwf.com wrote:
> How do I tell if sa-update is actually running?
> I mean, yes, I can run it by hand and get no error messages, and with -D
> I dont see any problems, still I feel that my stuff isnt current, and that
> there
> should be an update.
>
> Sh
clem...@dwf.com wrote:
> How do I tell if sa-update is actually running?
> I mean, yes, I can run it by hand and get no error messages, and with
> -D I dont see any problems, still I feel that my stuff isnt current,
> and that there should be an update.
>
> Should I be getting a message in /var/l
How do I tell if sa-update is actually running?
I mean, yes, I can run it by hand and get no error messages, and with -D
I dont see any problems, still I feel that my stuff isnt current, and that
there
should be an update.
Should I be getting a message in /var/log/messages? or /var/log/maillog?