Re: sa-update error 3 no mirrors.sought.rules.yerp.org

[Kenneth Porter]

--On Sunday, March 14, 2021 1:23 PM +1000 Simon Wilson 
 wrote:



You've not stated your OS but on a RHEL/CentOS 7 box the correct way to
remove is to go to /etc/mail/spamassassin/channel.d and delete
sought.conf.


RHEL bugzilla for the issue:

Re: sa-update error 3 no mirrors.sought.rules.yerp.org

[Simon Wilson]

- Message from a...@onet.eu -
   Date: Fri, 12 Mar 2021 13:16:25 +0100
   From: a...@onet.eu
Subject: sa-update error 3 no mirrors.sought.rules.yerp.org
 To: users@spamassassin.apache.org



Hi,
I'm getting this from cron since two days:
channel: no 'mirrors.sought.rules.yerp.org' record found, channel failed
11-Mar-2021 05:46:59: SpamAssassin: Unknown error code 3 from sa-update
ls /var/lib/spamassassin/3.004000/
sought_rules_yerp_org
sought_rules_yerp_org.cf
updates_spamassassin_org
updates_spamassassin_org.cf
rm -rf /var/lib/spamassassin/3.004002/
and then
sa-update -D
gives no errors,
but when I try to run cron job it takes a long time and does not finish:
/usr/share/spamassassin/sa-update.cron 2>&1 | tee -a /var/log/sa-update.log



The cron script contains a "sleep" function to randomise the time at  
which clients hit the servers for updates. You are running into the  
sleep when you run the script manually...



 
Greetings,
atat [at] onet.eu



- End message from a...@onet.eu -

See https://cwiki.apache.org/confluence/display/SPAMASSASSIN/SoughtRules

"Update: this is no longer active, and should not be used."

You've not stated your OS but on a RHEL/CentOS 7 box the correct way  
to remove is to go to /etc/mail/spamassassin/channel.d and delete  
sought.conf.




--
Simon Wilson
M: 0400 12 11 16

Re: sa-update error 3 no mirrors.sought.rules.yerp.org

[Axb]

Sought rules have been deprecated at least 5 years ago.
you can remove that part of the config.

h2h
Axb

On 3/12/21 1:16 PM, a...@onet.eu wrote:

Hi,
I'm getting this from cron since two days:
channel: no 'mirrors.sought.rules.yerp.org' record found, channel failed
11-Mar-2021 05:46:59: SpamAssassin: Unknown error code 3 from sa-update
ls /var/lib/spamassassin/3.004000/
sought_rules_yerp_org
sought_rules_yerp_org.cf
updates_spamassassin_org
updates_spamassassin_org.cf
rm -rf /var/lib/spamassassin/3.004002/
and then
sa-update -D
gives no errors,
but when I try to run cron job it takes a long time and does not finish:
/usr/share/spamassassin/sa-update.cron 2>&1 | tee -a /var/log/sa-update.log
  
Greetings,

atat [at] onet.eu

Re: sa-update error - config: invalid expression for rule T_MIXED_ES (fwd)

[Bill Cole]

On 9 Dec 2018, at 12:50, Kevin Walton wrote:


Hi

I am running:

SpamAssassin version 3.3.2
sa-update version svn917659


This is an unsupported obsolete version of SpamAssassin. If you are 
maintaining your own installation, you should update. If you are using a 
distribution maintained by someone else, you should urge them to upgrade 
their SA package or to backport a fix for this bug.


and I have been getting the following error for the last couple of 
days now when cron runs sa-update:


"
config:  invalid expression for rule T_MIXED_ES: "( __LOWER_E > 20 ) 
&& ( __E_LIKE_LETTER >
( (__LOWER_E * 14 ) / 10) ) && ( ( __E_LIKE_LETTER / __LOWER_E ) < 10 
)": division by zero

possible


Obviously, that's incorrect. As a Perl expression, the fact that '( 
__LOWER_E > 20 )' is first and the use of the short-circuiting logical 
and operator '&&' assures that the only division by a variable '( 
__E_LIKE_LETTER / __LOWER_E )' will never be evaluated if it could 
result in a division by zero.


This would be a bug in either SA v3.3.2 or the version of Perl you are 
using or in the combination of the two.



config: warning:  description exists for non-existent rule T_MIXED_ES

channel: lint check of update failed, channel failed
"


These are secondary to the initial incorrect judgment of T_MIXED_ES 
being invalid.



Running with -D, the error seems to be with the FreeMail plugin:


Not really...


"
Dec  9 16:12:19.254 [2525] dbg: plugin: loading 
Mail::SpamAssassin::Plugin::FreeMail from @INC
Dec  9 16:12:19.303 [2525] dbg: plugin: 
Mail::SpamAssassin::Plugin::FreeMail=HASH(0xc0d8f14) implements 
'parse_config', priority 0


This is noted because the plugin has a callback defined for 
'parse_config' which is called by Mail::SpamAssassin::Parser right 
before it proceeds to judging rules.


config:  invalid expression for rule T_MIXED_ES: "( __LOWER_E > 20 ) 
&& ( __E_LIKE_LETTER > ( (__LOWER_E * 14 ) / 10) ) && (

  ( __E_LIKE_LETTER / __LOWER_E ) < 10 )": division by zero possible

config: warning:  description exists for non-existent rule T_MIXED_ES
"

A google doesnt seem to bring up any help.  Any pointers much 
appretiated.


Update to non-obsolete software.

--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Available For Hire: https://linkedin.com/in/billcole

Re: SA-Update error "failed to run FORGED_GMAIL_RCVD test"

[David Jones]

On 01/30/2018 07:22 AM, David Jones wrote:

On 01/30/2018 06:46 AM, Alex wrote:

Hi,


Just spotted by others,
this diff fixes the problem:
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7540



Btw:
what's the state of 3.4.2+? Beta? Release?

from: http://spamassassin.apache.org/:
Latest News | 2015-04-30: SpamAssassin 3.4.1 has been released!

I didn't notice any announcements regarding SA versions !?


The current svn branch is 3.4, but it compiles to 3.4.2-pre3. Where is
the 3.4.2 referenced in this patch, or is it compiled without
IS_DEVEL_BUILD?


Now I see this check_for_forged_gmail_received_headers function was
just added to the 3.4 branch in the last few days.



https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7540

I will commit this version check for 3.4.2 patch in a few minutes when 
the test harness has completed but it will take a couple of days to 
actually get through the masscheck running and rule promotion process.




This is my sa-update.log file from this morning so at least the 3.4.1 
version of sa-update is doing a lint before applying the ruleset update. 
 This could fail for another two days until my recent commit works it's 
way through the rule promotion process.



Update available for channel updates.spamassassin.org: 1822491 -> 1822617
http: (curl) GET http://sa-update.spamassassin.org/1822617.tar.gz, success
http: (curl) GET http://sa-update.spamassassin.org/1822617.tar.gz.sha1, 
success
http: (curl) GET http://sa-update.spamassassin.org/1822617.tar.gz.asc, 
success

rules: failed to run FORGED_GMAIL_RCVD test, skipping:
(Can't locate object method 
"check_for_forged_gmail_received_headers" via package 
"Mail::SpamAssassin::PerMsgStatus" at (eval 1344) line 253.

)
channel: lint check of update failed, channel failed
Update failed, exiting with code 4
30-Jan-2018 05:37:28: SpamAssassin: Update available, but download or 
extract failed


--
David Jones

Re: SA-Update error "failed to run FORGED_GMAIL_RCVD test"

[David Jones]

On 01/30/2018 06:46 AM, Alex wrote:

Hi,


Just spotted by others,
this diff fixes the problem:
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7540



Btw:
what's the state of 3.4.2+? Beta? Release?

from: http://spamassassin.apache.org/:
Latest News | 2015-04-30: SpamAssassin 3.4.1 has been released!

I didn't notice any announcements regarding SA versions !?


The current svn branch is 3.4, but it compiles to 3.4.2-pre3. Where is
the 3.4.2 referenced in this patch, or is it compiled without
IS_DEVEL_BUILD?


Now I see this check_for_forged_gmail_received_headers function was
just added to the 3.4 branch in the last few days.



https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7540

I will commit this version check for 3.4.2 patch in a few minutes when 
the test harness has completed but it will take a couple of days to 
actually get through the masscheck running and rule promotion process.


--
David Jones

Re: SA-Update error "failed to run FORGED_GMAIL_RCVD test"

[Kevin A. McGrail]

On 1/30/2018 7:46 AM, Alex wrote:

Now I see this check_for_forged_gmail_received_headers function was
just added to the 3.4 branch in the last few days.
Yes, whoever added the rule needs to be more careful.  Not saying names 
(or initials :-) ).


Regards,
KAM

Re: SA-Update error "failed to run FORGED_GMAIL_RCVD test"

[Alex]

Hi,

>> Just spotted by others,
>> this diff fixes the problem:
>> https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7540
>
>> Btw:
>> what's the state of 3.4.2+? Beta? Release?
>>
>> from: http://spamassassin.apache.org/:
>> Latest News | 2015-04-30: SpamAssassin 3.4.1 has been released!
>>
>> I didn't notice any announcements regarding SA versions !?
>
> The current svn branch is 3.4, but it compiles to 3.4.2-pre3. Where is
> the 3.4.2 referenced in this patch, or is it compiled without
> IS_DEVEL_BUILD?

Now I see this check_for_forged_gmail_received_headers function was
just added to the 3.4 branch in the last few days.

Re: SA-Update error "failed to run FORGED_GMAIL_RCVD test"

[Alex]

Hi,


> Just spotted by others,
> this diff fixes the problem:
> https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7540

> Btw:
> what's the state of 3.4.2+? Beta? Release?
>
> from: http://spamassassin.apache.org/:
> Latest News | 2015-04-30: SpamAssassin 3.4.1 has been released!
>
> I didn't notice any announcements regarding SA versions !?

The current svn branch is 3.4, but it compiles to 3.4.2-pre3. Where is
the 3.4.2 referenced in this patch, or is it compiled without
IS_DEVEL_BUILD?

Re: SA-Update error "failed to run FORGED_GMAIL_RCVD test"

[Matthias Egger]

Hello Giovanni,

On 01/30/2018 12:55 PM, Giovanni Bechis wrote:
> On 01/30/18 12:43, A. Schulze wrote:
>>
>> Hello all,
>>
>> shortly (since around 09:30 UTC) I get such notifications on sa-update:
>>
>> rules: failed to run FORGED_GMAIL_RCVD test, skipping:
>> (Can't locate object method "check_for_forged_gmail_received_headers" 
>> via package "Mail::SpamAssassin::PerMsgStatus" at (eval 1277) line 253.
>> )
>> channel: lint check of update failed, channel failed
>>
>>
>> looks like the new version "1822617" is `other the former releases` :-)
>>
> Just spotted by others,
> this diff fixes the problem:
> https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7540
>  Giovanni

Thank you for that. Any idea when it will be downloadable? Currently the
DNS records still point to the faulty "1822617" Version.

# dig +short TXT 0.4.3.updates.spamassassin.org
"1822617"

And since the update of the current SA rules failes because of that
error, there seems to be no need to update or patch any diff manually
(because as far as i understand SA still works with the un-updated but
errorless version).

Best regards
Matthias
-- 
Matthias Egger
ETH Zurich
Department of Information Technology  maeg...@ee.ethz.ch
and Electrical Engineering
IT Support Group (ISG.EE), ETF/D/102  Phone +41 (0)44 632 03 90
Sternwartstrasse 7, CH-8092 ZurichFax   +41 (0)44 632 11 95



smime.p7s
Description: S/MIME Cryptographic Signature

Re: SA-Update error "failed to run FORGED_GMAIL_RCVD test"

[A. Schulze]

Giovanni Bechis:


Just spotted by others,
this diff fixes the problem:
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7540


yea! but that's a patch for the rules, right?
may we expect a fixed ruleset will be published shortly?

Andreas


Btw:
what's the state of 3.4.2+? Beta? Release?

from: http://spamassassin.apache.org/:
Latest News | 2015-04-30: SpamAssassin 3.4.1 has been released!

I didn't notice any announcements regarding SA versions !?

Re: SA-Update error "failed to run FORGED_GMAIL_RCVD test"

[Giovanni Bechis]

On 01/30/18 12:43, A. Schulze wrote:
> 
> Hello all,
> 
> shortly (since around 09:30 UTC) I get such notifications on sa-update:
> 
> rules: failed to run FORGED_GMAIL_RCVD test, skipping:
> (Can't locate object method "check_for_forged_gmail_received_headers" via 
> package "Mail::SpamAssassin::PerMsgStatus" at (eval 1277) line 253.
> )
> channel: lint check of update failed, channel failed
> 
> 
> looks like the new version "1822617" is `other the former releases` :-)
> 
Just spotted by others,
this diff fixes the problem:
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7540
 Giovanni


> Here some logs.
> 
> Jan 30 12:37:24.803 [21958] dbg: rules: ran header rule __HAS_MSGID ==> 
> got hit: "<"
> Jan 30 12:37:24.804 [21958] dbg: rules: ran header rule __SANE_MSGID ==> 
> got hit: "<1517312243@lint_rules>
> Jan 30 12:37:24.804 [21958] dbg: rules: [...] "
> Jan 30 12:37:24.804 [21958] dbg: rules: ran header rule __TO_NO_ARROWS_R 
> ==> got hit: "3.4"
> Jan 30 12:37:24.804 [21958] dbg: rules: ran header rule __HAS_FROM ==> 
> got hit: ""
> Jan 30 12:37:24.805 [21958] dbg: rules: running head_eval tests; score so 
> far=0
> Jan 30 12:37:24.806 [21958] dbg: rules: run_eval_tests - compiling eval code: 
> 9, priority 0
> Jan 30 12:37:24.811 [21958] dbg: FreeMail: RULE (FREEMAIL_FROM) 
> check_freemail_from
> Jan 30 12:37:24.811 [21958] dbg: FreeMail: all from-addresses: 
> ign...@compiling.spamassassin.taint.org
> rules: failed to run FORGED_GMAIL_RCVD test, skipping:
>     (Can't locate object method "check_for_forged_gmail_received_headers" 
> via package "Mail::SpamAssassin::PerMsgStatus" at (eval 1279) line 271.
> )
> Jan 30 12:37:24.812 [21958] dbg: FreeMail: RULE (__freemail_reply) 
> check_freemail_replyto
> Jan 30 12:37:24.812 [21958] dbg: FreeMail: From address: 
> ign...@compiling.spamassassin.taint.org
> Jan 30 12:37:24.812 [21958] dbg: FreeMail: No Reply-To and From is not 
> freemail, skipping check
> Jan 30 12:37:24.812 [21958] dbg: rules: ran eval rule NO_RELAYS ==> got 
> hit (1)
> Jan 30 12:37:24.813 [21958] dbg: rules: ran eval rule 
> __GATED_THROUGH_RCVD_REMOVER ==> got hit (1)
> 
> SA-Version: 3.4.1
> perl-Version: 5.01 (old, yes, I know ...)
> 
> 
> 
> 
> Andreas
> 

Re: sa-update error

[Benny Pedersen]

On Tue, June 9, 2009 17:33, Bowie Bailey wrote:
> I have a CentOS 5.3 system with everything installed from the repos and
> my @INC looks exactly the same, so I don't necessarily see a problem
> with the versions here.

problem is that some users of yum, rpm, and friends forget to make
reinstall of all non perl core modules after new perl version is installed

and since you just use repos from main stream, maintainers know how to
make a old perl stay in your disk :)

in gentoo "emerge --depclean" to have gentoo portage remove ebuild not
needed anymore, i suppose yum, rpm can beat it ?

-- 
http://localhost/ 100% uptime and 100% mirrored :)

Re: sa-update error

[Bowie Bailey]

Benny Pedersen wrote:

On Mon, June 8, 2009 14:41, snowweb wrote:

  

Then I tried again with sa-update and got the following:

[r...@s1 spamassassin]# sa-update
Can't locate Archive/Tar.pm in @INC (@INC contains:
/usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi /usr/lib/per
l5/site_perl/5.8.8 /usr/lib/perl5/site_perl/5.8.7/i386-linux-thread-multi
/usr/lib/perl5/site_perl/5.8.6/i386-linux-thr
ead-multi /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi
/usr/lib/perl5/site_perl/5.8.7 /usr/lib/perl5/site_per
l/5.8.6 /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl
/usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-mult
i /usr/lib/perl5/vendor_perl/5.8.7/i386-linux-thread-multi
/usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi /us
r/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi
/usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl/5.8.7
 /usr/lib/perl5/vendor_perl/5.8.6 /usr/lib/perl5/vendor_perl/5.8.5
/usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.8/i386
-linux-thread-multi /usr/lib/perl5/5.8.8) at /usr/bin/sa-update l



5.8.5
5.8.6
5.8.7
5.8.8

4 perl versions, are your distro out of there mind ? :)
  


I have a CentOS 5.3 system with everything installed from the repos and 
my @INC looks exactly the same, so I don't necessarily see a problem 
with the versions here.


--
Bowie

Re: sa-update error

[Benny Pedersen]

On Tue, June 9, 2009 03:48, LuKreme wrote:
> Second off, there is absolutely nothing wrong with using CPAN.

OP problem is mix of CPAN and RPM, he dont need both to solve it

CPAN is usefull if one makes RPM with it, but most belive its better just
to follow guides and use CPAN shells, when distro is RPM based

-- 
http://localhost/ 100% uptime and 100% mirrored :)

Re: sa-update error

[LuKreme]

On 8-Jun-2009, at 16:50, Benny Pedersen wrote:

On Mon, June 8, 2009 15:26, The Doctor wrote:


You can either use cpan or http://search.cpan.org .


bad advise !


First off, it's 'advice' (the noun) in this case, not 'advise' (the  
verb).


Second off, there is absolutely nothing wrong with using CPAN.


--
Well, I've wrestled with reality for 35 years, Doctor, and I'm happy  
to state I finally won out over it.

Re: sa-update error

[Benny Pedersen]

On Tue, June 9, 2009 00:59, Martin Gregorie wrote:
> On Tue, 2009-06-09 at 00:39 +0200, Benny Pedersen wrote:
>> does there exists a perl-cleanup in you distro ?
>>
> There's not a general one. On the assumption (true for Fedora) that both
> Perl and SA are distro supported packages, if I was tackling this I'd do
> the following:
>
> - make safety copies of SA customisation.
> - yum remove perl spamassassin
> - updatedb
> - use 'locate perl' to see if there are any other copies of perl -
>   there is in this case. At a guess it is a CPAN install.
> - remove it using 'rm -rf' as it is unlikely to be an RPM package
> - check that Perl is definitely gone. (updatedb; locate perl)
> - get the latest distro versions: yum install perl spamassassin
> - replace SA customisation if it got overwritten.
> - check that the default PATH doesn't point to anything that was
>   removed. It is set up in /etc/profile plus extras from /etc/profile.d

yes, when no perl is installed you can yum install spamassassin as it was
ment to from distros, if still problem with

spamassassin 2>&1 -D --lint

after this then report it to your distro as a dependice problem

i remember perl problems from my old freebsd 4.9 :=)

newer happended on gentoo here


-- 
http://localhost/ 100% uptime and 100% mirrored :)

Re: sa-update error

[Martin Gregorie]

On Tue, 2009-06-09 at 00:39 +0200, Benny Pedersen wrote:
> does there exists a perl-cleanup in you distro ?
> 
There's not a general one. On the assumption (true for Fedora) that both
Perl and SA are distro supported packages, if I was tackling this I'd do
the following:

- make safety copies of SA customisation.
- yum remove perl spamassassin
- updatedb
- use 'locate perl' to see if there are any other copies of perl - 
  there is in this case. At a guess it is a CPAN install.
- remove it using 'rm -rf' as it is unlikely to be an RPM package
- check that Perl is definitely gone. (updatedb; locate perl)
- get the latest distro versions: yum install perl spamassassin
- replace SA customisation if it got overwritten.
- check that the default PATH doesn't point to anything that was
  removed. It is set up in /etc/profile plus extras from /etc/profile.d

Martin

Re: sa-update error

[Benny Pedersen]

On Mon, June 8, 2009 15:26, The Doctor wrote:

> You can either use cpan or http://search.cpan.org .

bad advise !

-- 
http://localhost/ 100% uptime and 100% mirrored :)

Re: sa-update error

[Benny Pedersen]

On Mon, June 8, 2009 15:04, snowweb wrote:

> so I guess it's fixed.

until next time there is a new perl version yes :/

newer mix CPAN with a RPM system !


-- 
http://localhost/ 100% uptime and 100% mirrored :)

Re: sa-update error

[Benny Pedersen]

On Mon, June 8, 2009 14:41, snowweb wrote:

> Then I tried again with sa-update and got the following:
>
> [r...@s1 spamassassin]# sa-update
> Can't locate Archive/Tar.pm in @INC (@INC contains:
> /usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi /usr/lib/per
> l5/site_perl/5.8.8 /usr/lib/perl5/site_perl/5.8.7/i386-linux-thread-multi
> /usr/lib/perl5/site_perl/5.8.6/i386-linux-thr
> ead-multi /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi
> /usr/lib/perl5/site_perl/5.8.7 /usr/lib/perl5/site_per
> l/5.8.6 /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl
> /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-mult
> i /usr/lib/perl5/vendor_perl/5.8.7/i386-linux-thread-multi
> /usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi /us
> r/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi
> /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl/5.8.7
>  /usr/lib/perl5/vendor_perl/5.8.6 /usr/lib/perl5/vendor_perl/5.8.5
> /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.8/i386
> -linux-thread-multi /usr/lib/perl5/5.8.8) at /usr/bin/sa-update l

5.8.5
5.8.6
5.8.7
5.8.8

4 perl versions, are your distro out of there mind ? :)

-- 
http://localhost/ 100% uptime and 100% mirrored :)

Re: sa-update error

[Benny Pedersen]

On Mon, June 8, 2009 14:30, snowweb wrote:
>
> When I do "which perl" it only returns,
>
> "/usr/bin/perl"

unsure if thats relayted

> doesn't this mean that I only have one installed? (I'm not arguing.. just
> trying to understand, since I'm new to Linux).

spamassassin 2>&1 -D --lint

grep 5.8 on it

if you see 5.8.6 and 5.8.8 there we go

try remove the old perl version, but make sure all modules in 5.8.8 is
installed first

does there exists a perl-cleanup in you distro ?

-- 
http://localhost/ 100% uptime and 100% mirrored :)

Re: sa-update error

[Benny Pedersen]

On Mon, June 8, 2009 14:27, snowweb wrote:
> Sorry for my ignorance. I'm very new to Linux. Which missing perl module
> is that please?

there is non missing, you just have another perl version that miss it, how
to resolve problem with 2 versions of perl with yum i dont know, but solve
this and the remaining problem with mission perl modules will wanish at
the same time, if not ask distro maintainers for help on that issue, its
not a spamassassin problem

-- 
http://localhost/ 100% uptime and 100% mirrored :)

Re: sa-update error

[Matus UHLAR - fantomas]

On 08.06.09 06:04, snowweb wrote:
> Guys, thanks to you all. You're all the most helpful people I've come across
> online!
> 
> I think Stefan-Michael Guenther fixed it when he emailed me and told me to
> run this:
> 
> perl -MCPAN -e shell
> install Archive::Tar
> 
> Now when I type "sa-update", although I don't get any feedback, I don't get
> any errors either, so I guess it's fixed.

I don't think this is a good solution - all possible packages should be
installed through your package system, which ir apparently yum/RPM.
Otherwise, you may cause even more problems in the future.

So, make sure you have only one perl installed, that it's installed using
yum and if you can install Archive::Tar through yum (maybe archive-tar or
perl-archive-tar package), do that.

Proper packaging system should take care of dependencies, from SA to perl
and its packages, so your problem should not even happen!

And, of course, such questions belong more to your packaging systems'
mailing list, not here...

-- 
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Due to unexpected conditions Windows 2000 will be released
in first quarter of year 1901

Re: sa-update error

[The Doctor]

On Mon, Jun 08, 2009 at 03:30:59AM -0700, snowweb wrote:
> 
> I've just heard about sa-update and tried to run it. I was thinking of
> setting up a cron to do it daily, however, I got the following error message
> when I ran it manually:
> 
> [r...@s1 spamassassin]# sa-update && service spamassassin restart
> Can't locate Archive/Tar.pm in @INC (@INC contains:
> /usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi /usr/lib/per
> l5/site_perl/5.8.8 /usr/lib/perl5/site_perl/5.8.7/i386-linux-thread-multi
> /usr/lib/perl5/site_perl/5.8.6/i386-linux-thr
> ead-multi /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi
> /usr/lib/perl5/site_perl/5.8.7 /usr/lib/perl5/site_per
> l/5.8.6 /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl
> /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-mult
> i /usr/lib/perl5/vendor_perl/5.8.7/i386-linux-thread-multi
> /usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi /us
> r/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi
> /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl/5.8.7
>  /usr/lib/perl5/vendor_perl/5.8.6 /usr/lib/perl5/vendor_perl/5.8.5
> /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.8/i386
> -linux-thread-multi /usr/lib/perl5/5.8.8) at /usr/bin/sa-update line 81.
> BEGIN failed--compilation aborted at /usr/bin/sa-update line 81.
> 
> Any ideas please?
>

You need to install Archive-Tar .

You can either use cpan or http://search.cpan.org .
 
> pete
> -- 
> View this message in context: 
> http://www.nabble.com/sa-update-error-tp23921654p23921654.html
> Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
> 
> 
> -- 
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> 

-- 
Member - Liberal International  This is doc...@nl2k.ab.ca
Ici doc...@nl2k.ab.ca God, Queen and country! Beware Anti-Christ rising!
Never Satan President Republic!
Rudeness is the weak man's imitation of strength.  -Eric Hoffer 

Re: sa-update error

[snowweb]

Guys, thanks to you all. You're all the most helpful people I've come across
online!

I think Stefan-Michael Guenther fixed it when he emailed me and told me to
run this:

perl -MCPAN -e shell
install Archive::Tar

Now when I type "sa-update", although I don't get any feedback, I don't get
any errors either, so I guess it's fixed.

regards and many thanks

pete



snowweb wrote:
> 
> I've just heard about sa-update and tried to run it. I was thinking of
> setting up a cron to do it daily, however, I got the following error
> message when I ran it manually:
> 
> [r...@s1 spamassassin]# sa-update && service spamassassin restart
> Can't locate Archive/Tar.pm in @INC (@INC contains:
> /usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi /usr/lib/per
> l5/site_perl/5.8.8 /usr/lib/perl5/site_perl/5.8.7/i386-linux-thread-multi
> /usr/lib/perl5/site_perl/5.8.6/i386-linux-thr
> ead-multi /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi
> /usr/lib/perl5/site_perl/5.8.7 /usr/lib/perl5/site_per
> l/5.8.6 /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl
> /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-mult
> i /usr/lib/perl5/vendor_perl/5.8.7/i386-linux-thread-multi
> /usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi /us
> r/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi
> /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl/5.8.7
>  /usr/lib/perl5/vendor_perl/5.8.6 /usr/lib/perl5/vendor_perl/5.8.5
> /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.8/i386
> -linux-thread-multi /usr/lib/perl5/5.8.8) at /usr/bin/sa-update line 81.
> BEGIN failed--compilation aborted at /usr/bin/sa-update line 81.
> 
> Any ideas please?
> 
> pete
> 

-- 
View this message in context: 
http://www.nabble.com/sa-update-error-tp23921654p23923677.html
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.

Re: sa-update error

[Mark Wendt (Contractor)]

Using the command "which perl" will only turn up the first instance 
of perl in your path.  Try this: cd to the root directory, then type 
"find . -name perl -print" and hit return.  The find command will 
recursively search through all the directories on the machine and 
locate all files named "perl".


Mark


At 08:50 AM 6/8/2009, snowweb wrote:


I tested for two versions of perl using "which perl" and it only returned one
location.

I'm using CentOS 5.0 and I'm running DirectAdmin hosting software. The SA
was installed by the script which installed the DirectAdmin. I don't
understand how or where it got the SA from. Again, I don't know where the
perl came from either. Is there a way I can find out?

How will I check whether I have an incorrectly set environment variable
PERL5LIB set somewhere in startup/config files?

I should also mention that apart from the sa-update not working (and
FuzzyOcr SA plugin which I'm also working on), SA is working ok.

Thanks for your help Matus,

pete





Matus UHLAR - fantomas wrote:
>
> IIRC another answer said you probably have two perl versions installed
> separately. Check for that first. Then, check these:
>
> - which software (linux) distribution do you have?
> - do you have spamassassin installed from the distribution?
> - do you have perl installed from the distribution?
> - don't you have incorrectly set environment variable PERL5LIB set
> somewhere
> in startup/config files?
>

--
View this message in context: 
http://www.nabble.com/sa-update-error-tp23921654p23923417.html

Sent from the SpamAssassin - Users mailing list archive at Nabble.com.

Re: sa-update error

[snowweb]

I tested for two versions of perl using "which perl" and it only returned one
location.

I'm using CentOS 5.0 and I'm running DirectAdmin hosting software. The SA
was installed by the script which installed the DirectAdmin. I don't
understand how or where it got the SA from. Again, I don't know where the
perl came from either. Is there a way I can find out?

How will I check whether I have an incorrectly set environment variable
PERL5LIB set somewhere in startup/config files?

I should also mention that apart from the sa-update not working (and
FuzzyOcr SA plugin which I'm also working on), SA is working ok.

Thanks for your help Matus,

pete





Matus UHLAR - fantomas wrote:
> 
> IIRC another answer said you probably have two perl versions installed
> separately. Check for that first. Then, check these:
> 
> - which software (linux) distribution do you have? 
> - do you have spamassassin installed from the distribution?
> - do you have perl installed from the distribution?
> - don't you have incorrectly set environment variable PERL5LIB set
> somewhere
> in startup/config files?
> 

-- 
View this message in context: 
http://www.nabble.com/sa-update-error-tp23921654p23923417.html
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.

Re: sa-update error

[snowweb]

I just ran "yum upgrade spamassassin" and this was the result:

[r...@s1 spamassassin]# yum upgrade spamassassin
Loading "installonlyn" plugin
Setting up Upgrade Process
Setting up repositories
dag   100% |=| 1.1 kB00:00
openwebmail   100% |=|  951 B00:00
base  100% |=| 1.1 kB00:00
updates   100% |=|  951 B00:00
addons100% |=|  951 B00:00
extras100% |=| 1.1 kB00:00
Reading repository metadata in from local files
primary.xml.gz100% |=| 3.1 MB00:10
## 8680/8680
Excluding Packages in global exclude list
Finished
Could not find update match for spamassassin
No Packages marked for Update/Obsoletion

Then I tried again with sa-update and got the following:

[r...@s1 spamassassin]# sa-update
Can't locate Archive/Tar.pm in @INC (@INC contains:
/usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi /usr/lib/per
l5/site_perl/5.8.8 /usr/lib/perl5/site_perl/5.8.7/i386-linux-thread-multi
/usr/lib/perl5/site_perl/5.8.6/i386-linux-thr
ead-multi /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi
/usr/lib/perl5/site_perl/5.8.7 /usr/lib/perl5/site_per
l/5.8.6 /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl
/usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-mult
i /usr/lib/perl5/vendor_perl/5.8.7/i386-linux-thread-multi
/usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi /us
r/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi
/usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl/5.8.7
 /usr/lib/perl5/vendor_perl/5.8.6 /usr/lib/perl5/vendor_perl/5.8.5
/usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.8/i386
-linux-thread-multi /usr/lib/perl5/5.8.8) at /usr/bin/sa-update l

pete



Nigel Frankcom-2 wrote:
> 
> On Mon, 8 Jun 2009 03:30:59 -0700 (PDT), snowweb 
> wrote:
> 
>>
>>I've just heard about sa-update and tried to run it. I was thinking of
>>setting up a cron to do it daily, however, I got the following error
message
>>when I ran it manually:
>>
>>[r...@s1 spamassassin]# sa-update && service spamassassin restart
>>Can't locate Archive/Tar.pm in @INC (@INC contains:
>>/usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi /usr/lib/per
>>l5/site_perl/5.8.8 /usr/lib/perl5/site_perl/5.8.7/i386-linux-thread-multi
>>/usr/lib/perl5/site_perl/5.8.6/i386-linux-thr
>>ead-multi /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi
>>/usr/lib/perl5/site_perl/5.8.7 /usr/lib/perl5/site_per
>>l/5.8.6 /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl
>>/usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-mult
>>i /usr/lib/perl5/vendor_perl/5.8.7/i386-linux-thread-multi
>>/usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi /us
>>r/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi
>>/usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl/5.8.7
>> /usr/lib/perl5/vendor_perl/5.8.6 /usr/lib/perl5/vendor_perl/5.8.5
>>/usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.8/i386
>>-linux-thread-multi /usr/lib/perl5/5.8.8) at /usr/bin/sa-update line 81.
>>BEGIN failed--compilation aborted at /usr/bin/sa-update line 81.
>>
>>Any ideas please?
>>
>>pete
> 
> I think the Tar package is available via yum if you want an easy way
> to keep it current. If not Install it via CPAN. You may need to
> restart SA after, not sure.
> 
> It may also be worth running "spamassassin --lint -D" to see if you
> are missing any other packages.
> 
> HTH
> 
> Nigel
> 
> 

-- 
View this message in context: 
http://www.nabble.com/sa-update-error-tp23921654p23923296.html
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.

Re: sa-update error

[Matus UHLAR - fantomas]

> > On Mon, 2009-06-08 at 03:30 -0700, an anonymous Nabble user wrote:
> >> I've just heard about sa-update and tried to run it. I was thinking of
> >> setting up a cron to do it daily, however, I got the following error
> >> message when I ran it manually:
> >> 
> >> [r...@s1 spamassassin]# sa-update && service spamassassin restart
> >> Can't locate Archive/Tar.pm in @INC (@INC contains:
> > 
> >> BEGIN failed--compilation aborted at /usr/bin/sa-update line 81.
> >> 
> >> Any ideas please?

> Karsten Bräckelmann-2 wrote:
> > Install the missing Perl module...?

On 08.06.09 05:27, snowweb wrote:
> Sorry for my ignorance. I'm very new to Linux. Which missing perl module is
> that please?

IIRC another answer said you probably have two perl versions installed
separately. Check for that first. Then, check these:

- which software (linux) distribution do you have? 
- do you have spamassassin installed from the distribution?
- do you have perl installed from the distribution?
- don't you have incorrectly set environment variable PERL5LIB set somewhere
in startup/config files?

-- 
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
(R)etry, (A)bort, (C)ancer

Re: sa-update error

[snowweb]

When I do "which perl" it only returns,

"/usr/bin/perl"

doesn't this mean that I only have one installed? (I'm not arguing.. just
trying to understand, since I'm new to Linux).

pete



Benny Pedersen wrote:
> 
> 
> On Mon, June 8, 2009 12:55, Nigel Frankcom wrote:
> 
>> It may also be worth running "spamassassin --lint -D" to see if you
>> are missing any other packages.
> 
> you have currently 2 perl versions installed
> 
> this is the problem, if not all modules exists in 5.8.8, but some only
> does in 5.8.6
> 
> 
> -- 
> http://localhost/ 100% uptime and 100% mirrored :)
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/sa-update-error-tp23921654p23923139.html
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.

Re: sa-update error

[snowweb]

Sorry for my ignorance. I'm very new to Linux. Which missing perl module is
that please?

pete


Karsten Bräckelmann-2 wrote:
> 
> On Mon, 2009-06-08 at 03:30 -0700, an anonymous Nabble user wrote:
>> I've just heard about sa-update and tried to run it. I was thinking of
>> setting up a cron to do it daily, however, I got the following error
>> message
>> when I ran it manually:
>> 
>> [r...@s1 spamassassin]# sa-update && service spamassassin restart
>> Can't locate Archive/Tar.pm in @INC (@INC contains:
> 
>> BEGIN failed--compilation aborted at /usr/bin/sa-update line 81.
>> 
>> Any ideas please?
> 
> Install the missing Perl module...?
> 
> 
> -- 
> char
> *t="\10pse\0r\0dtu...@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
> main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i c<<=1:
> (c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0;
> }}}
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/sa-update-error-tp23921654p23923079.html
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.

Re: sa-update error

[Benny Pedersen]

On Mon, June 8, 2009 12:55, Nigel Frankcom wrote:

> It may also be worth running "spamassassin --lint -D" to see if you
> are missing any other packages.

you have currently 2 perl versions installed

this is the problem, if not all modules exists in 5.8.8, but some only
does in 5.8.6


-- 
http://localhost/ 100% uptime and 100% mirrored :)

Re: sa-update error

[Nigel Frankcom]

On Mon, 8 Jun 2009 03:30:59 -0700 (PDT), snowweb 
wrote:

>
>I've just heard about sa-update and tried to run it. I was thinking of
>setting up a cron to do it daily, however, I got the following error message
>when I ran it manually:
>
>[r...@s1 spamassassin]# sa-update && service spamassassin restart
>Can't locate Archive/Tar.pm in @INC (@INC contains:
>/usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi /usr/lib/per
>l5/site_perl/5.8.8 /usr/lib/perl5/site_perl/5.8.7/i386-linux-thread-multi
>/usr/lib/perl5/site_perl/5.8.6/i386-linux-thr
>ead-multi /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi
>/usr/lib/perl5/site_perl/5.8.7 /usr/lib/perl5/site_per
>l/5.8.6 /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl
>/usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-mult
>i /usr/lib/perl5/vendor_perl/5.8.7/i386-linux-thread-multi
>/usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi /us
>r/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi
>/usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl/5.8.7
> /usr/lib/perl5/vendor_perl/5.8.6 /usr/lib/perl5/vendor_perl/5.8.5
>/usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.8/i386
>-linux-thread-multi /usr/lib/perl5/5.8.8) at /usr/bin/sa-update line 81.
>BEGIN failed--compilation aborted at /usr/bin/sa-update line 81.
>
>Any ideas please?
>
>pete

I think the Tar package is available via yum if you want an easy way
to keep it current. If not Install it via CPAN. You may need to
restart SA after, not sure.

It may also be worth running "spamassassin --lint -D" to see if you
are missing any other packages.

HTH

Nigel

Re: sa-update error

[Karsten Bräckelmann]

On Mon, 2009-06-08 at 03:30 -0700, an anonymous Nabble user wrote:
> I've just heard about sa-update and tried to run it. I was thinking of
> setting up a cron to do it daily, however, I got the following error message
> when I ran it manually:
> 
> [r...@s1 spamassassin]# sa-update && service spamassassin restart
> Can't locate Archive/Tar.pm in @INC (@INC contains:

> BEGIN failed--compilation aborted at /usr/bin/sa-update line 81.
> 
> Any ideas please?

Install the missing Perl module...?


-- 
char *t="\10pse\0r\0dtu...@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}

Re: SA-update error

[Matt Kettler]

Dennis Clark wrote:

Using Spamassassin 3.1.8.  I haven't updated SA in about six months.  Ran SA-update -D 
using the default channel of updates.spamassassin.org, received error "new version 
is 585884, skipped channel".

What exactly is going wrong here.  Has the sa update default channel been 
changed?
  
No, but there also haven't been any sa-updates posted to 3.1.x in a long 
time, so I wouldn't be surprised to find you're already "up to date" for 
that version.


We've been on the 3.2.x series since May of last year. The current 
release is 3.2.4, and 3.3.0 is starting to show signs of forming on the 
horizon.

RE: SA-update error

[Michael Hutchinson]

> -Original Message-
> From: Dennis Clark [mailto:[EMAIL PROTECTED]
> Sent: Thursday, 27 March 2008 3:18 p.m.
> To: users@spamassassin.apache.org
> Subject: SA-update error
> 
> Using Spamassassin 3.1.8.  I haven't updated SA in about six months.
Ran
> SA-update -D using the default channel of updates.spamassassin.org,
> received error "new version is 585884, skipped channel".
> 
> What exactly is going wrong here.  Has the sa update default channel
been
> changed?

You need, perhaps, to copy and paste a bit more of the "sa-update -D"
output. 

>From the snippet you provided, many people could easily make the
assumption that it's simply skipping the channel, because it is already
up to date. 
I would make this assumption also, without seeing more from the output
of your "sa-update -D"

Cheers,
Mike

Re: SA-update error

[Theo Van Dinter]

On Wed, Mar 26, 2008 at 06:18:02PM -0800, Dennis Clark wrote:
> Using Spamassassin 3.1.8.  I haven't updated SA in about six months.  Ran 
> SA-update -D using the default channel of updates.spamassassin.org, received 
> error "new version is 585884, skipped channel".
> 
> What exactly is going wrong here.  Has the sa update default channel been 
> changed?

You'd want to pastebot your debug output somewhere.  My guess is that your
installed version == new version, so there was nothing to do.

-- 
Randomly Selected Tagline:
"I don't even have to get dressed up for Halloween.  I go as me." - Judge Judy


pgpeAHS48Gu3T.pgp
Description: PGP signature

RE: sa-update error wrong gpg key...

[Steve Monkhouse]

Hey guys.. 

We're seeing the same thing.. although slightly different.. this error has
only been happening for a week or so now.. everything's been fine before
that.. it seems to be with the RSA key generated on 15Jan.. 

An sa-update -D shows :

[/usr/local/etc/mail/spamassassin]# sa-update -D
[56267] dbg: logger: adding facilities: all
[56267] dbg: logger: logging level is DBG
[56267] dbg: generic: SpamAssassin version 3.2.4
[56267] dbg: config: score set 0 chosen.
[56267] dbg: dns: is Net::DNS::Resolver available? yes
[56267] dbg: dns: Net::DNS version: 0.62
[56267] dbg: generic: sa-update version svn607589
[56267] dbg: generic: using update directory: /var/db/spamassassin/3.002004
[56267] dbg: diag: perl platform: 5.008008 freebsd
[56267] dbg: diag: module installed: Digest::SHA1, version 2.11
[56267] dbg: diag: module installed: HTML::Parser, version 3.56
[56267] dbg: diag: module installed: Net::DNS, version 0.62
[56267] dbg: diag: module installed: MIME::Base64, version 3.07
[56267] dbg: diag: module installed: DB_File, version 1.814
[56267] dbg: diag: module installed: Net::SMTP, version 2.31
[56267] dbg: diag: module not installed: Mail::SPF ('require' failed)
[56267] dbg: diag: module not installed: Mail::SPF::Query ('require' failed)
[56267] dbg: diag: module not installed: IP::Country::Fast ('require'
failed)
[56267] dbg: diag: module installed: Razor2::Client::Agent, version 2.84
[56267] dbg: diag: module not installed: Net::Ident ('require' failed)
[56267] dbg: diag: module installed: IO::Socket::INET6, version 2.51
[56267] dbg: diag: module installed: IO::Socket::SSL, version 1.12
[56267] dbg: diag: module installed: Compress::Zlib, version 2.008
[56267] dbg: diag: module installed: Time::HiRes, version 1.9711
[56267] dbg: diag: module not installed: Mail::DomainKeys ('require' failed)
[56267] dbg: diag: module not installed: Mail::DKIM ('require' failed)
[56267] dbg: diag: module installed: DBI, version 1.601
[56267] dbg: diag: module installed: Getopt::Long, version 2.35
[56267] dbg: diag: module installed: LWP::UserAgent, version 2.033
[56267] dbg: diag: module installed: HTTP::Date, version 1.47
[56267] dbg: diag: module installed: Archive::Tar, version 1.38
[56267] dbg: diag: module installed: IO::Zlib, version 1.07
[56267] dbg: diag: module installed: Encode::Detect, version 1.00
[56267] dbg: gpg: Searching for 'gpg'
[56267] dbg: util: current PATH is:
/sbin:/usr/sbin:/bin:/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/X11R6/bin
[56267] dbg: util: executable for gpg was found at /usr/local/bin/gpg
[56267] dbg: gpg: found /usr/local/bin/gpg
[56267] dbg: gpg: release trusted key id list:
5E541DC959CB8BAC7C78DFDC4056A61A5244EC45
26C900A46DD40CD5AD24F6D7DEE01987265FA05B
0C2B1D7175B852C64B3CDC716C55397824F434CE
[56267] dbg: channel: attempting channel updates.spamassassin.org
[56267] dbg: channel: update directory
/var/db/spamassassin/3.002004/updates_spamassassin_org
[56267] dbg: channel: channel cf file
/var/db/spamassassin/3.002004/updates_spamassassin_org.cf
[56267] dbg: channel: channel pre file
/var/db/spamassassin/3.002004/updates_spamassassin_org.pre
[56267] dbg: dns: 4.2.3.updates.spamassassin.org => 611820, parsed as 611820
[56267] dbg: channel: preparing temp directory for new channel
[56267] dbg: generic: update tmp directory /tmp/.spamassassin56267NDLylZtmp
[56267] dbg: generic: lint checking site pre files once before attempting
channel updates
[56267] dbg: generic: SpamAssassin version 3.2.4
[56267] dbg: config: score set 0 chosen.
[56267] dbg: dns: is Net::DNS::Resolver available? yes
[56267] dbg: dns: Net::DNS version: 0.62
[56267] dbg: ignore: using a test message to lint rules
[56267] dbg: config: using "/usr/local/etc/mail/spamassassin" for site rules
pre files
[56267] dbg: config: read file /usr/local/etc/mail/spamassassin/init.pre
[56267] dbg: config: read file /usr/local/etc/mail/spamassassin/v310.pre
[56267] dbg: config: read file /usr/local/etc/mail/spamassassin/v312.pre
[56267] dbg: config: read file /usr/local/etc/mail/spamassassin/v320.pre
[56267] dbg: config: using "/tmp/.spamassassin56267NDLylZtmp/doesnotexist"
for sys rules pre files
[56267] dbg: config: using "/tmp/.spamassassin56267NDLylZtmp/doesnotexist"
for default rules dir
[56267] dbg: config: using
"/tmp/.spamassassin56267NDLylZtmp/doesnotexist/doesnotexist" for user prefs
file
[56267] dbg: plugin: loading Mail::SpamAssassin::Plugin::URIDNSBL from @INC
[56267] dbg: plugin: loading Mail::SpamAssassin::Plugin::Hashcash from @INC
[56267] dbg: plugin: loading Mail::SpamAssassin::Plugin::Pyzor from @INC
[56267] dbg: pyzor: local tests only, disabling Pyzor
[56267] dbg: plugin: loading Mail::SpamAssassin::Plugin::Razor2 from @INC
[56267] dbg: razor2: local tests only, skipping Razor
[56267] dbg: plugin: loading Mail::SpamAssassin::Plugin::SpamCop from @INC
[56267] dbg: reporter: local tests only, disabling SpamCop
[56267] dbg: plugin: loading Mail::SpamAssassin::Plugin::AWL from @INC
[56267] dbg: plugin: loadi

Re: sa-update error wrong gpg key...

[Daryl C. W. O'Shea]

Steve Monkhouse wrote:
> Hey guys.. 
> 
> We're seeing the same thing.. although slightly different..

Not really the same thing.  In the OPs case he wasn't using the key for
the channel.  In your case, your (I assume) recently updated version of
GPG refuses to use the non-cross-certified key.

> this error has
> only been happening for a week or so now.. everything's been fine before
> that.. it seems to be with the RSA key generated on 15Jan.. 

http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5775

Daryl

Re: sa-update error wrong gpg key...

[Daryl C. W. O'Shea]

Justin Mason wrote:
> Kevin --  I have bad news. ;)  that's not coming from our channels,
> it's the sare.sa-update.dostech.net channel I'd guess.

Hey, why's that bad news! :)

> Kevin W. Gagel writes:
>> Thanks for looking into this. I've copied and pasted everything below so
>> that you have a complete picture.
>>
>> The command line is (in a cronjob):
>> sa-update --allowplugins --channelfile
>> /etc/mail/spamassassin/sa-update-keys/sa-update-channels &&
>> /etc/init.d/spamassassin restart

>> 70_sare_adult.cf.sare.sa-update.dostech.net
[...]
>>
>> This is what I receive in my inbox in the morning:
>> error: GPG validation failed! 
>> The update downloaded successfully, but it was not signed with a trusted
>> GPG 
>> key. Instead, it was signed with the following keys: 
>>
>> 856AA88A 
>>
>> Perhaps you need to import the channel's GPG key? For example: 
>>
>> wget http://spamassassin.apache.org/updates/GPG.KEY 
>> sa-update --import GPG.KEY 

This is completely expected.  You're missing --gpgkey 856AA88A from your
command line and I'm not sure that you've imported the correct key or
have just re-imported the default channel's key.

Take a look at the instructions I have for these channels at:
http://daryl.dostech.ca/sa-update/sare/sare-sa-update-howto.txt

Daryl

Re: sa-update error wrong gpg key...

[Justin Mason]

Kevin --  I have bad news. ;)  that's not coming from our channels,
it's the sare.sa-update.dostech.net channel I'd guess.

--j.

Kevin W. Gagel writes:
> - Original Message -
> >hi Kevin -- what's the channel and command line?
> 
> Hi Justin,
> 
> Thanks for looking into this. I've copied and pasted everything below so
> that you have a complete picture.
> 
> The command line is (in a cronjob):
> sa-update --allowplugins --channelfile
> /etc/mail/spamassassin/sa-update-keys/sa-update-channels &&
> /etc/init.d/spamassassin restart
> 
> The channels are (all of them are failing, copied from the
> sa-update-channels file):
> 70_sare_adult.cf.sare.sa-update.dostech.net
> 70_sare_bayes_poison_nxm.cf.sare.sa-update.dostech.net
> 70_sare_evilnum0.cf.sare.sa-update.dostech.net
> 70_sare_evilnum1.cf.sare.sa-update.dostech.net
> 70_sare_genlsubj0.cf.sare.sa-update.dostech.net
> 70_sare_genlsubj2.cf.sare.sa-update.dostech.net
> 70_sare_header.cf.sare.sa-update.dostech.net
> 70_sare_html.cf.sare.sa-update.dostech.net
> 70_sare_obfu0.cf.sare.sa-update.dostech.net
> 70_sare_obfu1.cf.sare.sa-update.dostech.net
> 70_sare_oem.cf.sare.sa-update.dostech.net
> 70_sare_random.cf.sare.sa-update.dostech.net
> 70_sare_specific.cf.sare.sa-update.dostech.net
> 70_sare_spoof.cf.sare.sa-update.dostech.net
> 70_sare_stocks.cf.sare.sa-update.dostech.net
> 70_sare_unsub.cf.sare.sa-update.dostech.net
> 70_sare_uri0.cf.sare.sa-update.dostech.net
> 70_sare_whitelist.cf.sare.sa-update.dostech.net
> 70_sare_whitelist_rcvd.cf.sare.sa-update.dostech.net
> 70_sare_whitelist_spf.cf.sare.sa-update.dostech.net
> 72_sare_bml_post25x.cf.sare.sa-update.dostech.net
> 72_sare_redirect_post3.0.0.cf.sare.sa-update.dostech.net
> updates.spamassassin.org
> 
> This is what I receive in my inbox in the morning:
> error: GPG validation failed! 
> The update downloaded successfully, but it was not signed with a trusted
> GPG 
> key. Instead, it was signed with the following keys: 
> 
> 856AA88A 
> 
> Perhaps you need to import the channel's GPG key? For example: 
> 
> wget http://spamassassin.apache.org/updates/GPG.KEY 
> sa-update --import GPG.KEY 
> 
> channel: GPG validation failed, channel failed 
> error: GPG validation failed! 
> The update downloaded successfully, but it was not signed with a trusted
> GPG 
> key. Instead, it was signed with the following keys: 
> 
> 856AA88A 
> 
> Perhaps you need to import the channel's GPG key? For example: 
> 
> wget http://spamassassin.apache.org/updates/GPG.KEY 
> sa-update --import GPG.KEY 
> 
> channel: GPG validation failed, channel failed 
> error: GPG validation failed! 
> The update downloaded successfully, but it was not signed with a trusted
> GPG 
> key. Instead, it was signed with the following keys: 
> 
> 856AA88A 
> 
> Perhaps you need to import the channel's GPG key? For example: 
> 
> wget http://spamassassin.apache.org/updates/GPG.KEY 
> sa-update --import GPG.KEY 
> 
> channel: GPG validation failed, channel failed 
> error: GPG validation failed! 
> The update downloaded successfully, but it was not signed with a trusted
> GPG 
> key. Instead, it was signed with the following keys: 
> 
> 856AA88A 
> 
> Perhaps you need to import the channel's GPG key? For example: 
> 
> wget http://spamassassin.apache.org/updates/GPG.KEY 
> sa-update --import GPG.KEY 
> 
> channel: GPG validation failed, channel failed 
> error: GPG validation failed! 
> The update downloaded successfully, but it was not signed with a trusted
> GPG 
> key. Instead, it was signed with the following keys: 
> 
> 856AA88A 
> 
> Perhaps you need to import the channel's GPG key? For example: 
> 
> wget http://spamassassin.apache.org/updates/GPG.KEY 
> sa-update --import GPG.KEY 
> 
> channel: GPG validation failed, channel failed 
> error: GPG validation failed! 
> The update downloaded successfully, but it was not signed with a trusted
> GPG 
> key. Instead, it was signed with the following keys: 
> 
> 856AA88A 
> 
> Perhaps you need to import the channel's GPG key? For example: 
> 
> wget http://spamassassin.apache.org/updates/GPG.KEY 
> sa-update --import GPG.KEY 
> 
> channel: GPG validation failed, channel failed 
> error: GPG validation failed! 
> The update downloaded successfully, but it was not signed with a trusted
> GPG 
> key. Instead, it was signed with the following keys: 
> 
> 856AA88A 
> 
> Perhaps you need to import the channel's GPG key? For example: 
> 
> wget http://spamassassin.apache.org/updates/GPG.KEY 
> sa-update --import GPG.KEY 
> 
> channel: GPG validation failed, channel failed 
> error: GPG validation failed! 
> The update downloaded successfully, but it was not signed with a trusted
> GPG 
> key. Instead, it was signed with the following keys: 
> 
> 856AA88A 
> 
> Perhaps you need to import the channel's GPG key? For example: 
> 
> wget http://spamassassin.apache.org/updates/GPG.KEY 
> sa-update --import GPG.KEY 
> 
> channel: GPG validation failed, channel failed 
> error: GPG validation failed!

Re: Antwort: Re: sa-update error

[Philipp Snizek]

try this:

perl -MCPAN -e 'notest force install Archive::Tar'

no warranty that this will not cause any problems with Archive::Tar at
some point later. I remember your spamassassin --lint -D saying that it
found Archive::Tar, so I guess there is an install of this module on your
box. However this command should install Archive::Tar on your box by
force.

Nevertheless I think the better way is finding out why it fails to install
and resolve that.





> It won't install:
>
> Test Summary Report
> ---
> t/02_methods.t(Wstat: 65280 Tests: 252 Failed: 65)
>   Failed test number(s):  18-25, 71-72, 74-75, 77-80, 82-83, 92-97
> 105, 110-117, 123-125, 151-154, 162, 167-168
> 186-189, 195-197, 214-217, 225, 230-231
> 240-243, 249-252
>   Non-zero exit status: 255
> t/04_resolved_issues.t (Wstat: 65280 Tests: 7 Failed: 2)
>   Failed test number(s):  6-7
>   Non-zero exit status: 255
> Files=5, Tests=482,  1 wallclock secs ( 0.07 usr  0.00 sys +  0.54 cusr
> 0.05 csys =  0.66 CPU)
> Result: FAIL
> Failed 2/5 test programs. 67/482 subtests failed.
> make: *** [test_dynamic] Fehler 11
>   /usr/bin/make test -- NOT OK
> Running make install
>   make test had returned bad status, won't install without force
>
>
>
>
>
> "Philipp Snizek" <[EMAIL PROTECTED]>
> 06.12.2007 14:07
>
> An
> [EMAIL PROTECTED]
> Kopie
> users@spamassassin.apache.org
> Thema
> Re: sa-update error
>
>
>
>
>
>
>> Hi
>>
>> can anyone help me with this?
>> I think its the archive::tar which makes problems,
>> so i installed a newer version, but the error remains...
>>
>> [23086] dbg: channel: populating temp content file
>> [23086] dbg: channel: file verification passed, testing update
>> [23086] dbg: channel: extracting archive
>> No data could be read from file at /usr/bin/sa-update line 961
>> fatal: couldn't create Archive::Tar object!
>
> what does
>
> perl -MCPAN -e 'install Archive::Tar'
>
> say?
>
> - Philipp
>
>
>
>
>

Antwort: Re: sa-update error

[Juergen . Boehm]

It won't install:

Test Summary Report
---
t/02_methods.t(Wstat: 65280 Tests: 252 Failed: 65)
  Failed test number(s):  18-25, 71-72, 74-75, 77-80, 82-83, 92-97
105, 110-117, 123-125, 151-154, 162, 167-168
186-189, 195-197, 214-217, 225, 230-231
240-243, 249-252
  Non-zero exit status: 255
t/04_resolved_issues.t (Wstat: 65280 Tests: 7 Failed: 2)
  Failed test number(s):  6-7
  Non-zero exit status: 255
Files=5, Tests=482,  1 wallclock secs ( 0.07 usr  0.00 sys +  0.54 cusr 
0.05 csys =  0.66 CPU)
Result: FAIL
Failed 2/5 test programs. 67/482 subtests failed.
make: *** [test_dynamic] Fehler 11
  /usr/bin/make test -- NOT OK
Running make install
  make test had returned bad status, won't install without force





"Philipp Snizek" <[EMAIL PROTECTED]> 
06.12.2007 14:07

An
[EMAIL PROTECTED]
Kopie
users@spamassassin.apache.org
Thema
Re: sa-update error






> Hi
>
> can anyone help me with this?
> I think its the archive::tar which makes problems,
> so i installed a newer version, but the error remains...
>
> [23086] dbg: channel: populating temp content file
> [23086] dbg: channel: file verification passed, testing update
> [23086] dbg: channel: extracting archive
> No data could be read from file at /usr/bin/sa-update line 961
> fatal: couldn't create Archive::Tar object!

what does

perl -MCPAN -e 'install Archive::Tar'

say?

- Philipp

Re: sa-update error

[Philipp Snizek]

> Hi
>
> can anyone help me with this?
> I think its the archive::tar which makes problems,
> so i installed a newer version, but the error remains...
>
> [23086] dbg: channel: populating temp content file
> [23086] dbg: channel: file verification passed, testing update
> [23086] dbg: channel: extracting archive
> No data could be read from file at /usr/bin/sa-update line 961
> fatal: couldn't create Archive::Tar object!

what does

perl -MCPAN -e 'install Archive::Tar'

say?

- Philipp

Re: sa-update error

[Philipp Snizek]

Hi

> Thx so far. Yes thats it. Its our DNS on the Router. In all other cases it
> works fine but it don't like 3.2.3.updates.spamassassin.org.
> Can i somehow tell sa-update to use another (global) DNS Server?

Yes, you can. The first choice probably would be the DNS servers of your ISP.
However, you could also run a DNS cache server on your antispam box or on
some other linux/unix/windows based machine. This would give you a
performance advantage.

Philipp

> PS.: I've got the newest version of the updates because i manually built
> the directories and copied the files from my private machine .-)
>
>
>
>
> Jürgen Böhm <[EMAIL PROTECTED]>
> 04.12.2007 06:26
>
> An
> [EMAIL PROTECTED]
> Kopie
>
> Thema
> [Fwd: Re: sa-update error]
>
>
>
>
>
>
>
>
>
> - Nachricht von "Daryl C. W. O'Shea" <[EMAIL PROTECTED]> auf
> Mon, 03 Dec 2007 11:14:32 -0500 -
> An:
> [EMAIL PROTECTED]
> Kopie:
> users@spamassassin.apache.org
> Thema:
> Re: sa-update error
>
> [EMAIL PROTECTED] wrote:
>
>> i get following error when i run sa-update.
>> uery failed: 3.2.3.updates.spamassassin.org => answer section incomplete
>> can anybody help me with this?
>> here is the whole dump from sa-update:
>
> I'm getting the proper response from all five of our name servers.
>
> Try the query manually to see if you can spot a problem.
>
> dig txt 3.2.3.updates.spamassassin.org
>
> Be sure to run the query against the first name server listed in your
> /etc/resolv.conf file since it's the only one that will be uses (maybe
> it's down or having problems).
>
>> [31625] dbg: channel: metadata version = 590061
>
> Note that 590061 is the current version so you had to have successfully
> updated the channel in the past.
>
> Daryl
>
>
>
>
> - Nachricht von "Daryl C. W. O'Shea" <[EMAIL PROTECTED]> auf
> Mon, 03 Dec 2007 11:14:32 -0500 -
> An:
> [EMAIL PROTECTED]
> Kopie:
> users@spamassassin.apache.org
> Thema:
> Re: sa-update error
>
> [EMAIL PROTECTED] wrote:
>
>> i get following error when i run sa-update.
>> uery failed: 3.2.3.updates.spamassassin.org => answer section incomplete
>> can anybody help me with this?
>> here is the whole dump from sa-update:
>
> I'm getting the proper response from all five of our name servers.
>
> Try the query manually to see if you can spot a problem.
>
> dig txt 3.2.3.updates.spamassassin.org
>
> Be sure to run the query against the first name server listed in your
> /etc/resolv.conf file since it's the only one that will be uses (maybe
> it's down or having problems).
>
>> [31625] dbg: channel: metadata version = 590061
>
> Note that 590061 is the current version so you had to have successfully
> updated the channel in the past.
>
> Daryl
>
>
>
>

Re: sa-update error

[Juergen . Boehm]

Thx so far. Yes thats it. Its our DNS on the Router. In all other cases it 
works fine but it don't like 3.2.3.updates.spamassassin.org.
Can i somehow tell sa-update to use another (global) DNS Server?
PS.: I've got the newest version of the updates because i manually built 
the directories and copied the files from my private machine .-)




Jürgen Böhm <[EMAIL PROTECTED]> 
04.12.2007 06:26

An
[EMAIL PROTECTED]
Kopie

Thema
[Fwd: Re: sa-update error]









- Nachricht von "Daryl C. W. O'Shea" <[EMAIL PROTECTED]> auf 
Mon, 03 Dec 2007 11:14:32 -0500 -
An:
[EMAIL PROTECTED]
Kopie:
users@spamassassin.apache.org
Thema:
Re: sa-update error

[EMAIL PROTECTED] wrote:

> i get following error when i run sa-update.
> uery failed: 3.2.3.updates.spamassassin.org => answer section incomplete
> can anybody help me with this?
> here is the whole dump from sa-update:

I'm getting the proper response from all five of our name servers.

Try the query manually to see if you can spot a problem.

dig txt 3.2.3.updates.spamassassin.org

Be sure to run the query against the first name server listed in your 
/etc/resolv.conf file since it's the only one that will be uses (maybe 
it's down or having problems).

> [31625] dbg: channel: metadata version = 590061

Note that 590061 is the current version so you had to have successfully 
updated the channel in the past.

Daryl




- Nachricht von "Daryl C. W. O'Shea" <[EMAIL PROTECTED]> auf 
Mon, 03 Dec 2007 11:14:32 -0500 -
An:
[EMAIL PROTECTED]
Kopie:
users@spamassassin.apache.org
Thema:
Re: sa-update error

[EMAIL PROTECTED] wrote:

> i get following error when i run sa-update.
> uery failed: 3.2.3.updates.spamassassin.org => answer section incomplete
> can anybody help me with this?
> here is the whole dump from sa-update:

I'm getting the proper response from all five of our name servers.

Try the query manually to see if you can spot a problem.

dig txt 3.2.3.updates.spamassassin.org

Be sure to run the query against the first name server listed in your 
/etc/resolv.conf file since it's the only one that will be uses (maybe 
it's down or having problems).

> [31625] dbg: channel: metadata version = 590061

Note that 590061 is the current version so you had to have successfully 
updated the channel in the past.

Daryl

Re: sa-update error

[Daryl C. W. O'Shea]

[EMAIL PROTECTED] wrote:


i get following error when i run sa-update.
uery failed: 3.2.3.updates.spamassassin.org => answer section incomplete
can anybody help me with this?
here is the whole dump from sa-update:


I'm getting the proper response from all five of our name servers.

Try the query manually to see if you can spot a problem.

dig txt 3.2.3.updates.spamassassin.org

Be sure to run the query against the first name server listed in your 
/etc/resolv.conf file since it's the only one that will be uses (maybe 
it's down or having problems).



[31625] dbg: channel: metadata version = 590061


Note that 590061 is the current version so you had to have successfully 
updated the channel in the past.


Daryl

Re: sa-update error

[Matt Kettler]

Sg wrote:
> Hi
>
> I am using SA 3.1.7. I want to update it.
>
> I tried this command
>
> sa-update --nogpg --channel updates.spamassassin.org
>  --channel saupdates.openprotect.com
> 
>
> But i got this error  ""Argument "1.26_01" isnt numeric in subroutine
> entry at sa-update line 91""
It appears your Archive::Tar version is 1.26_01, which is an unfortunate
mis-use of a non-number for the version of a a perl module.

Try upgrading your Archive::Tar to a version which isn't mis-labeled
like that. As a bonus 1.29 and higher recover more gracefully from
garbage input than 1.26_01.

Re: sa-update error

[Zbigniew Szalbot]

Hi Daryl,

On Tue, 24 Jul 2007 02:56:02 -0400, "Daryl C. W. O'Shea"
<[EMAIL PROTECTED]> wrote:
> Zbigniew Szalbot wrote:
>> Hello,
>>
>> I'd be glad for your suggestions re sa-update error.
>>
>> $ sa-update
>> can't resolve "l27.0.0.1" to address at
> 
> L27.0.0.1 isn't quite the same as 127.0.0.1.

Well,  I'm red all over my face. Wonder how my box worked with such an
interesting "local" resolve address.

Warm regards, 

-- 
Zbigniew Szalbot

Re: sa-update error

[Daryl C. W. O'Shea]

Zbigniew Szalbot wrote:

Hello,

I'd be glad for your suggestions re sa-update error.

$ sa-update
can't resolve "l27.0.0.1" to address at


L27.0.0.1 isn't quite the same as 127.0.0.1.

Daryl



/usr/local/lib/perl5/site_perl/5.8.8/mach/Net/DNS/Resolver/Base.pm line
751.

I think the issue started when I switched from my ISP DNS server to using
my own caching name server at localhost. All things work properly but I see
this error when the system boots and when I issue sa-update.

Many thanks in advance for pointing me in the right direction!

Re: sa-update error:

[diptanjan]

Thanks Daryl

You were 100% right.. I just missed that section.

I tried to Update those section issuing the commands from CPAN... 

But the problem was the Mirror CPAN was using was not accessable so it
wasn't downloading the *.gz files

So I had to download those .gz files manually from different mirroe site and
than run the CPAN command... 

I am little surprized why CPAN is using a mirror site thats not working? Or
is there something wrong in myside..

Anyway all credit goes to you... If you not have mentioned the skipped
section in INSTALL.doc I would never have spotted out the sa-update error.

Thanks again

Diptanjan

###

Perhaps you haven't installed Archive::Tar (or IO::Zlib) as noted in the 
INSTALL doc.

Daryl

-- 
View this message in context: 
http://www.nabble.com/sa-update-error%3A-tf3882174.html#a11005804
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.

Re: sa-update error:

[Daryl C. W. O'Shea]

diptanjan wrote:

Hi Friends,

I have installed spamassassin few days back. using CPAN.
I gave the following command 


# perl -MCPAN -e shell[as root]
cpan>o conf prerequisites_policy ask
cpan>install Mail::SpamAssassin
cpan>quit

spamassassin -V gives me 


SpamAssassin version 3.2.0
running on Perl version 5.8.8

I have tested my isatallation by giving command

# /usr/bin/spamassassin -t <
/root/.cpan/build/Mail-SpamAssassin-3.2.0/sample-spam.txt

But now when I am trying to update my Spamassassin by following command its
give me error.

# sa-update
Can't locate Archive/Tar.pm in @INC (@INC contains:
/usr/lib/perl5/site_perl/5.8.8/i586-linux-thread-multi
/usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/5.8.8/i586-linux-thread-multi
/usr/lib/perl5/5.8.8 /usr/lib/perl5/site_perl
/usr/lib/perl5/vendor_perl/5.8.8/i586-linux-thread-multi
/usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl) at
/usr/bin/sa-update line 81.
BEGIN failed--compilation aborted at /usr/bin/sa-update line 81.

Can someone help me what went wrong? ans how to solve this problem.


Perhaps you haven't installed Archive::Tar (or IO::Zlib) as noted in the 
INSTALL doc.


Daryl

Re: sa-update error

[Daryl C. W. O'Shea]

Jim Knuth wrote:

Heute (13.04.2007/02:56 Uhr) schrieb Daryl C. W. O'Shea,


Jim Knuth wrote:

Heute (13.04.2007/02:29 Uhr) schrieb Daryl C. W. O'Shea,


Jim Knuth wrote:

Hello spamassassin-users,

Since the Upgrade on Debian Etch I receive this mistake

# sa-update
config: failed to parse line, skipping, in
"/tmp/.spamassassin4363HNOBtxtmp/25_asn.cf": asn_lookup
asn.routeviews.org _ASN_ _ASNCIDR_
channel: lint check of update failed, channel failed

What is wrong?

It appears that you're attempting to use a current 3.2 update with an
old copy of the 3.2 code (ie RC1 or an svn checkout more than about a
day old).
Daryl


It`s

SpamAssassin version 3.2.0-rc1
  running on Perl version 5.8.4

What can I do?



Not use the (sa-)update or update the code (via svn or RC2 that was made
available today).


*lol* ok, thank you. I read this (RC2) here?


Ummm, oops... it wasn't actually announced yet.  You may want to just 
disable the ASN plugin (that's the only thing causing your problem) for 
now and wait a day or two for the RC announcement.


Daryl

Re: sa-update error

[Jim Knuth]

Heute (13.04.2007/02:56 Uhr) schrieb Daryl C. W. O'Shea,

> Jim Knuth wrote:
>> Heute (13.04.2007/02:29 Uhr) schrieb Daryl C. W. O'Shea,
>> 
>>> Jim Knuth wrote:
 Hello spamassassin-users,

 Since the Upgrade on Debian Etch I receive this mistake

 # sa-update
 config: failed to parse line, skipping, in
 "/tmp/.spamassassin4363HNOBtxtmp/25_asn.cf": asn_lookup
 asn.routeviews.org _ASN_ _ASNCIDR_
 channel: lint check of update failed, channel failed

 What is wrong?
>> 
>>> It appears that you're attempting to use a current 3.2 update with an
>>> old copy of the 3.2 code (ie RC1 or an svn checkout more than about a
>>> day old).
>> 
>>> Daryl
>> 
>> 
>> It`s
>> 
>> SpamAssassin version 3.2.0-rc1
>>   running on Perl version 5.8.4
>> 
>> What can I do?

> Not use the (sa-)update or update the code (via svn or RC2 that was made
> available today).

*lol* ok, thank you. I read this (RC2) here?

> Daryl

-- 
Viele Gruesse, Kind regards,
 Jim Knuth
 [EMAIL PROTECTED]
 ICQ #277289867
--
Zufalls-Zitat
--
Das niedrig gewachsene, schmalschultrige, breithüftige und 
kurzbeinige Geschlecht das schöne zu nennen, dies konnte 
nur der vom Geschlechtstrieb umnebelte männliche Intellekt 
fertigbringen. (Arthur Schoppenhauer)
--
Der Text hat nichts mit dem Empfaenger der Mail zu tun
--
Virus free. Checked by NOD32 Version 2185 Build 9554  12.04.2007

Re: sa-update error

[Daryl C. W. O'Shea]

Jim Knuth wrote:

Heute (13.04.2007/02:29 Uhr) schrieb Daryl C. W. O'Shea,


Jim Knuth wrote:

Hello spamassassin-users,

Since the Upgrade on Debian Etch I receive this mistake

# sa-update
config: failed to parse line, skipping, in
"/tmp/.spamassassin4363HNOBtxtmp/25_asn.cf": asn_lookup
asn.routeviews.org _ASN_ _ASNCIDR_
channel: lint check of update failed, channel failed

What is wrong?



It appears that you're attempting to use a current 3.2 update with an
old copy of the 3.2 code (ie RC1 or an svn checkout more than about a
day old).



Daryl



It`s

SpamAssassin version 3.2.0-rc1
  running on Perl version 5.8.4

What can I do?


Not use the (sa-)update or update the code (via svn or RC2 that was made 
available today).


Daryl

Re: sa-update error

[Jim Knuth]

Heute (13.04.2007/02:29 Uhr) schrieb Daryl C. W. O'Shea,

> Jim Knuth wrote:
>> Hello spamassassin-users,
>> 
>> Since the Upgrade on Debian Etch I receive this mistake
>> 
>> # sa-update
>> config: failed to parse line, skipping, in
>> "/tmp/.spamassassin4363HNOBtxtmp/25_asn.cf": asn_lookup
>> asn.routeviews.org _ASN_ _ASNCIDR_
>> channel: lint check of update failed, channel failed
>> 
>> What is wrong?

> It appears that you're attempting to use a current 3.2 update with an
> old copy of the 3.2 code (ie RC1 or an svn checkout more than about a
> day old).

> Daryl


It`s

SpamAssassin version 3.2.0-rc1
  running on Perl version 5.8.4

What can I do?


-- 
Viele Gruesse, Kind regards,
 Jim Knuth
 [EMAIL PROTECTED]
 ICQ #277289867
--
Zufalls-Zitat
--
Krisen meistert man am besten, indem man ihnen zuvorkommt. 
(Walt Whitman Rostow, am. Wirtschaftswissenschaftler)
--
Der Text hat nichts mit dem Empfaenger der Mail zu tun
--
Virus free. Checked by NOD32 Version 2185 Build 9554  12.04.2007

Re: sa-update error

[Daryl C. W. O'Shea]

Jim Knuth wrote:

Hello spamassassin-users,

Since the Upgrade on Debian Etch I receive this mistake

# sa-update
config: failed to parse line, skipping, in
"/tmp/.spamassassin4363HNOBtxtmp/25_asn.cf": asn_lookup
asn.routeviews.org _ASN_ _ASNCIDR_
channel: lint check of update failed, channel failed

What is wrong?


It appears that you're attempting to use a current 3.2 update with an 
old copy of the 3.2 code (ie RC1 or an svn checkout more than about a 
day old).


Daryl

Re: SA-Update error messages

[John Andersen]

On Thursday 26 October 2006 09:10, Daryl C. W. O'Shea wrote:
> John Andersen wrote:
> > Everytime my SA-Update runs the output from the cron job shows these
> > lines:
>
> Only from cron?

Nope, not only from cron, also when manually run.

Other machines with later versions of Perl do not do
this so I'm thinking its something about 5.8.0
that it does not like.

-- 
_
John Andersen

Re: SA-Update error messages

[Daryl C. W. O'Shea]

John Andersen wrote:

Everytime my SA-Update runs the output from the cron job shows these lines:


Only from cron?



Use of uninitialized value in eval "string" at /usr/bin/sa-update line 91.
Use of uninitialized value in eval "string" at /usr/bin/sa-update line 91.
Use of uninitialized value in eval "string" at /usr/bin/sa-update line 91.
Use of uninitialized value in eval "string" at /usr/bin/sa-update line 92.
Use of uninitialized value in eval "string" at /usr/bin/sa-update line 92.
Use of uninitialized value in eval "string" at /usr/bin/sa-update line 92.
Use of uninitialized value in eval "string" at /usr/bin/sa-update line 93.
Use of uninitialized value in eval "string" at /usr/bin/sa-update line 93.
Use of uninitialized value in eval "string" at /usr/bin/sa-update line 93.
Use of uninitialized value in eval "string" at /usr/bin/sa-update line 94.
Use of uninitialized value in eval "string" at /usr/bin/sa-update line 94.
Use of uninitialized value in eval "string" at /usr/bin/sa-update line 94.
Use of uninitialized value in eval "string" at /usr/bin/sa-update line 95.
Use of uninitialized value in eval "string" at /usr/bin/sa-update line 95.
Use of uninitialized value in eval "string" at /usr/bin/sa-update line 95.


Weird that there's exactly three for each.


Daryl

Re: SA-Update error messages

[Theo Van Dinter]

On Tue, Oct 24, 2006 at 08:26:09PM -0800, John Andersen wrote:
> > > Use of uninitialized value in eval "string" at /usr/bin/sa-update line 91.
> > > eval { use Net::DNS; };
> > Just curious, what version of perl are you using?
> 
> 5.8.0

Interesting.  I have no idea what would cause perl to generate that warning,
since there's clearly no uninitialized values in the eval string.

-- 
Randomly Selected Tagline:
How do I type "for i in *.dvi do xdvi i done" in a GUI?
 (Discussion in comp.os.linux.misc on the intuitiveness of interfaces.)


pgpsq3nGRlQua.pgp
Description: PGP signature

Re: SA-Update error messages

[John Andersen]

continuing with the pop-posting 

They are installed Simone. 

[1107] dbg: diag: module installed: Digest::SHA1, version 2.11
[1107] dbg: diag: module installed: Net::DNS, version 0.58
[1107] dbg: diag: module installed: MIME::Base64, version 3.07
[1107] dbg: diag: module installed: HTML::Parser, version 3.55
[1107] dbg: diag: module installed: DB_File, version 1.804
[1107] dbg: diag: module installed: Net::SMTP, version 2.29
[1107] dbg: diag: module installed: Mail::SPF::Query, version 1.999001
[1107] dbg: diag: module installed: IP::Country::Fast, version 604.001
[1107] dbg: diag: module installed: Razor2::Client::Agent, version 2.82
[1107] dbg: diag: module not installed: Net::Ident ('require' failed)
[1107] dbg: diag: module not installed: IO::Socket::INET6 ('require' failed)
[1107] dbg: diag: module not installed: IO::Socket::SSL ('require' failed)
[1107] dbg: diag: module installed: Time::HiRes, version 1.66
[1107] dbg: diag: module installed: DBI, version 1.51
[1107] dbg: diag: module installed: Getopt::Long, version 2.35
[1107] dbg: diag: module installed: LWP::UserAgent, version 2.033
[1107] dbg: diag: module installed: HTTP::Date, version 1.47
[1107] dbg: diag: module installed: Archive::Tar, version 1.29
[1107] dbg: diag: module installed: IO::Zlib, version 1.04


On Tuesday 24 October 2006 01:07, Simone ABATE wrote:
> You have to install these package via CPAN.
> 
> John Andersen ha scritto:
> > Everytime my SA-Update runs the output from the cron job shows these lines:
> >
> >
> > Use of uninitialized value in eval "string" at /usr/bin/sa-update line 91.
> > Use of uninitialized value in eval "string" at /usr/bin/sa-update line 91.



-- 
_
John Andersen


pgppqapnYQFBU.pgp
Description: PGP signature

Re: SA-Update error messages

[John Andersen]

On Tuesday 24 October 2006 08:56, Theo Van Dinter wrote:
> On Sun, Oct 22, 2006 at 01:19:37AM -0800, John Andersen wrote:
> > Use of uninitialized value in eval "string" at /usr/bin/sa-update line 91.
> [...]
> > Use of uninitialized value in eval "string" at /usr/bin/sa-update line 95.
> > 
> > eval { use Net::DNS; };
> [...]
> > eval { use IO::Zlib 1.04; };
> 
> Just curious, what version of perl are you using?
> 

5.8.0

I probably should have mentioned that these messages just started
showing up with 3.1.7 but the two machines I'm seeing it on 
have been running successive versions of SA since 2.4.something.

All the modules it complains about are installed according to 
--lint --debug

This is perl, v5.8.0 built for i586-linux-thread-multi

[1107] dbg: diag: module installed: Digest::SHA1, version 2.11
[1107] dbg: diag: module installed: Net::DNS, version 0.58
[1107] dbg: diag: module installed: MIME::Base64, version 3.07
[1107] dbg: diag: module installed: HTML::Parser, version 3.55
[1107] dbg: diag: module installed: DB_File, version 1.804
[1107] dbg: diag: module installed: Net::SMTP, version 2.29
[1107] dbg: diag: module installed: Mail::SPF::Query, version 1.999001
[1107] dbg: diag: module installed: IP::Country::Fast, version 604.001
[1107] dbg: diag: module installed: Razor2::Client::Agent, version 2.82
[1107] dbg: diag: module not installed: Net::Ident ('require' failed)
[1107] dbg: diag: module not installed: IO::Socket::INET6 ('require' failed)
[1107] dbg: diag: module not installed: IO::Socket::SSL ('require' failed)
[1107] dbg: diag: module installed: Time::HiRes, version 1.66
[1107] dbg: diag: module installed: DBI, version 1.51
[1107] dbg: diag: module installed: Getopt::Long, version 2.35
[1107] dbg: diag: module installed: LWP::UserAgent, version 2.033
[1107] dbg: diag: module installed: HTTP::Date, version 1.47
[1107] dbg: diag: module installed: Archive::Tar, version 1.29
[1107] dbg: diag: module installed: IO::Zlib, version 1.04




-- 
_
John Andersen


pgpOG4cContOt.pgp
Description: PGP signature

Re: SA-Update error messages

[Theo Van Dinter]

On Sun, Oct 22, 2006 at 01:19:37AM -0800, John Andersen wrote:
> Use of uninitialized value in eval "string" at /usr/bin/sa-update line 91.
[...]
> Use of uninitialized value in eval "string" at /usr/bin/sa-update line 95.
> 
> eval { use Net::DNS; };
[...]
> eval { use IO::Zlib 1.04; };

Just curious, what version of perl are you using?

-- 
Randomly Selected Tagline:
"With a name like 'Theo', shouldn't you be running OpenBSD?  "
 - Unknown person at Collective Technologies


pgp5MasOQL9ae.pgp
Description: PGP signature

Re: SA-Update error messages

[Simone ABATE]

You have to install these package via CPAN.

John Andersen ha scritto:

Everytime my SA-Update runs the output from the cron job shows these lines:


Use of uninitialized value in eval "string" at /usr/bin/sa-update line 91.
Use of uninitialized value in eval "string" at /usr/bin/sa-update line 91.
Use of uninitialized value in eval "string" at /usr/bin/sa-update line 91.
Use of uninitialized value in eval "string" at /usr/bin/sa-update line 92.
Use of uninitialized value in eval "string" at /usr/bin/sa-update line 92.
Use of uninitialized value in eval "string" at /usr/bin/sa-update line 92.
Use of uninitialized value in eval "string" at /usr/bin/sa-update line 93.
Use of uninitialized value in eval "string" at /usr/bin/sa-update line 93.
Use of uninitialized value in eval "string" at /usr/bin/sa-update line 93.
Use of uninitialized value in eval "string" at /usr/bin/sa-update line 94.
Use of uninitialized value in eval "string" at /usr/bin/sa-update line 94.
Use of uninitialized value in eval "string" at /usr/bin/sa-update line 94.
Use of uninitialized value in eval "string" at /usr/bin/sa-update line 95.
Use of uninitialized value in eval "string" at /usr/bin/sa-update line 95.
Use of uninitialized value in eval "string" at /usr/bin/sa-update line 95.

Which refer to these lines in sa-update:

eval { use Net::DNS; };
eval { use LWP::UserAgent; };
eval { use HTTP::Date qw(time2str); };
eval { use Archive::Tar 1.23; };
eval { use IO::Zlib 1.04; };


Whats up with that?


  



--
Informativa ai sensi dell' art. 13 Dlgs 196/2003.
I dati personali forniti in occasione di relazione a mezzo di scambio 
elettronico di messaggi, sono soggetti a trattamento con strumento elettronico. 
Le finalita' del trattamento sono solo quelle relative all'oggetto del 
messaggio o al contesto della relazione instaurata. Il Titolare del trattamento 
e' la Software Design S.p.A. con sede in via Domitiana 105/G, Pozzuoli (NA). Il 
Responsabile del trattamento e' il destinatario del messaggio.
E' possibile esercitare il diritto all'accesso dei dati personali per mezzo di 
posta elettronica o telefono al numero 081.8673211.
Nel caso in cui aveste ricevuto questa e-mail per errore, vogliate cortesemente 
avvertire tempestivamente il mittente e distruggere il presente messaggio. 
Grazie

begin:vcard
fn:Simone  ABATE
n:ABATE;Simone 
org:Software Design S.P.A.;Information Tecnology
email;internet:[EMAIL PROTECTED]
title:System Manager
tel;work:+390817896828
tel;fax:+390817896344
x-mozilla-html:TRUE
version:2.1
end:vcard

Re: sa-update error

[Chris]

On Friday 04 August 2006 9:33 am, Theo Van Dinter wrote:

> The problem is, yet again, of assumption.  The code assumes that if the
> update directory exists, that certain channel files will be in there
> because it creates them (aka: channel.cf and channel.pre).  So when an
> update occurs, the code dutifully removes those files before installing
> the update where it'll recreate them for the new files.  Unfortunately,
> there's a flaw in the assumption wherein the channel files only _may_
> exist -- if sa-update doesn't have anything to put into the file,
> it doesn't bother writing it out.  So in the end we get this warning
> because the attempt to remove the non-existant file failed.
>
> I had also forgotten that the "don't create if empty" bit was in the
> code, hence my "Crap!" when I was reading through and found it. :|
>
> > channel: attempt to rm channel pre file failed, attempting to continue
> > anyway at /usr/bin/sa-update line 691.
> > /bin/sh: line 1: service: command not found
> >
> > Or is that also part of the bug?
>
> The "service: command not found" line?  No, that's something you're
> calling outside of sa-update.  My guess is you're trying something like:
>
> sa-update && service spamassassin restart
>
> which assumes you're on an OS with the "service" command and that it's
> in your path (amongst other things).

Yes, I'm running it as a cronjob with sa-update && service spamassassin 
restart. It worked the first time it ran and it must have worked today as 
the "updates.spamassassinorg.cf file is time stamped today at 6:11am as 
well as all the files in /var/lib/spamassassin/3.001004. Thats assuming 
there was an update since yesterday, however, looking at my syslog it 
appears as though spamassassin did not restart.

-- 
Chris
17:37:47 up 4 days, 23:06, 1 user, load average: 0.22, 0.20, 0.19
~~
Any sufficiently advanced technology is indistinguishable from a rigged 
demo.
~~


pgpMVCnKs1jHA.pgp
Description: PGP signature

Re: sa-update error

[Theo Van Dinter]

On Fri, Aug 04, 2006 at 06:25:04AM -0500, Chris wrote:
> > Aha!  I see the issue!  Crap!
> 
> Theo, why would you get this if the /var/lib/spamassassin/3.001004 'does' 
> exist? 

The problem is, yet again, of assumption.  The code assumes that if the
update directory exists, that certain channel files will be in there
because it creates them (aka: channel.cf and channel.pre).  So when an
update occurs, the code dutifully removes those files before installing
the update where it'll recreate them for the new files.  Unfortunately,
there's a flaw in the assumption wherein the channel files only _may_
exist -- if sa-update doesn't have anything to put into the file,
it doesn't bother writing it out.  So in the end we get this warning
because the attempt to remove the non-existant file failed.

I had also forgotten that the "don't create if empty" bit was in the code,
hence my "Crap!" when I was reading through and found it. :|

> channel: attempt to rm channel pre file failed, attempting to continue 
> anyway at /usr/bin/sa-update line 691.
> /bin/sh: line 1: service: command not found
> 
> Or is that also part of the bug?

The "service: command not found" line?  No, that's something you're calling
outside of sa-update.  My guess is you're trying something like:

sa-update && service spamassassin restart

which assumes you're on an OS with the "service" command and that it's
in your path (amongst other things).

-- 
Randomly Generated Tagline:
"Depends on how you define 'always'.  :-)"   - Larry Wall


pgpz5e3lJ7G5X.pgp
Description: PGP signature

Re: sa-update error

[Chris]

On Thursday 03 August 2006 10:17 am, Theo Van Dinter wrote:
> On Thu, Aug 03, 2006 at 04:08:16PM +0100, Nigel Frankcom wrote:
> > >> channel: attempt to rm channel pre file failed, attempting to
> > >> continue anyway at /usr/bin/sa-update line 694
> > >> --lint -D shows no errors, just wondering if I should be concerned?
> >
> > I don't use updatedir - just straight sa-update. I'll add detail to
> > the ticket
>
> Aha!  I see the issue!  Crap!
>
> Yeah, please open the ticket and I'll get a patch written up.  Dang it.

Theo, why would you get this if the /var/lib/spamassassin/3.001004 'does' 
exist? 

channel: attempt to rm channel pre file failed, attempting to continue 
anyway at /usr/bin/sa-update line 691.
/bin/sh: line 1: service: command not found

Or is that also part of the bug?

-- 
Chris
06:21:46 up 4 days, 11:50, 1 user, load average: 0.39, 0.38, 0.20



pgpyQM2qitlQO.pgp
Description: PGP signature

Re: sa-update error

[Theo Van Dinter]

On Thu, Aug 03, 2006 at 04:08:16PM +0100, Nigel Frankcom wrote:
> >> channel: attempt to rm channel pre file failed, attempting to continue
> >> anyway at /usr/bin/sa-update line 694
> >> --lint -D shows no errors, just wondering if I should be concerned?
> 
> I don't use updatedir - just straight sa-update. I'll add detail to
> the ticket

Aha!  I see the issue!  Crap!

Yeah, please open the ticket and I'll get a patch written up.  Dang it.

-- 
Randomly Generated Tagline:
"It timed me out... I hate Windows." - Prof. Farr


pgptwSfJwZZVM.pgp
Description: PGP signature

Re: sa-update error

[Nigel Frankcom]

On Thu, 3 Aug 2006 10:06:31 -0400, Theo Van Dinter
<[EMAIL PROTECTED]> wrote:

>On Thu, Aug 03, 2006 at 10:19:44AM +0100, Nigel Frankcom wrote:
>> channel: attempt to rm channel pre file failed, attempting to continue
>> anyway at /usr/bin/sa-update line 694
>> --lint -D shows no errors, just wondering if I should be concerned?
>
>Hrm.  Well, it's one of those "features" as opposed to a bug
>(though I'd appreciate it if you could open a BZ ticket about it:
>http://issues.apache.org/SpamAssassin/).  In short, there's no problem --
>it'll happen the first time you run sa-update in 3.1.4 and you're using
>updatedir to aim at a non-standard (and already existing) location.
>
>The code assumes that certain files should exist if the update directory
>already exists, so when it tries to delete the files and they're not
>there, it shows a warning -- but if this is the first time sa-update
>from 3.1.4 is run, the channel pre file won't exist.

I don't use updatedir - just straight sa-update. I'll add detail to
the ticket

Kind regards

Nigel

Re: sa-update error

[Theo Van Dinter]

On Thu, Aug 03, 2006 at 10:19:44AM +0100, Nigel Frankcom wrote:
> channel: attempt to rm channel pre file failed, attempting to continue
> anyway at /usr/bin/sa-update line 694
> --lint -D shows no errors, just wondering if I should be concerned?

Hrm.  Well, it's one of those "features" as opposed to a bug
(though I'd appreciate it if you could open a BZ ticket about it:
http://issues.apache.org/SpamAssassin/).  In short, there's no problem --
it'll happen the first time you run sa-update in 3.1.4 and you're using
updatedir to aim at a non-standard (and already existing) location.

The code assumes that certain files should exist if the update directory
already exists, so when it tries to delete the files and they're not
there, it shows a warning -- but if this is the first time sa-update
from 3.1.4 is run, the channel pre file won't exist.

-- 
Randomly Generated Tagline:
Gimme two brains on drugs, over easy, and bacon...


pgpeGNLdCLScZ.pgp
Description: PGP signature