You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Rainer Sokoll <ra...@sokoll.com> on 2017/07/06 08:06:38 UTC

updates.spamassassin.org gone?

Hi,

for at least the last 2 days, updates.spamassin.org does not resolve anymore:

~$ host updates.spamassassin.org.
~$

But note:

~$ host nonexistent.spamassassin.org.
Host nonexistent.spamassassin.org. not found: 3(NXDOMAIN)
~$

Meaning: no updates for SA anymore?

Rainer

Re: updates.spamassassin.org gone?

Posted by Rainer Sokoll <ra...@sokoll.com>.
> Am 06.07.2017 um 19:19 schrieb Bill Cole <sa...@billmail.scconsult.com>:
> 
> On 6 Jul 2017, at 4:06, Rainer Sokoll wrote:

>> Meaning: no updates for SA anymore?
> 
> That's quite a leap of illogic...

OK, my fault.
I saw cron's error mail and thought that there could be a DNS problem.
Now I've learned from all of you that there is no problem at all. False alarm.

If I call the cron job directly, it works:

root@mx1:~# /etc/cron.daily/spamassassin
root@mx1:~# echo $?
0
root@mx1:~#

So, I do not understand why cron threw an error, maybe something was broken in my network at this time.

Thank you all,

Rainer

PS: One thing: Is it recommended to use 3.4.1 from backports on Jessie?

Re: updates.spamassassin.org gone?

Posted by Bill Cole <sa...@billmail.scconsult.com>.
On 6 Jul 2017, at 4:06, Rainer Sokoll wrote:

> Hi,
>
> for at least the last 2 days, updates.spamassin.org does not resolve anymore:
>
> ~$ host updates.spamassassin.org.

Which means the name has no A record, but does have other records and/or subdomains.

> But note:
>
> ~$ host nonexistent.spamassassin.org.
> Host nonexistent.spamassassin.org. not found: 3(NXDOMAIN)

However:

$ host -t txt 2.3.3.updates.spamassassin.org
2.3.3.updates.spamassassin.org descriptive text "1799552"
$ host -t txt 3.3.3.updates.spamassassin.org
3.3.3.updates.spamassassin.org descriptive text "1799552"
$ host -t txt 0.4.3.updates.spamassassin.org
0.4.3.updates.spamassassin.org descriptive text "1799552"
$ host -t txt 1.4.3.updates.spamassassin.org
1.4.3.updates.spamassassin.org is an alias for 3.3.3.updates.spamassassin.org.
3.3.3.updates.spamassassin.org descriptive text "1799552"
$ host -t txt 2.4.3.updates.spamassassin.org
2.4.3.updates.spamassassin.org is an alias for 3.3.3.updates.spamassassin.org.
3.3.3.updates.spamassassin.org descriptive text "1799552"

> Meaning: no updates for SA anymore?

That's quite a leap of illogic...

Re: [SOLVED] I'm an idiot

Posted by Bill Cole <sa...@billmail.scconsult.com>.
On 7 Jul 2017, at 12:15, jdow wrote:

> On the other hand, FireFox reports:
> This site can’t be reached
>
> updates.spamassassin.org’s server DNS address could not be found.

Which is simultaneously:

1. True
2. Normal
3. Neither a cause nor symptom of any operational problem.

Re: [SOLVED] I'm an idiot

Posted by jdow <jd...@earthlink.net>.
On 2017-07-07 03:38, Rainer Sokoll wrote:
> 
>> Am 06.07.2017 um 18:27 schrieb Rainer Sokoll <ra...@sokoll.com>:
> 
> [...]
> 
>> Hm, I got an email from cron:
>>
>> -------8<------
>> /etc/cron.daily/spamassassin:
>> error: unable to refresh mirrors file for channel updates.spamassassin.org, using old file
>> channel: could not find working mirror, channel failed
>> sa-update failed for unknown reasons
>> -------8<------
> 
> After losing some hairs it turned out that there are no problems in DNS, no problems in my network.
> /etc/cron.daily/spamassassin changes UID:GUID to debian-spamd:debian-spamd during run.
> But /var/lib/spamassassin/ was owned by root:root :-(
> 
> Sorry for all the noise,
> 
> Rainer

On the other hand, FireFox reports:
This site can’t be reached

updates.spamassassin.org’s server DNS address could not be found.
Go to http://spamassassin.org/
Search Google for updates spamassassin org
ERR_NAME_NOT_RESOLVED

{o.o}   God never promised us only one problem at a time.

[SOLVED] I'm an idiot (was: Re: updates.spamassassin.org gone?)

Posted by Rainer Sokoll <ra...@sokoll.com>.
> Am 06.07.2017 um 18:27 schrieb Rainer Sokoll <ra...@sokoll.com>:

[...]

> Hm, I got an email from cron:
> 
> -------8<------
> /etc/cron.daily/spamassassin:
> error: unable to refresh mirrors file for channel updates.spamassassin.org, using old file
> channel: could not find working mirror, channel failed
> sa-update failed for unknown reasons
> -------8<------

After losing some hairs it turned out that there are no problems in DNS, no problems in my network.
/etc/cron.daily/spamassassin changes UID:GUID to debian-spamd:debian-spamd during run.
But /var/lib/spamassassin/ was owned by root:root :-(

Sorry for all the noise,

Rainer


Re: updates.spamassassin.org gone?

Posted by Antony Stone <An...@spamassassin.open.source.it>.
On Thursday 06 July 2017 at 18:59:19, Rainer Sokoll wrote:

> > Am 06.07.2017 um 18:55 schrieb Antony Stone:
> > 
> > "apt-get policy spamassassin" should show you which one really is
> > installed
> 
> apt-cache ;-)

Oops :)

Yeah, I knew it was one of those apt-something commands which I wish aptitude 
would do for you but doesn't...

> ~$ ssh mx1 apt-cache policy spamassassin
> spamassassin:
>   Installed: 3.4.0-6
>   Candidate: 3.4.0-6
>   Version table:
>  *** 3.4.0-6 0
>         500 http://ftp.de.debian.org/debian/ jessie/main amd64 Packages
>         100 /var/lib/dpkg/status
> 
> So, 3.4.0

Right.  This also suggests you're not using Jessie-backports at all, otherwise 
3.4.1 would at least be a candidate, even if not installed.



Antony.

-- 
If you can't find an Open Source solution for it, then it isn't a real problem.

                                                   Please reply to the list;
                                                         please *don't* CC me.

Re: updates.spamassassin.org gone?

Posted by Rainer Sokoll <ra...@sokoll.com>.
> Am 06.07.2017 um 18:55 schrieb Antony Stone <An...@spamassassin.open.source.it>:
> 


> If you're using Jessie-backports as well (and have deliberately installed the
> backports version of this package) then you have 3.4.1
> 
> 
> "apt-get policy spamassassin" should show you which one really is installed

apt-cache ;-)

~$ ssh mx1 apt-cache policy spamassassin
spamassassin:
  Installed: 3.4.0-6
  Candidate: 3.4.0-6
  Version table:
 *** 3.4.0-6 0
        500 http://ftp.de.debian.org/debian/ jessie/main amd64 Packages
        100 /var/lib/dpkg/status

So, 3.4.0

Rainer

Re: updates.spamassassin.org gone?

Posted by Antony Stone <An...@spamassassin.open.source.it>.
On Thursday 06 July 2017 at 18:53:10, Rainer Sokoll wrote:

> > Am 06.07.2017 um 18:50 schrieb David Jones <dj...@ena.com>:
> > 
> > What version of SA are you running?
> 
> 3.4.0, shipped with Debian 8. But I cannot guarantee that this is in fact
> 3.4.1, because I've never understood Debian's backporting strategy :-(

https://packages.debian.org/search?keywords=spamassassin

If you're just using plain Debian 8 Jessie, you have 3.4.0

If you're using Jessie-backports as well (and have deliberately installed the 
backports version of this package) then you have 3.4.1


"apt-get policy spamassassin" should show you which one really is installed


Antony.

-- 
Anyone that's normal doesn't really achieve much.

 - Mark Blair, Australian rocket engineer

                                                   Please reply to the list;
                                                         please *don't* CC me.

Re: updates.spamassassin.org gone?

Posted by Bill Cole <sa...@billmail.scconsult.com>.
On 6 Jul 2017, at 18:48, jdow wrote:

> No A or PTR record:
>
> ===8<---
> [jdow@thursday ~]$ dig updates.spamassassin.org ns1.apache.org all

1. What is the reason to expect the name "ns1.apache.org" to have any 
DNS records?

2. Using "all" as the final RRTYPE argument (or any other word beginning 
with 'a' except "any") is interpreted by 'dig' as a request for an A 
record. If you think it does something else, look closely at the 
"QUESTION SECTION" of the output.

FWIW:

$ dig apache.org ns

; <<>> DiG 9.11.0-P3 <<>> apache.org ns
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 48013
;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 10

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: dc160d1e1d013255b792d135595eeaae64e1cefb957d8966 (good)
;; QUESTION SECTION:
;apache.org.			IN	NS

;; ANSWER SECTION:
apache.org.		945IN	NS	ns4.no-ip.com.
apache.org.		945	IN	NS	ns3.no-ip.com.
apache.org.		945	IN	NS	ns2.no-ip.com.
apache.org.		945	IN	NS	ns2.surfnet.nl.
apache.org.		945	IN	NS	ns1.no-ip.com.

;; ADDITIONAL SECTION:
ns1.no-ip.com.		2657	IN	A	204.16.255.55
ns2.no-ip.com.		2657	IN	A	204.16.254.6
ns2.surfnet.nl.		2384	IN	A	192.87.36.2
ns3.no-ip.com.		75016	IN	A	207.34.6.1
ns4.no-ip.com.		75016	IN	A	204.16.254.44
ns1.no-ip.com.		25334	IN	AAAA	2620:0:2e60::33
ns2.no-ip.com.		25334	IN	AAAA	2001:1838:f000::6
ns2.surfnet.nl.		2384	IN	AAAA	2001:610:3:200a:192:87:36:2
ns3.no-ip.com.		25334	IN	AAAA	2620:171:802:752d::1

;; Query time: 2 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Thu Jul 06 21:58:06 EDT 2017
;; MSG SIZE  rcvd: 368



Re: updates.spamassassin.org gone?

Posted by Dave Warren <da...@hireahit.com>.
Did you read any of the thread? 

There shouldn't be an A record, and there literally can't be a (valid)
PTR record.

On Thu, Jul 6, 2017, at 15:48, jdow wrote:
> No A or PTR record:
> 
> ===8<---
> [jdow@thursday ~]$ dig updates.spamassassin.org ns1.apache.org all
> 
> ; <<>> DiG 9.9.4-RedHat-9.9.4-50.el7_3.1 <<>> updates.spamassassin.org 
> ns1.apache.org all
> ;; global options: +cmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 7892
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
> 
> ;; OPT PSEUDOSECTION:
> ; EDNS: version: 0, flags:; udp: 4096
> ;; QUESTION SECTION:
> ;updates.spamassassin.org.      IN      A
> 
> ;; AUTHORITY SECTION:
> spamassassin.org.       3415    IN      SOA     ns2.pccc.com. 
> pmc.spamassassin.apache.org. 2017062901 7200 3600 604800 3600
> 
> ;; Query time: 0 msec
> ;; SERVER: 127.0.0.1#53(127.0.0.1)
> ;; WHEN: Thu Jul 06 15:28:44 PDT 2017
> ;; MSG SIZE  rcvd: 125
> 
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 39442
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
> 
> ;; OPT PSEUDOSECTION:
> ; EDNS: version: 0, flags:; udp: 4096
> ;; QUESTION SECTION:
> ;ns1.apache.org.                        IN      A
> 
> ;; AUTHORITY SECTION:
> apache.org.             1800    IN      SOA     ns2.surfnet.nl. 
> hostmaster-2005-alpha.apache.org. 2017070600 3600 900 604800 3600
> 
> ;; Query time: 321 msec
> ;; SERVER: 127.0.0.1#53(127.0.0.1)
> ;; WHEN: Thu Jul 06 15:28:45 PDT 2017
> ;; MSG SIZE  rcvd: 115
> 
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 56671
> ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
> 
> ;; OPT PSEUDOSECTION:
> ; EDNS: version: 0, flags:; udp: 4096
> ;; QUESTION SECTION:
> ;all.                           IN      A
> 
> ;; AUTHORITY SECTION:
> .                       10740   IN      SOA     a.root-servers.net. 
> nstld.verisign-grs.com. 2017070601 1800 900 604800 86400
> 
> ;; Query time: 0 msec
> ;; SERVER: 127.0.0.1#53(127.0.0.1)
> ;; WHEN: Thu Jul 06 15:28:45 PDT 2017
> ;; MSG SIZE  rcvd: 107
> ===8<---
> 
> It looks like somebody fat fingered when updating the Apache.org NS
> records. (Or 
> perhaps it was  ns.pccc.com that was fscked up perhaps on June 29th.)
> 
> {^_^}   Joanne
> 
> On 2017-07-06 11:39, RW wrote:
> > On Thu, 6 Jul 2017 12:14:02 -0500
> > David Jones wrote:
> > 
> >> On 07/06/2017 12:02 PM, Rainer Sokoll wrote:
> >>>    
> >>>> Am 06.07.2017 um 18:55 schrieb David Jones <dj...@ena.com>:
> >>>    
> >>>> You can also run 'sa-update -vvv' to see more information on what
> >>>> it's looking for.
> >>>
> >>> Now I'm really confused: it works the way described in this thread:
> >>>
> > 
> >>>    
> >>
> >> That's odd.  Nothing has changed in DNS for almost 2 weeks so that
> >> shouldn't have happened.
> > 
> > Both DNS txt lookups worked, all the HTTP downloads failed. If the
> > script has worked in the past, and nothing has changed, it was most
> > likely just a temporary networking problem.
> > 
> 


Re: updates.spamassassin.org gone?

Posted by jdow <jd...@earthlink.net>.
No A or PTR record:

===8<---
[jdow@thursday ~]$ dig updates.spamassassin.org ns1.apache.org all

; <<>> DiG 9.9.4-RedHat-9.9.4-50.el7_3.1 <<>> updates.spamassassin.org 
ns1.apache.org all
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 7892
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;updates.spamassassin.org.      IN      A

;; AUTHORITY SECTION:
spamassassin.org.       3415    IN      SOA     ns2.pccc.com. 
pmc.spamassassin.apache.org. 2017062901 7200 3600 604800 3600

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Thu Jul 06 15:28:44 PDT 2017
;; MSG SIZE  rcvd: 125

;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 39442
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;ns1.apache.org.                        IN      A

;; AUTHORITY SECTION:
apache.org.             1800    IN      SOA     ns2.surfnet.nl. 
hostmaster-2005-alpha.apache.org. 2017070600 3600 900 604800 3600

;; Query time: 321 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Thu Jul 06 15:28:45 PDT 2017
;; MSG SIZE  rcvd: 115

;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 56671
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;all.                           IN      A

;; AUTHORITY SECTION:
.                       10740   IN      SOA     a.root-servers.net. 
nstld.verisign-grs.com. 2017070601 1800 900 604800 86400

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Thu Jul 06 15:28:45 PDT 2017
;; MSG SIZE  rcvd: 107
===8<---

It looks like somebody fat fingered when updating the Apache.org NS records. (Or 
perhaps it was  ns.pccc.com that was fscked up perhaps on June 29th.)

{^_^}   Joanne

On 2017-07-06 11:39, RW wrote:
> On Thu, 6 Jul 2017 12:14:02 -0500
> David Jones wrote:
> 
>> On 07/06/2017 12:02 PM, Rainer Sokoll wrote:
>>>    
>>>> Am 06.07.2017 um 18:55 schrieb David Jones <dj...@ena.com>:
>>>    
>>>> You can also run 'sa-update -vvv' to see more information on what
>>>> it's looking for.
>>>
>>> Now I'm really confused: it works the way described in this thread:
>>>
> 
>>>    
>>
>> That's odd.  Nothing has changed in DNS for almost 2 weeks so that
>> shouldn't have happened.
> 
> Both DNS txt lookups worked, all the HTTP downloads failed. If the
> script has worked in the past, and nothing has changed, it was most
> likely just a temporary networking problem.
> 

Re: updates.spamassassin.org gone?

Posted by RW <rw...@googlemail.com>.
On Thu, 6 Jul 2017 12:14:02 -0500
David Jones wrote:

> On 07/06/2017 12:02 PM, Rainer Sokoll wrote:
> >   
> >> Am 06.07.2017 um 18:55 schrieb David Jones <dj...@ena.com>:  
> >   
> >> You can also run 'sa-update -vvv' to see more information on what
> >> it's looking for.  
> > 
> > Now I'm really confused: it works the way described in this thread:
> > 

> >   
> 
> That's odd.  Nothing has changed in DNS for almost 2 weeks so that 
> shouldn't have happened.  

Both DNS txt lookups worked, all the HTTP downloads failed. If the
script has worked in the past, and nothing has changed, it was most
likely just a temporary networking problem.

Re: updates.spamassassin.org gone?

Posted by David Jones <dj...@ena.com>.
On 07/06/2017 12:02 PM, Rainer Sokoll wrote:
> 
>> Am 06.07.2017 um 18:55 schrieb David Jones <dj...@ena.com>:
> 
>> You can also run 'sa-update -vvv' to see more information on what it's looking for.
> 
> Now I'm really confused: it works the way described in this thread:
> 
> root@mx1:~# sa-update -vvv
> DNS TXT query: 0.4.3.updates.spamassassin.org -> 1799552
> Update available for channel updates.spamassassin.org: 1786640 -> 1799552
> DNS TXT query: mirrors.updates.spamassassin.org -> http://spamassassin.apache.org/updates/MIRRORED.BY
> fetching http://spamassassin.apache.org/updates/MIRRORED.BY
> http: (curl) GET http://spamassassin.apache.org/updates/MIRRORED.BY, success
> fetching http://sa-update.secnap.net/1799552.tar.gz
> http: (curl) GET http://sa-update.secnap.net/1799552.tar.gz, success
> fetching http://sa-update.secnap.net/1799552.tar.gz.sha1
> http: (curl) GET http://sa-update.secnap.net/1799552.tar.gz.sha1, success
> fetching http://sa-update.secnap.net/1799552.tar.gz.asc
> http: (curl) GET http://sa-update.secnap.net/1799552.tar.gz.asc, success
> Update was available, and was downloaded and installed successfully
> root@mx1:~#
> 
> 

That's odd.  Nothing has changed in DNS for almost 2 weeks so that 
shouldn't have happened.  Can you post the contents of 
/etc/cron.daily/spamassassin so we can see what it's trying to run?

-- 
Dave

Re: updates.spamassassin.org gone?

Posted by Rainer Sokoll <ra...@sokoll.com>.
> Am 06.07.2017 um 18:55 schrieb David Jones <dj...@ena.com>:

> You can also run 'sa-update -vvv' to see more information on what it's looking for.

Now I'm really confused: it works the way described in this thread:

root@mx1:~# sa-update -vvv
DNS TXT query: 0.4.3.updates.spamassassin.org -> 1799552
Update available for channel updates.spamassassin.org: 1786640 -> 1799552
DNS TXT query: mirrors.updates.spamassassin.org -> http://spamassassin.apache.org/updates/MIRRORED.BY
fetching http://spamassassin.apache.org/updates/MIRRORED.BY
http: (curl) GET http://spamassassin.apache.org/updates/MIRRORED.BY, success
fetching http://sa-update.secnap.net/1799552.tar.gz
http: (curl) GET http://sa-update.secnap.net/1799552.tar.gz, success
fetching http://sa-update.secnap.net/1799552.tar.gz.sha1
http: (curl) GET http://sa-update.secnap.net/1799552.tar.gz.sha1, success
fetching http://sa-update.secnap.net/1799552.tar.gz.asc
http: (curl) GET http://sa-update.secnap.net/1799552.tar.gz.asc, success
Update was available, and was downloaded and installed successfully
root@mx1:~#



Re: updates.spamassassin.org gone?

Posted by David Jones <dj...@ena.com>.
On 07/06/2017 11:53 AM, Rainer Sokoll wrote:
> 
>> Am 06.07.2017 um 18:50 schrieb David Jones <dj...@ena.com>:
> 
>> What version of SA are you running?
> 
> 3.4.0, shipped with Debian 8. But I cannot guarantee that this is in fact 3.4.1, because I've never understood Debian's backporting strategy :-(
> 
> Rainer
> 

Run 'spamassassin -V' and report back with the version.

You can also run 'sa-update -vvv' to see more information on what it's 
looking for.

-- 
Dave

Re: updates.spamassassin.org gone?

Posted by Rainer Sokoll <ra...@sokoll.com>.
> Am 06.07.2017 um 18:50 schrieb David Jones <dj...@ena.com>:

> What version of SA are you running?

3.4.0, shipped with Debian 8. But I cannot guarantee that this is in fact 3.4.1, because I've never understood Debian's backporting strategy :-(

Rainer

Re: updates.spamassassin.org gone?

Posted by David Jones <dj...@ena.com>.
On 07/06/2017 11:27 AM, Rainer Sokoll wrote:
>> Am 06.07.2017 um 10:33 schrieb Tobi <to...@brain-force.ch>:
>>
>> afaik updates.spamassassin.org does not need to be resolvable
>>
>> The two important records for updates exist and resolve:
>>
>> $dig mirrors.updates.spamassassin.org txt +short
>> "http://spamassassin.apache.org/updates/MIRRORED.BY"
>>
>> $dig 0.4.3.updates.spamassassin.org txt +short
>> "1799552"
> 
> Hm, I got an email from cron:
> 
> -------8<------
> /etc/cron.daily/spamassassin:
> error: unable to refresh mirrors file for channel updates.spamassassin.org, using old file
> channel: could not find working mirror, channel failed
> sa-update failed for unknown reasons
> -------8<------
> 
> This is a (to my best knowledge) stock Debian Jessie. So the Debian package maintainer is to blame here?
> 
> Rainer
> 

What version of SA are you running?

-- 
Dave

Re: updates.spamassassin.org gone?

Posted by Rainer Sokoll <ra...@sokoll.com>.
> Am 06.07.2017 um 10:33 schrieb Tobi <to...@brain-force.ch>:
> 
> afaik updates.spamassassin.org does not need to be resolvable
> 
> The two important records for updates exist and resolve:
> 
> $dig mirrors.updates.spamassassin.org txt +short
> "http://spamassassin.apache.org/updates/MIRRORED.BY"
> 
> $dig 0.4.3.updates.spamassassin.org txt +short
> "1799552"

Hm, I got an email from cron:

-------8<------
/etc/cron.daily/spamassassin:
error: unable to refresh mirrors file for channel updates.spamassassin.org, using old file
channel: could not find working mirror, channel failed
sa-update failed for unknown reasons
-------8<------

This is a (to my best knowledge) stock Debian Jessie. So the Debian package maintainer is to blame here?

Rainer

Re: updates.spamassassin.org gone?

Posted by Tobi <to...@brain-force.ch>.
afaik updates.spamassassin.org does not need to be resolvable

The two important records for updates exist and resolve:

$dig mirrors.updates.spamassassin.org txt +short
"http://spamassassin.apache.org/updates/MIRRORED.BY"

$dig 0.4.3.updates.spamassassin.org txt +short
"1799552"

Am 06.07.2017 um 10:06 schrieb Rainer Sokoll:
> Hi,
>
> for at least the last 2 days, updates.spamassin.org does not resolve anymore:
>
> ~$ host updates.spamassassin.org.
> ~$
>
> But note:
>
> ~$ host nonexistent.spamassassin.org.
> Host nonexistent.spamassassin.org. not found: 3(NXDOMAIN)
> ~$
>
> Meaning: no updates for SA anymore?
>
> Rainer


Re: updates.spamassassin.org gone?

Posted by Charles Sprickman <sp...@bway.net>.
> On Jul 6, 2017, at 9:48 AM, Kevin A. McGrail <ke...@mcgrail.com> wrote:
> 
> And my firm has put a lot of time into this which is still half the time David has in fixing ruleqa. So buy him a beer. 

Done!

Re: updates.spamassassin.org gone?

Posted by "Kevin A. McGrail" <ke...@mcgrail.com>.
As David says, we use TXT and CNAME records not A records.  We did switch to cnames which broke sa 3.3.0 update resolution but that was fixed. 

We know rulegen is turned off but rule distribution is working.

This means you can install SA and use sa-update to get current rules.

And they are current because there are not a whole lot of rules being generated and Dave was able to get a current rule set with the old scores manually published.  

And my firm has put a lot of time into this which is still half the time David has in fixing ruleqa.  So buy him a beer.  But no need for alarm.  

Right now though I have switched back to 3.4 work as my priority for the week.

You can also grab KAM.cf which isn't in the stock rules.

https://www.pccc.com/downloads/SpamAssassin/contrib/KAM.cf
Regards,
KAM

Re: updates.spamassassin.org gone?

Posted by David Jones <dj...@ena.com>.
On 07/06/2017 04:54 AM, Merijn van den Kroonenberg wrote:
>> Hi
>>
>> I get the same, who do we report it to
> 
> David, who works on these issues will read it here, he follows the list.
> 
>>
>>
>> Michael
>>
>>
>> On 06/07/17 09:06, Rainer Sokoll wrote:
>>> Hi,
>>>
>>> for at least the last 2 days, updates.spamassin.org does not resolve
>>> anymore:
>>>
>>> ~$ host updates.spamassassin.org.
>>> ~$
>>>

The DNS zone doesn't have an A or CNAME record for 
updates.spamassassin.org.  Sa-update uses a TXT record under this zone 
to detect when an update is ready to be downloaded and applied.

$ dig +short 1.4.3.updates.spamassassin.org txt
3.3.3.updates.spamassassin.org.
"1799552"

FYI, we are currently holding at version 1799552 until I/we can figure 
out what is going wrong with the build of 72_scores.cf.  I have spent 
many hours trying to figure out what is going on so far and have 
pinpointed where the problem is but haven't found the exact cause yet.

>>> But note:
>>>
>>> ~$ host nonexistent.spamassassin.org.
>>> Host nonexistent.spamassassin.org. not found: 3(NXDOMAIN)
>>> ~$
>>>
>>> Meaning: no updates for SA anymore?
> 
> There have not really been updates since March due to server migration and
> such. Hopefully soon again.
> 
>>>
>>> Rainer
>>
>> --
>> Michael Da Cova, Technical Support Manager
>> NetPilot Internet Security Ltd.
>>
>> www.netpilot.com
>>
>> +44 (0)117 335 7335 | +44 (0)7990887629
>> https://uk.linkedin.com/in/michael-da-cova-5427969
>>
>>
> 
> 

-- 
Dave

Re: updates.spamassassin.org gone?

Posted by Rainer Sokoll <ra...@sokoll.com>.
> Am 06.07.2017 um 11:54 schrieb Merijn van den Kroonenberg <me...@web2all.nl>:
> 

> There have not really been updates since March due to server migration and
> such. Hopefully soon again.

The last update I see is from Apr  5 15:23 CET according the to time stamp.
Never noticed that until yesterday…

Rainer


Re: updates.spamassassin.org gone?

Posted by Merijn van den Kroonenberg <me...@web2all.nl>.
> Hi
>
> I get the same, who do we report it to

David, who works on these issues will read it here, he follows the list.

>
>
> Michael
>
>
> On 06/07/17 09:06, Rainer Sokoll wrote:
>> Hi,
>>
>> for at least the last 2 days, updates.spamassin.org does not resolve
>> anymore:
>>
>> ~$ host updates.spamassassin.org.
>> ~$
>>
>> But note:
>>
>> ~$ host nonexistent.spamassassin.org.
>> Host nonexistent.spamassassin.org. not found: 3(NXDOMAIN)
>> ~$
>>
>> Meaning: no updates for SA anymore?

There have not really been updates since March due to server migration and
such. Hopefully soon again.

>>
>> Rainer
>
> --
> Michael Da Cova, Technical Support Manager
> NetPilot Internet Security Ltd.
>
> www.netpilot.com
>
> +44 (0)117 335 7335 | +44 (0)7990887629
> https://uk.linkedin.com/in/michael-da-cova-5427969
>
>



Re: updates.spamassassin.org gone?

Posted by Michael Da Cova <md...@netpilot.com>.
Hi

I get the same, who do we report it to


Michael


On 06/07/17 09:06, Rainer Sokoll wrote:
> Hi,
>
> for at least the last 2 days, updates.spamassin.org does not resolve anymore:
>
> ~$ host updates.spamassassin.org.
> ~$
>
> But note:
>
> ~$ host nonexistent.spamassassin.org.
> Host nonexistent.spamassassin.org. not found: 3(NXDOMAIN)
> ~$
>
> Meaning: no updates for SA anymore?
>
> Rainer

-- 
Michael Da Cova, Technical Support Manager
NetPilot Internet Security Ltd.

www.netpilot.com

+44 (0)117 335 7335 | +44 (0)7990887629
https://uk.linkedin.com/in/michael-da-cova-5427969