Re: dns:2.3.3.updates.spamassassin.org => 3.3 1786853, parsed as 3
Wow … thanks for the response … and thank you for all the time you are putting into getting this working again. David > On May 29, 2017, at 9:56 AM, David Jones wrote: > >> From: David Dodell > >> I've noticed that my rules are not updating anymore. > >> I'm on SpamAssassin 3.3.2 > >> So I get this error; > >> dns:2.3.3.updates.spamassassin.org => 3.3 1786853, parsed as 3 >> current version is 1786853, new version is 3, skipping channel > >> I've tried googling the error, checking the SA website ... but can't >> find any discussion of this. > >> If I do a DNS lookup of: > >> 2.3.3.updates.spamassassin.org canonical name = >> 3.3.3.updates.spamassassin.org > >> DNS then can not find 3.3.3.updates.spamassassin.org; tried some >> off-site DNS lookups, and they too can not find >> 3.3.3.updates.spamassassin.org > > Sorry about that. I am working on getting the rule update scripts > working again on our master server. I think I know what is going > on so I should be able to revert my changes to get 3.3.2 sa-update > working again. It must not be able to handle the CNAME like newer > versions of sa-update can. > > From what I can tell, all versions of SA 3.3.0 and above are compatible > with the same rules so I was hoping to only have to do rule validation > against a single version 3.3.3 and set the DNS TXT record for 3.3.3. It > appears I am going to have to adjust the script slightly to also set a direct > TXT for 3.3.2 and not use a CNAME like newer versions of sa-update > support. > > BTW, I hope to have the rules updating very soon so we can continue > with the ruleqa processing and scoring updates. I know there are a > couple of rule updates needed so I am working very hard and many > hours to get this going as soon as possible. > > Dave smime.p7s Description: S/MIME cryptographic signature
dns:2.3.3.updates.spamassassin.org => 3.3 1786853, parsed as 3
I've noticed that my rules are not updating anymore. I'm on SpamAssassin 3.3.2 So I get this error; dns:2.3.3.updates.spamassassin.org => 3.3 1786853, parsed as 3 current version is 1786853, new version is 3, skipping channel I've tried googling the error, checking the SA website ... but can't find any discussion of this. If I do a DNS lookup of: 2.3.3.updates.spamassassin.org canonical name = 3.3.3.updates.spamassassin.org DNS then can not find 3.3.3.updates.spamassassin.org; tried some off-site DNS lookups, and they too can not find 3.3.3.updates.spamassassin.org While I see on the SA website that 3.3.2 is no longer being updated or supported, I see nothing about the rules not being updates.Maybe I’m missing something in my search? David smime.p7s Description: S/MIME cryptographic signature
Re: Rules not updating
Thank you … puts my mind at ease … is there someplace on the web that is published the latest rules, so I can assure myself in the future that my installation is not broken. It seems that for months the rules were being updated daily, and kinda surprised I haven’t seen anything in over a week. > On Feb 8, 2015, at 3:29 AM, Axb wrote: > > On 02/07/2015 03:10 PM, David Dodell wrote: >> My spam assassin has been running fine for months, and then last >> Saturday started reporting that there were no rule updates ending >> with version 1655961 >> >> From the wiki it looks like the rules are at 1658033. >> >> Being very much a novice at this, should I be issuing some type of >> manual sa-update command to force an update?If I do a regular >> update, it exists with code 1 and version 1655961 being report as the >> latest. >> >> I’ve noticed the amount of spam sneaking through this past week has >> increased dramatically, I’m assuming due to the rule set? >> >> Should I be manually deleting the rules from someplace, or a pointer, >> to force the update and get back on track? >> >> Thanks, be kind … I only play a network administrator on TV and did >> not stay at a Holiday Inn Express last night >> >> David >> > > Feb 8 11:27:40.214 [35736] dbg: channel: current version is 1655961, new > version is 1655961, skipping channel > > > 1655961 is the latest - no need to worry >
Rules not updating
My spam assassin has been running fine for months, and then last Saturday started reporting that there were no rule updates ending with version 1655961 From the wiki it looks like the rules are at 1658033. Being very much a novice at this, should I be issuing some type of manual sa-update command to force an update?If I do a regular update, it exists with code 1 and version 1655961 being report as the latest. I’ve noticed the amount of spam sneaking through this past week has increased dramatically, I’m assuming due to the rule set? Should I be manually deleting the rules from someplace, or a pointer, to force the update and get back on track? Thanks, be kind … I only play a network administrator on TV and did not stay at a Holiday Inn Express last night David
sa-update not updating?
My sa-update has been working well for month … updating at 5 am local time with new rules. Starting last week, I haven’t seen an update, my sa-update ends up with exiting with level 1, showing that the update server is at version 1655961 and no new update is needed. But it looks from the wiki that the updates are at 1658033 Since I am playing a network administrator on TV, and didn’t stay at a Holiday Inn Express … am I missing something … the amount of spam getting through has increased since last week. Is there a way to “force” an update to the latest rules, ignoring what I have on my server to get me back in sync? Suggestions / help? Thanks David
Re: Rules Not Updating
Thank you … I don't see it that way in my log; I have the following
below … I'm assuming that the last three lines coming from
updates.spamassasin.org show the version on the update server, and that
I'm matching, therefore no update?
Also, how come I can't do a DNS
lookup of updates.spamassassin.org ?? Is that the FQDN of the update
server?
Thanks
David
---
Feb 3 05:00:01.980 [39716] dbg:
logger: adding facilities: all
Feb 3 05:00:01.993 [39716] dbg: logger:
logging level is DBG
Feb 3 05:00:01.994 [39716] dbg: generic:
SpamAssassin version 3.3.2-r929478
Feb 3 05:00:01.994 [39716] dbg:
generic: Perl 5.012003, PREFIX=/,
DEF_RULES_DIR=/private/var/spamassassin/3.003002,
LOCAL_RULES_DIR=/private/etc/mail/spamassassin,
LOCAL_STATE_DIR=//var/spamassassin
Feb 3 05:00:01.994 [39716] dbg:
config: timing enabled
Feb 3 05:00:01.995 [39716] dbg: config: score set
0 chosen.
Feb 3 05:00:02.003 [39716] dbg: dns: is Net::DNS::Resolver
available? yes
Feb 3 05:00:02.003 [39716] dbg: dns: Net::DNS version:
0.66
Feb 3 05:00:02.003 [39716] dbg: generic: sa-update version
svn917659
Feb 3 05:00:02.003 [39716] dbg: generic: using update
directory: /etc/mail/spamassassin
Feb 3 05:00:02.100 [39716] dbg: diag:
perl platform: 5.012003 darwin
Feb 3 05:00:02.100 [39716] dbg: diag:
[...] module installed: Digest::SHA1, version 2.13
Feb 3 05:00:02.100
[39716] dbg: diag: [...] module installed: HTML::Parser, version
3.68
Feb 3 05:00:02.100 [39716] dbg: diag: [...] module installed:
Net::DNS, version 0.66
Feb 3 05:00:02.101 [39716] dbg: diag: [...]
module installed: NetAddr::IP, version 4.037
Feb 3 05:00:02.101 [39716]
dbg: diag: [...] module installed: Time::HiRes, version 1.9719
Feb 3
05:00:02.101 [39716] dbg: diag: [...] module installed: Archive::Tar,
version 1.54
Feb 3 05:00:02.101 [39716] dbg: diag: [...] module
installed: IO::Zlib, version 1.10
Feb 3 05:00:02.101 [39716] dbg: diag:
[...] module installed: Digest::SHA1, version 2.13
Feb 3 05:00:02.101
[39716] dbg: diag: [...] module installed: MIME::Base64, version
3.08
Feb 3 05:00:02.101 [39716] dbg: diag: [...] module installed:
DB_File, version 1.82
Feb 3 05:00:02.101 [39716] dbg: diag: [...] module
installed: Net::SMTP, version 2.31
Feb 3 05:00:02.101 [39716] dbg: diag:
[...] module installed: Mail::SPF, version v2.007
Feb 3 05:00:02.101
[39716] dbg: diag: [...] module installed: IP::Country::Fast, version
604.001
Feb 3 05:00:02.101 [39716] dbg: diag: [...] module not
installed: Razor2::Client::Agent ('require' failed)
Feb 3 05:00:02.101
[39716] dbg: diag: [...] module not installed: Net::Ident ('require'
failed)
Feb 3 05:00:02.101 [39716] dbg: diag: [...] module installed:
IO::Socket::INET6, version 2.65
Feb 3 05:00:02.101 [39716] dbg: diag:
[...] module installed: IO::Socket::SSL, version 1.35
Feb 3 05:00:02.101
[39716] dbg: diag: [...] module installed: Compress::Zlib, version
2.024
Feb 3 05:00:02.101 [39716] dbg: diag: [...] module installed:
Mail::DKIM, version 0.39
Feb 3 05:00:02.101 [39716] dbg: diag: [...]
module installed: DBI, version 1.615
Feb 3 05:00:02.101 [39716] dbg:
diag: [...] module installed: Getopt::Long, version 2.38
Feb 3
05:00:02.101 [39716] dbg: diag: [...] module installed: LWP::UserAgent,
version 5.835
Feb 3 05:00:02.101 [39716] dbg: diag: [...] module
installed: HTTP::Date, version 5.831
Feb 3 05:00:02.101 [39716] dbg:
diag: [...] module installed: Encode::Detect, version 1.01
Feb 3
05:00:02.112 [39716] dbg: channel: attempting channel
updates.spamassassin.org
Feb 3 05:00:02.112 [39716] dbg: channel: update
directory /etc/mail/spamassassin/updates_spamassassin_org
Feb 3
05:00:02.112 [39716] dbg: channel: channel cf file
/etc/mail/spamassassin/updates_spamassassin_org.cf
Feb 3 05:00:02.112
[39716] dbg: channel: channel pre file
/etc/mail/spamassassin/updates_spamassassin_org.pre
Feb 3 05:00:02.112
[39716] dbg: channel: metadata version = 1655961
Feb 3 05:00:02.207
[39716] dbg: dns: 2.3.3.updates.spamassassin.org => 1655961, parsed as
1655961
Feb 3 05:00:02.207 [39716] dbg: channel: current version is
1655961, new version is 1655961, skipping channel
Feb 3 05:00:02.207
[39716] dbg: diag: updates complete, exiting with code 1
On 03.02.2015
19:54, Reindl Harald wrote:
> Am 04.02.2015 um 03:47 schrieb David
Dodell:
>
>> I have noticed that the last three nights that I have not
had any rule updates, sa-update exists with code 1. Any site have
information on what the current rule set release is … haven't had
problems for months, usually seeing a new release nightly … did
something change in the last 3 days?
>
> just look in your logs
>
>
[root@localhost:~]$ cat /var/log/sa-update.log
> 01-Feb-2015 05:31:54:
SpamAssassin: No update available
> 02-Feb-2015 04:38:11: SpamAssassin:
No update available
> 03-Feb-2015 05:14:06: SpamAssassin: No update
available
Rules Not Updating
I have noticed that the last three nights that I have not had any rule updates, sa-update exists with code 1. Any site have information on what the current rule set release is … haven’t had problems for months, usually seeing a new release nightly … did something change in the last 3 days? Thank you David Dodell
