You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by David Dodell <da...@d2net.net> on 2017/05/29 15:28:07 UTC
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
Re: dns:2.3.3.updates.spamassassin.org => 3.3 1786853, parsed as 3
Posted by David Dodell <da...@d2net.net>.
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 <dj...@ena.com> wrote:
>
>> From: David Dodell <da...@d2net.net>
>
>> 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
Re: dns:2.3.3.updates.spamassassin.org => 3.3 1786853, parsed as 3
Posted by David Jones <dj...@ena.com>.
>From: David Dodell <da...@d2net.net>
>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