https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7800
Bill Cole <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |[email protected] Resolution|--- |WORKSFORME --- Comment #2 from Bill Cole <[email protected]> --- (In reply to mike from comment #0) > There is no DNS entry for update.spamassassin.org or sought.rules.yerp.org. > The channel.d files spamassassin-official.cong and sought.conf were last > updated on Feb. 4. The "sought" rules are many years out of date and do more harm than good due to how they were created, which was intentionally for short-term use. They are also not (and never have been) a part of the Apache SpamAssassin Project. If they've finally stopped working altogether, that is a good thing. The DNS node updates.spamassassin.org does not have any records of its own, because they are unneeded for it's function. It does have child nodes with appropriate records: # dig 4.4.3.updates.spamassassin.org ; <<>> DiG 9.14.10 <<>> 4.4.3.updates.spamassassin.org ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 54102 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ; COOKIE: b637d10b5993bfa52b24ee845e52e434ac57f18a4309f8d0 (good) ;; QUESTION SECTION: ;4.4.3.updates.spamassassin.org. IN A ;; ANSWER SECTION: 4.4.3.updates.spamassassin.org. 3577 IN CNAME 3.3.3.updates.spamassassin.org. ;; AUTHORITY SECTION: spamassassin.org. 3600 IN SOA ns2.pccc.com. pmc.spamassassin.apache.org. 2020022305 7200 3600 604800 3600 ;; Query time: 104 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Sun Feb 23 15:44:36 EST 2020 ;; MSG SIZE rcvd: 222 Whatever the problem is that you are having is NOT a bug in SpamAssassin. It may be a local configuration or DNS problem but I can find no indication of trouble with rule updates. I fetched a new version (1874360) of the updates.spamassassin.org channel today at 10:17 UTC, and my personal backups show unique versions for each of the past 3 days. The monitoring emails sent to dev team members when daily updates aren't completed on time indicate 4 failures in the past month. As this is clearly a problem local to your system, I am closing this bug. You may find more in-depth help in figuring out what is wrong by posting on the SpamAssassin-Users mailing list. -- You are receiving this mail because: You are the assignee for the bug.
