RE: RDJ Blacklist
I think I now see the problem. The url
to retrieve the blacklist-uri has been changed, and this is reflected in
version 1.24. I also see there is a change form random.cf. The
interesting thing I am not sure of.is why System B does not reflect the
changes of version 1.24, but was till downloading the current version of
blacklist-uri.cf
-Original Message-
From: Casey King
[mailto:[EMAIL PROTECTED]
Sent: Thursday, September 29, 2005 9:29 AM
To: SpamAssassin Users
Subject: RDJ Blacklist
While checking RDJ on my systems. I
noticed, blacklist-uri last updated on 9.21.2005 on two of my systems, and on
my third system, it is current as of today. The version of RDJ I am
running on all three systems is 1.21. I know there is a 1.24, but I would
like to get this working again before I decide to change to another
version. I ran the update from the command line and piped it to a test
file. Everything looks the same until reaching the blacklist.uri
part. For some reason systemA says blacklist does not need updated, and
systemB updates to the most current version. Below are snips from systemA
and systemB. As I said before, system A is current to 9.21.2005, and
system B is 9.29.2005
System A
[snip] (top of piped information)
exec: curl -w %{http_code}
--compressed -O -R -s -S -z /etc/mail/spamassassin/RulesDuJour/rules_du_jour
http://sandgnat.com/rdj/rules_du_jour 21
curl_output: 304
[snip]
-- BLACKLIST_URI --
RULESET_NAME=BLACKLIST_URI
INDEX=10
CF_URL=http://www.stearns.org/sa-blacklist/sa-blacklist.current.uri.cf
CF_FILE=blacklist-uri.cf
CF_NAME=William Stearn's URI
blacklist
PARSE_NEW_VER_SCRIPT=grep -i
'^#.*sa-blacklist.uri: 200' | sort | tail -1
CF_MUNGE_SCRIPT=
Old sa-blacklist.current.uri.cf
already existed in /etc/mail/spamassassin/RulesDuJour...
Retrieving file from
http://www.stearns.org/sa-blacklist/sa-blacklist.current.uri.cf...
exec: curl -w %{http_code}
--compressed -O -R -s -S -z /etc/mail/spamassassin/RulesDuJour/sa-blacklist.current.uri.cf
http://www.stearns.org/sa-blacklist/sa-blacklist.current.uri.cf 21
curl_output: 302
sa-blacklist.current.uri.cf was up
to date [skipped downloading of
http://www.stearns.org/sa-blacklist/sa-blacklist.current.uri.cf ] ...
System B
[snip] (top of piped information)
Curl version is 7.9 (Not 7.10 or
greater). Falling back to wget.
exec: wget -N
http://sandgnat.com/rdj/rules_du_jour
/etc/mail/spamassassin/RulesDuJour/wget.log 21
wget_output: --08:36:06-- http://sandgnat.com/rdj/rules_du_jour
= `rules_du_jour'
Resolving sandgnat.com... done.
Connecting to
sandgnat.com[208.42.148.125]:80... connected.
HTTP request sent, awaiting
response... 200 OK
Length: 60,691
[application/octet-stream]
Server file no newer than local file
`rules_du_jour' -- not retrieving.
[snip]
-- BLACKLIST_URI --
RULESET_NAME=BLACKLIST_URI
INDEX=10
CF_URL=http://www.stearns.org/sa-blacklist/sa-blacklist.current.uri.cf
CF_FILE=blacklist-uri.cf
CF_NAME=William Stearn's URI
blacklist
PARSE_NEW_VER_SCRIPT=grep -i
'^#.*sa-blacklist.uri: 200' | sort | tail -1
CF_MUNGE_SCRIPT=
Old sa-blacklist.current.uri.cf
already existed in /etc/mail/spamassassin/RulesDuJour...
Retrieving file from http://www.stearns.org/sa-blacklist/sa-blacklist.current.uri.cf...
exec: wget -N
http://www.stearns.org/sa-blacklist/sa-blacklist.current.uri.cf
/etc/mail/spamassassin/RulesDuJour/wget.log 21
wget_output: --08:36:08--
http://www.stearns.org/sa-blacklist/sa-blacklist.current.uri.cf
= `sa-blacklist.current.uri.cf'
Resolving www.stearns.org... done.
Connecting to
www.stearns.org[66.59.111.182]:80... connected.
HTTP request sent, awaiting
response... 302 Found
Location: http://www.sa-blacklist.stearns.org/sa-blacklist/sa-blacklist.current.uri.cf
[following]
--08:36:09--
http://www.sa-blacklist.stearns.org/sa-blacklist/sa-blacklist.current.uri.cf
= `sa-blacklist.current.uri.cf'
Resolving
www.sa-blacklist.stearns.org... done.
Connecting to
www.sa-blacklist.stearns.org[147.102.222.211]:80... connected.
HTTP request sent, awaiting
response... 200 OK
Length: 2,820,512 [text/plain]
Remote file is newer, retrieving.
--08:36:09--
http://www.sa-blacklist.stearns.org/sa-blacklist/sa-blacklist.current.uri.cf
= `sa-blacklist.current.uri.cf'
Connecting to
www.sa-blacklist.stearns.org[147.102.222.211]:80... connected.
HTTP request sent, awaiting
response... 200 OK
Length: 2,820,512 [text/plain]
0K ..
.. .. .. .. 1% 60.17 KB/s
50K ..
.. .. .. .. 3% 83.89 KB/s
100K .. ..
.. .. .. 5% 34.41 KB/s
150K .. ..
.. .. .. 7% 55.37 KB/s
200K .. ..
.. .. .. 9% 36.28 KB/s
250K .. ..
.. .. .. 10% 24.26 KB/s
300K .. ..
.. .. .. 12% 38.40 KB/s
Re: RDJ Blacklist
Aha!
I see you've found a bug in Rules du Jour! Bill is returning a 302 http
response code which indicates a temporary URL change. However, RDJ is
incorrectly interpreting the 302 as a not changed.
Short term solution is to upgrade to the new RDJ with the current URL as
you've stated. I need to fix RDJ with curl though to do the right thing.
Casey King wrote:
I think I now see the problem. The url to retrieve the blacklist-uri
has been changed, and this is reflected in version 1.24. I also see
there is a change form random.cf. The interesting thing I am not sure
of….is why System B does not reflect the changes of version 1.24, but
was till downloading the current version of blacklist-uri.cf
-Original Message-
*From:* Casey King [mailto:[EMAIL PROTECTED]
*Sent:* Thursday, September 29, 2005 9:29 AM
*To:* SpamAssassin Users
*Subject:* RDJ Blacklist
While checking RDJ on my systems. I noticed, blacklist-uri last
updated on 9.21.2005 on two of my systems, and on my third system, it
is current as of today. The version of RDJ I am running on all three
systems is 1.21. I know there is a 1.24, but I would like to get this
working again before I decide to change to another version. I ran the
update from the command line and piped it to a test file. Everything
looks the same until reaching the blacklist.uri part. For some reason
systemA says blacklist does not need updated, and systemB updates to
the most current version. Below are snips from systemA and systemB. As
I said before, system A is current to 9.21.2005, and system B is 9.29.2005
System A
[snip] (top of piped information)
exec: curl -w %{http_code} --compressed -O -R -s -S -z
/etc/mail/spamassassin/RulesDuJour/rules_du_jour
http://sandgnat.com/rdj/rules_du_jour 21
curl_output: 304
[snip]
-- BLACKLIST_URI --
RULESET_NAME=BLACKLIST_URI
INDEX=10
CF_URL=http://www.stearns.org/sa-blacklist/sa-blacklist.current.uri.cf
CF_FILE=blacklist-uri.cf
CF_NAME=William Stearn's URI blacklist
PARSE_NEW_VER_SCRIPT=grep -i '^#.*sa-blacklist.uri: 200' | sort | tail -1
CF_MUNGE_SCRIPT=
Old sa-blacklist.current.uri.cf already existed in
/etc/mail/spamassassin/RulesDuJour...
Retrieving file from
http://www.stearns.org/sa-blacklist/sa-blacklist.current.uri.cf...
exec: curl -w %{http_code} --compressed -O -R -s -S -z
/etc/mail/spamassassin/RulesDuJour/sa-blacklist.current.uri.cf
http://www.stearns.org/sa-blacklist/sa-blacklist.current.uri.cf 21
curl_output: 302
sa-blacklist.current.uri.cf was up to date [skipped downloading of
http://www.stearns.org/sa-blacklist/sa-blacklist.current.uri.cf ] ...
System B
[snip] (top of piped information)
Curl version is 7.9 (Not 7.10 or greater). Falling back to wget.
exec: wget -N http://sandgnat.com/rdj/rules_du_jour
/etc/mail/spamassassin/RulesDuJour/wget.log 21
wget_output: --08:36:06-- http://sandgnat.com/rdj/rules_du_jour
= `rules_du_jour'
Resolving sandgnat.com... done.
Connecting to sandgnat.com[208.42.148.125]:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 60,691 [application/octet-stream]
Server file no newer than local file `rules_du_jour' -- not retrieving.
[snip]
-- BLACKLIST_URI --
RULESET_NAME=BLACKLIST_URI
INDEX=10
CF_URL=http://www.stearns.org/sa-blacklist/sa-blacklist.current.uri.cf
CF_FILE=blacklist-uri.cf
CF_NAME=William Stearn's URI blacklist
PARSE_NEW_VER_SCRIPT=grep -i '^#.*sa-blacklist.uri: 200' | sort | tail -1
CF_MUNGE_SCRIPT=
Old sa-blacklist.current.uri.cf already existed in
/etc/mail/spamassassin/RulesDuJour...
Retrieving file from
http://www.stearns.org/sa-blacklist/sa-blacklist.current.uri.cf...
exec: wget -N
http://www.stearns.org/sa-blacklist/sa-blacklist.current.uri.cf
/etc/mail/spamassassin/RulesDuJour/wget.log 21
wget_output: --08:36:08--
http://www.stearns.org/sa-blacklist/sa-blacklist.current.uri.cf
= `sa-blacklist.current.uri.cf'
Resolving www.stearns.org... done.
Connecting to www.stearns.org[66.59.111.182]:80... connected.
HTTP request sent, awaiting response... 302 Found
Location:
http://www.sa-blacklist.stearns.org/sa-blacklist/sa-blacklist.current.uri.cf
[following]
--08:36:09--
http://www.sa-blacklist.stearns.org/sa-blacklist/sa-blacklist.current.uri.cf
= `sa-blacklist.current.uri.cf'
Resolving www.sa-blacklist.stearns.org... done.
Connecting to www.sa-blacklist.stearns.org[147.102.222.211]:80...
connected.
HTTP request sent, awaiting response... 200 OK
Length: 2,820,512 [text/plain]
Remote file is newer, retrieving.
--08:36:09--
http://www.sa-blacklist.stearns.org/sa-blacklist/sa-blacklist.current.uri.cf
= `sa-blacklist.current.uri.cf'
Connecting to www.sa-blacklist.stearns.org[147.102.222.211]:80...
connected.
HTTP request sent, awaiting response... 200 OK
Length: 2,820,512 [text/plain]
0K .. .. .. .. .. 1% 60.17 KB/s
50K .. .. .. .. .. 3% 83.89 KB/s
Re: RDJ Blacklist
Good evening, Chris, On Thu, 29 Sep 2005, Chris Thielen wrote: Aha! I see you've found a bug in Rules du Jour! Bill is returning a 302 http response code which indicates a temporary URL change. However, RDJ is incorrectly interpreting the 302 as a not changed. Short term solution is to upgrade to the new RDJ with the current URL as you've stated. I need to fix RDJ with curl though to do the right thing. I do understand that you need to check the output of curl in general to handle situations like this in the future. As for this current issue with my random.cf and sa-blacklistcf files, I thought you had updated the urls for this in rules du jour already? Is it just a case that people are still using old versions on rdj? I really am sorry to have to do that redirect, but I don't know of a more elegant way to move people over to the mirror sites. Cheers, - Bill --- I called up the Bureau of Alcohol, Tobacco, and Firearms regional office and asked, What wine goes best with an M-16? The guy who answered did his best to be helpful: That depends. What are you smoking? (Courtesy of Andrej Todosic [EMAIL PROTECTED]) -- William Stearns ([EMAIL PROTECTED]). Mason, Buildkernel, freedups, p0f, rsync-backup, ssh-keyinstall, dns-check, more at: http://www.stearns.org --
Re: RDJ Blacklist
William Stearns wrote: I see you've found a bug in Rules du Jour! Bill is returning a 302 http response code which indicates a temporary URL change. However, RDJ is incorrectly interpreting the 302 as a not changed. Short term solution is to upgrade to the new RDJ with the current URL as you've stated. I need to fix RDJ with curl though to do the right thing. I do understand that you need to check the output of curl in general to handle situations like this in the future. As for this current issue with my random.cf and sa-blacklistcf files, I thought you had updated the urls for this in rules du jour already? Is it just a case that people are still using old versions on rdj? Yep, I have updated the URLs already and Yep Casey just hasn't installed the new version yet! I really am sorry to have to do that redirect, but I don't know of a more elegant way to move people over to the mirror sites. Seems like the most elegant method to me, as long as all the clients (*cough*) respond properly :) Chris signature.asc Description: OpenPGP digital signature
