Advanced
Mailing List Archive

Mailing List Archive

  1. Home >
  2. SpamAssassin>
  3. users
1 2 3  View All
sa-update
mjackson at barking-dog
Nov 29, 2005, 11:24 AM
Post #1 of 61 (11742 views)
Permalink
Thanks to another thread today, I discovered the sa-update script (which
must be new, or I haven't noticed it in 3+ years of using SA). However, when
I try to run it on two separate boxes, I get debug output similar to this
(when invoked with no command line options other than -D):

[8348] dbg: logger: adding facilities: all
[8348] dbg: logger: logging level is DBG
[8348] dbg: generic: SpamAssassin version 3.1.0
[8348] dbg: config: score set 0 chosen.
[8348] dbg: dns: is Net::DNS::Resolver available? yes
[8348] dbg: dns: Net::DNS version: 0.53
[8348] dbg: dns: name server: 72.3.128.240, family: 2, ipv6: 0
[8348] dbg: generic: sa-update version svn231362
[8348] dbg: generic: using update directory: /etc/mail/spamassassin
[8348] dbg: diag: perl platform: 5.008005 linux
[8348] dbg: diag: module installed: Digest::SHA1, version 2.10
[8348] dbg: diag: module installed: Getopt::Long, version 2.34
[8348] dbg: diag: module installed: LWP::UserAgent, version 2.033
[8348] dbg: diag: module installed: HTTP::Date, version 1.46
[8348] dbg: diag: module installed: Archive::Tar, version 1.26
[8348] dbg: diag: module installed: IO::Zlib, version 1.04
[8348] dbg: diag: module installed: DB_File, version 1.809
[8348] dbg: diag: module installed: HTML::Parser, version 3.46
[8348] dbg: diag: module installed: MIME::Base64, version 3.05
[8348] dbg: diag: module installed: Net::DNS, version 0.53
[8348] dbg: diag: module installed: Net::SMTP, version 2.29
[8348] dbg: diag: module installed: Mail::SPF::Query, version 1.997
[8348] dbg: diag: module installed: IP::Country::Fast, version 309.002
[8348] dbg: diag: module installed: Razor2::Client::Agent, version 2.75
[8348] dbg: diag: module not installed: Net::Ident ('require' failed)
[8348] dbg: diag: module not installed: IO::Socket::INET6 ('require' failed)
[8348] dbg: diag: module not installed: IO::Socket::SSL ('require' failed)
[8348] dbg: diag: module installed: Time::HiRes, version 1.82
[8348] dbg: diag: module installed: DBI, version 1.48
[8348] dbg: channel: attempting channel updates.spamassassin.org
[8348] dbg: channel: update directory
/etc/mail/spamassassin/updates_spamassassin_org
[8348] dbg: channel: channel cf file
/etc/mail/spamassassin/updates_spamassassin_org.cf
[8348] dbg: dns: query failed: 0.1.3.updates.spamassassin.org => NXDOMAIN
[8348] dbg: channel: no updates available, skipping channel
[8348] dbg: diag: updates complete, exiting with code 0

The pertinent error seems to be the NXDOMAIN for
0.1.3.updates.spamassassin.org. Is that normal?
Re: sa-update [ In reply to ]
felicity at apache
Nov 29, 2005, 11:38 AM
Post #2 of 61 (11526 views)
Permalink
On Tue, Nov 29, 2005 at 11:24:28AM -0800, Mike Jackson wrote:
> Thanks to another thread today, I discovered the sa-update script (which
> must be new, or I haven't noticed it in 3+ years of using SA). However,

It's new with 3.1.

> when I try to run it on two separate boxes, I get debug output similar to
> this (when invoked with no command line options other than -D):
>
> [8348] dbg: dns: query failed: 0.1.3.updates.spamassassin.org => NXDOMAIN
> [8348] dbg: channel: no updates available, skipping channel
> [8348] dbg: diag: updates complete, exiting with code 0
>
> The pertinent error seems to be the NXDOMAIN for
> 0.1.3.updates.spamassassin.org. Is that normal?

It is for now. We have not, as of yet, published any updates via the
default channel, therefore there are no updates available, therefore
NXDOMAIN for the "latest update version" request.

Basically the plan was to make the script available such that when we actually
do updates, it'll be easier for people to do updates since the script will
have been out there for a while.

--
Randomly Generated Tagline:
"see, you field a lot of questions that are unimportant enough to me that
I don't bother to look them up if you're not there to answer them for me."
"excellent. I'm like Clippy."
- Lukas Karlsson and Theo
Re: sa-update [ In reply to ]
maillists at conactive
May 19, 2006, 6:31 AM
Post #3 of 61 (11472 views)
Permalink
Will Nordmeyer wrote on Fri, 19 May 2006 06:02:56 -0400:

> When I restart spamd, does it look in that directory for the updated rules
> or do I have a step I'm missing to put the rules over into the primary rules
> folder

It seems you have installed sa only for this user? It identified a "local state
dir", it should use it. You can check this by running spamassassin -D --lint
with the same user that spamd runs under.

Kai

--
Kai Schätzl, Berlin, Germany
Get your web at Conactive Internet Services: http://www.conactive.com
Re: sa-update [ In reply to ]
will at willspc
May 19, 2006, 6:56 AM
Post #4 of 61 (11478 views)
Permalink
Nope, SA is installed systemwide. I have the home foldier for the
install because the systemwide perl has to be kept at perl 5.05 for
Cobalt requirements, so I have an entire little subsystem for
spamassassin that uses Perl 5.8.3.

The spamd daemon runs as root.

Each child process runs as the user in question when it is processing a
message.

OK - I did the --lint and it appears to load the updates dir.

One of my problems with it, though, is that the 10_misc.cf in the
updates dir doesn't have the proper @@CONTACT_ADDRESS@@.

--Will

> Will Nordmeyer wrote on Fri, 19 May 2006 06:02:56 -0400:
>
> > When I restart spamd, does it look in that directory for the
updated rules
> > or do I have a step I'm missing to put the rules over into the
primary rules
> > folder
>
> It seems you have installed sa only for this user? It identified
a "local state
> dir", it should use it. You can check this by running spamassassin -
D --lint
> with the same user that spamd runs under.
>
> Kai
>
> --
> Kai Schätzl, Berlin, Germany
> Get your web at Conactive Internet Services: http://www.conactive.com
>
>
>
>
Re: sa-update [ In reply to ]
maillists at conactive
May 19, 2006, 3:31 PM
Post #5 of 61 (11461 views)
Permalink
Will Nordmeyer wrote on Fri, 19 May 2006 09:56:21 -0400:

> One of my problems with it, though, is that the 10_misc.cf in the
> updates dir doesn't have the proper @@CONTACT_ADDRESS@@.

I think that's a known problem. This address gets inserted when you "perl
Makefile.PL" and they forgot about it. If you need it you may insert it
yourself. (That may change some checksum, though, I don't know.)

Kai

--
Kai Schätzl, Berlin, Germany
Get your web at Conactive Internet Services: http://www.conactive.com
Re: sa-update [ In reply to ]
felicity at apache
May 19, 2006, 3:44 PM
Post #6 of 61 (11475 views)
Permalink
On Sat, May 20, 2006 at 12:31:16AM +0200, Kai Schaetzl wrote:
> > One of my problems with it, though, is that the 10_misc.cf in the
> > updates dir doesn't have the proper @@CONTACT_ADDRESS@@.
>
> I think that's a known problem. This address gets inserted when you "perl
> Makefile.PL" and they forgot about it. If you need it you may insert it
> yourself. (That may change some checksum, though, I don't know.)

Put the config line in your /etc/mail/spamassassin/local.cf and that'll take
care of it for now.

--
Randomly Generated Tagline:
Beware of the opinion of someone without any facts.
Re: sa-update [ In reply to ]
felicity at apache
Jul 23, 2006, 1:50 PM
Post #7 of 61 (11431 views)
Permalink
On Sun, Jul 23, 2006 at 10:44:29PM +0200, Christian Schade wrote:
> > Assuming the updates.spamassassin.org (default) channel ...
>
> Are there any other (usefull) channels beside the default jet?

We have a jet? Cool! :P

I can't speak for anyone else out there, but from the ASF SpamAssassin
project, there's only the one channel available right now.

--
Randomly Generated Tagline:
If Love is grand... Divorce is twenty grand...
RE: Sa-update [ In reply to ]
scheidell at secnap
Apr 6, 2007, 4:36 AM
Post #8 of 61 (11306 views)
Permalink
> -----Original Message-----
> From: Emre BALCI [mailto:emrebalci@yahoo.com]
> Sent: Friday, April 06, 2007 6:59 AM
> To: users@spamassassin.apache.org
> Subject: Sa-update
>
>
> Hi all
> I am using sa on gentoo when I run sa-update its
> copying rules into /var/lib/spamassassin/version
> I should copy rules form this location to
> /usr/share/spamassassin ?
No, these rules REPLACE the rules in ../share
Copying them might get SA to read some old rules, maybe creating an
inconstancy.

>can I use rules between different versions ?

You would need to add a copy/move/ sa-update/diff script to your
procedures. Probably not a bad idea.
(or, I think you might be able to see the changes via CVS browse to the
sources)

_________________________________________________________________________
This email has been scanned and certified safe by SpammerTrap(tm).
For Information please see http://www.spammertrap.com
_________________________________________________________________________
Re:sa-update [ In reply to ]
carnold5 at nc
Jul 5, 2007, 4:53 PM
Post #9 of 61 (11191 views)
Permalink
On Thu, Jul 05, 2007 at 05:01:47PM -0400,
>Install the required modules. They're listed in the INSTALL doc.
Thanks Theo!
I installed all but IO::Zlib via cpan and on IO::Zlib, it gives this error:
t/tied..........ok
t/uncomp1.......FAILED test 5
Failed 1/10 tests, 90.00% okay
t/uncomp2.......FAILED test 5
Failed 1/10 tests, 90.00% okay
Failed Test Stat Wstat Total Fail Failed List of Failed
-------------------------------------------------------------------------------
t/uncomp1.t 10 1 10.00% 5
t/uncomp2.t 10 1 10.00% 5
1 subtest skipped.
Failed 2/10 test scripts, 80.00% okay. 2/123 subtests failed, 98.37% okay.
make: *** [test_dynamic] Error 255
/usr/bin/make test -- NOT OK
Running make install
make test had returned bad status, won't install without force

Chris

Attached Files:

Re: Sa-update [ In reply to ]
ihtraum18 at gmail
Jul 25, 2008, 6:06 AM
Post #10 of 61 (10940 views)
Permalink
I could see the problem:

read on:
http://www.ijs.si/software/amavisd/#faq-spam


amavisd realized that's who manages the upgrade of headers, overwriting any
changes made by spamassassin.

So what I incialmente is that the check is made by spammers by spamassassin
alone, without the amavis as an intermediary.

Desabilitei in / etc / amavis / amavisd.conf the line that makes the check
for spam:

# @ bypass_spam_checks_acl = qw (.);



I do not know if this is the appropriate list, but:

uncomment the above is sufficient for most amavis not call the spamassassin?

I ask this because below that the configuration file, you have several rules
that relate to spamassassin.



[]´s


On Fri, Jul 25, 2008 at 8:58 AM, Eduardo Júnior <ihtraum18@gmail.com> wrote:

>
> Hi,
>
>
> I have just done an update in the rules of my spamassassin with sa-update
>
> He dropped everything to /var/lib/spamassassin/version
>
> He created the directory with several updates_spamassassin_org. Cf
> And a updates_spamassassin_org.cf and updates_spamassassin_org.pre.
>
> Peguei of the includes updates_spamassassin_org.cf and put in
> /etc/spamassassin/local.cf and I made a copy of my *. cf / etc /
> spamassassin to maintain consistently referenced in the path includes.
>
> Executei a /init.d/spamassassin restart to restart.
>
> The question is:
>
> I am making an accurate?
> How to test if these new rules are working properly?
>
>
>
> I´m using:
>
> # spamassassin --version
> SpamAssassin version 3.1.7
> running on Perl version 5.8.8
>
>
>
>
> []´s
>
> --
> Eduardo Júnior
> GNU/Linux user #423272
>
> :wq
>



--
Eduardo Júnior
GNU/Linux user #423272

:wq
RE: Sa-update [ In reply to ]
Bowie_Bailey at BUC
Jul 25, 2008, 6:23 AM
Post #11 of 61 (10932 views)
Permalink
Eduardo Júnior wrote:
>
> I have just done an update in the rules of my spamassassin with
> sa-update
>
> He dropped everything to /var/lib/spamassassin/version
>
> He created the directory with several updates_spamassassin_org. Cf
> And a updates_spamassassin_org.cf and updates_spamassassin_org.pre.
>
> Peguei of the includes updates_spamassassin_org.cf and put in
> /etc/spamassassin/local.cf and I made a copy of my *. cf / etc /
> spamassassin to maintain consistently referenced in the path
> includes.

I'm not quite sure what you are saying here, but it sounds like you said
that you moved the .cf files from the updates directory to
/etc/spamassassin. Don't do that! :)

sa-update will update the built-in rules for SA (as well as any other
channels you define). These updates will be put under
/var/lib/spamassassin. SpamAssassin will automatically look in that
directory and load the new rules. You don't need to do anything to
them.

Updating SpamAssassin works like this:

1) sa-update
2) restart SpamAssassin

You don't need to do anything else.

--
Bowie
Re: Sa-update [ In reply to ]
maillists at conactive
Jul 25, 2008, 6:31 AM
Post #12 of 61 (10937 views)
Permalink
Eduardo Júnior wrote on Fri, 25 Jul 2008 08:58:25 -0300:

> Peguei of the includes updates_spamassassin_org.cf and put in
> /etc/spamassassin/local.cf and I made a copy of my *. cf / etc /
> spamassassin to maintain consistently referenced in the path includes.

Not sure what this means. You have to do *nothing* after an sa-update with
the exception of restarting spamd or whatever daemon application you are
using. In case you symlinked some stuff from /etc/mail/spamassassin to
/var/lib/spamassassin or reverse or copied some stuff over: this was
wrong, revert it.

Kai

--
Kai Schätzl, Berlin, Germany
Get your web at Conactive Internet Services: http://www.conactive.com
Re: Sa-update [ In reply to ]
richard.frovarp at sendit
Jul 25, 2008, 7:17 AM
Post #13 of 61 (10921 views)
Permalink
Kai Schaetzl wrote:
> Eduardo Júnior wrote on Fri, 25 Jul 2008 08:58:25 -0300:
>
>
>> Peguei of the includes updates_spamassassin_org.cf and put in
>> /etc/spamassassin/local.cf and I made a copy of my *. cf / etc /
>> spamassassin to maintain consistently referenced in the path includes.
>>
>
> Not sure what this means. You have to do *nothing* after an sa-update with
> the exception of restarting spamd or whatever daemon application you are
> using. In case you symlinked some stuff from /etc/mail/spamassassin to
> /var/lib/spamassassin or reverse or copied some stuff over: this was
> wrong, revert it.
>
> Kai
>
>
You may want to run sa-compile if the rules have changed. That is if you
use sa-compile. Then restart whatever is using SA.
Re: Sa-update [ In reply to ]
ihtraum18 at gmail
Jul 25, 2008, 8:04 AM
Post #14 of 61 (10907 views)
Permalink
At least in my pathhad no sa-compile.

But that's not important now.
I did as recommended by colleagues above, correcting my mistakes and
understanding the operation.
Until had found odd repetition of files.


But when I run sa-update, my list of rules is not updated and can now be
used after restarted?
I must compile the rules updated with sa-compile so they can be used?

any reference


[]´s


On Fri, Jul 25, 2008 at 11:17 AM, Richard Frovarp <
richard.frovarp@sendit.nodak.edu> wrote:

> Kai Schaetzl wrote:
>
>> Eduardo Júnior wrote on Fri, 25 Jul 2008 08:58:25 -0300:
>>
>>
>>
>>> Peguei of the includes updates_spamassassin_org.cf and put in
>>> /etc/spamassassin/local.cf and I made a copy of my *. cf / etc /
>>> spamassassin to maintain consistently referenced in the path includes.
>>>
>>>
>>
>> Not sure what this means. You have to do *nothing* after an sa-update with
>> the exception of restarting spamd or whatever daemon application you are
>> using. In case you symlinked some stuff from /etc/mail/spamassassin to
>> /var/lib/spamassassin or reverse or copied some stuff over: this was wrong,
>> revert it.
>>
>> Kai
>>
>>
>>
> You may want to run sa-compile if the rules have changed. That is if you
> use sa-compile. Then restart whatever is using SA.
>



--
Eduardo Júnior
GNU/Linux user #423272

:wq
Re: Sa-update [ In reply to ]
mouss at netoyen
Jul 25, 2008, 9:06 AM
Post #15 of 61 (10953 views)
Permalink
Eduardo Júnior wrote:
> At least in my pathhad no sa-compile.
>
> But that's not important now.
> I did as recommended by colleagues above, correcting my mistakes and
> understanding the operation.
> Until had found odd repetition of files.
>
>
> But when I run sa-update, my list of rules is not updated and can now be
> used after restarted?
> I must compile the rules updated with sa-compile so they can be used?
>


there are (mainly) two set of rules:

- your own rules
- public rules


your own rules are those rules that you write yourself. these are not
updated by any SA tool. these are the rule that _you_ decide to
implement. these rules are generally found in $base/etc/spamassassin or
$base/etc/mail/spamassassin/.

the public rules are the ones that all of us have (whether we use
directly, we override, or not). at installation time, they are in an
installation directory ($base/share/spamassassin/). when you use
sa-update, the "original" ones are no more used and your SA will use the
updated ones.


if you use sa-update, the public rules are updated. and optionally, you
can get more rules. all these go to a new directory (generally
$datadir/spamassassin/).


once you update your rules, you can run sa-compile. some people do. some
don't.
RE: Sa-update [ In reply to ]
Bowie_Bailey at BUC
Jul 25, 2008, 9:28 AM
Post #16 of 61 (10930 views)
Permalink
Eduardo Júnior wrote:
> At least in my pathhad no sa-compile.
>
> But that's not important now.
> I did as recommended by colleagues above, correcting my mistakes and
> understanding the operation.
> Until had found odd repetition of files.
>
>
> But when I run sa-update, my list of rules is not updated and can now
> be used after restarted?
> I must compile the rules updated with sa-compile so they can be used?

By default SpamAssassin does not compile the rules. If you have set it
up to compile the rules, you will need to re-run sa-compile whenever you
update them. If you have not used sa-compile in the past, you do not
need to use it now.

--
Bowie
Re: Sa-update [ In reply to ]
mkettler_sa at verizon
Jul 25, 2008, 4:39 PM
Post #17 of 61 (10912 views)
Permalink
Eduardo Júnior wrote:
>
> Hi,
>
>
> I have just done an update in the rules of my spamassassin with sa-update
>
> He dropped everything to /var/lib/spamassassin/version
>
> He created the directory with several updates_spamassassin_org. Cf
> And a updates_spamassassin_org.cf <http://updates_spamassassin_org.cf>
> and updates_spamassassin_org.pre.
>
> Peguei of the includes updates_spamassassin_org.cf
> <http://updates_spamassassin_org.cf> and put in
> /etc/spamassassin/local.cf <http://local.cf> and I made a copy of my
> *. cf / etc / spamassassin to maintain consistently referenced in the
> path includes.
No. DO NOT copy the files from where sa-update put them. Just run it,
and leave them where they are. SA will find them where sa-update put them.

The *ONLY* files that should be in /etc/spamassassin are the ones you
put there (ie: local.cf, or any add-on rules that aren't a part of the
standard set).


>
> Executei a /init.d/spamassassin restart to restart.
>
> The question is:
>
> I am making an accurate?
> How to test if these new rules are working properly?
If you want to make sure your SA is detecting the new rule directory
sa-update created:

Look near the top of the output of "spamassassin --lint -D", it should
mention the new directory about a half page down or so.
>
>
>
> I´m using:
>
> # spamassassin --version
> SpamAssassin version 3.1.7
> running on Perl version 5.8.8
You really should consider upgrading versions. sa-update only updates
rules, and there have been no new rules for the 3.1.x family since late
2007. We're on 3.2.5 now.
Re: Sa-update [ In reply to ]
ihtraum18 at gmail
Jul 26, 2008, 6:42 AM
Post #18 of 61 (10904 views)
Permalink
On Fri, Jul 25, 2008 at 8:39 PM, Matt Kettler <mkettler_sa@verizon.net>wrote:

> Eduardo Júnior wrote:
>
>>
>> Hi,
>>
>>
>> I have just done an update in the rules of my spamassassin with sa-update
>>
>> He dropped everything to /var/lib/spamassassin/version
>>
>> He created the directory with several updates_spamassassin_org. Cf
>> And a updates_spamassassin_org.cf <http://updates_spamassassin_org.cf>
>> and updates_spamassassin_org.pre.
>>
>> Peguei of the includes updates_spamassassin_org.cf <
>> http://updates_spamassassin_org.cf> and put in /etc/spamassassin/local.cf<
>> http://local.cf> and I made a copy of my *. cf / etc / spamassassin to
>> maintain consistently referenced in the path includes.
>>
> No. DO NOT copy the files from where sa-update put them. Just run it, and
> leave them where they are. SA will find them where sa-update put them.
>
> The *ONLY* files that should be in /etc/spamassassin are the ones you put
> there (ie: local.cf, or any add-on rules that aren't a part of the
> standard set).




Ok, but I already did this, correct this, as this before.



>
>
>
>> Executei a /init.d/spamassassin restart to restart.
>>
>> The question is:
>>
>> I am making an accurate?
>> How to test if these new rules are working properly?
>>
> If you want to make sure your SA is detecting the new rule directory
> sa-update created:
>
> Look near the top of the output of "spamassassin --lint -D", it should
> mention the new directory about a half page down or so.



Yes, debugging shows me that information.




>
>>
>>
>> I´m using:
>>
>> # spamassassin --version
>> SpamAssassin version 3.1.7
>> running on Perl version 5.8.8
>>
> You really should consider upgrading versions. sa-update only updates
> rules, and there have been no new rules for the 3.1.x family since late
> 2007. We're on 3.2.5 now.



Unfortunately, it's not possible now, because the server is in production
and can't stop.
But i already proposed an updated.



[]'s



--
Eduardo Júnior
GNU/Linux user #423272

:wq
Re: Sa-update [ In reply to ]
ihtraum18 at gmail
Aug 6, 2008, 6:31 AM
Post #19 of 61 (10854 views)
Permalink
Continuing with the sa-update

When run sa-update -D, my output has the following excerpt:

[14661] dbg: diag: module not installed: IP:: Country:: Fast ( 'require'
failed)
[14661] dbg: diag: module not installed: Razor2:: Client:: Agent ( 'require'
failed)
[14661] dbg: diag: module not installed: Net:: Ident ( 'require' failed)
[14661] dbg: diag: module not installed: IO:: Socket:: INET6 ( 'require'
failed)
[14661] dbg: diag: module not installed: IO:: Socket:: SSL ( 'require'
failed)


They have some influence in learning?
And how to verify that the recognition of spam in fact improved?



On Sat, Jul 26, 2008 at 10:42 AM, Eduardo Júnior <ihtraum18@gmail.com>wrote:

>
>
> On Fri, Jul 25, 2008 at 8:39 PM, Matt Kettler <mkettler_sa@verizon.net>wrote:
>
>> Eduardo Júnior wrote:
>>
>>>
>>> Hi,
>>>
>>>
>>> I have just done an update in the rules of my spamassassin with sa-update
>>>
>>> He dropped everything to /var/lib/spamassassin/version
>>>
>>> He created the directory with several updates_spamassassin_org. Cf
>>> And a updates_spamassassin_org.cf <http://updates_spamassassin_org.cf>
>>> and updates_spamassassin_org.pre.
>>>
>>> Peguei of the includes updates_spamassassin_org.cf <
>>> http://updates_spamassassin_org.cf> and put in /etc/spamassassin/
>>> local.cf <http://local.cf> and I made a copy of my *. cf / etc /
>>> spamassassin to maintain consistently referenced in the path includes.
>>>
>> No. DO NOT copy the files from where sa-update put them. Just run it, and
>> leave them where they are. SA will find them where sa-update put them.
>>
>> The *ONLY* files that should be in /etc/spamassassin are the ones you put
>> there (ie: local.cf, or any add-on rules that aren't a part of the
>> standard set).
>
>
>
>
> Ok, but I already did this, correct this, as this before.
>
>
>
>>
>>
>>
>>> Executei a /init.d/spamassassin restart to restart.
>>>
>>> The question is:
>>>
>>> I am making an accurate?
>>> How to test if these new rules are working properly?
>>>
>> If you want to make sure your SA is detecting the new rule directory
>> sa-update created:
>>
>> Look near the top of the output of "spamassassin --lint -D", it should
>> mention the new directory about a half page down or so.
>
>
>
> Yes, debugging shows me that information.
>
>
>
>
>>
>>>
>>>
>>> I´m using:
>>>
>>> # spamassassin --version
>>> SpamAssassin version 3.1.7
>>> running on Perl version 5.8.8
>>>
>> You really should consider upgrading versions. sa-update only updates
>> rules, and there have been no new rules for the 3.1.x family since late
>> 2007. We're on 3.2.5 now.
>
>
>
> Unfortunately, it's not possible now, because the server is in production
> and can't stop.
> But i already proposed an updated.
>
>
>
> []'s
>
>
>
> --
> Eduardo Júnior
> GNU/Linux user #423272
>
> :wq
>



--
Eduardo Júnior
GNU/Linux user #423272

:wq
Re: Sa-update [ In reply to ]
mkettler_sa at verizon
Aug 6, 2008, 4:44 PM
Post #20 of 61 (10838 views)
Permalink
Eduardo Júnior wrote:
>
> Continuing with the sa-update
>
> When run sa-update -D, my output has the following excerpt:
>
> [14661] dbg: diag: module not installed: IP:: Country:: Fast (
> 'require' failed)
> [14661] dbg: diag: module not installed: Razor2:: Client:: Agent (
> 'require' failed)
> [14661] dbg: diag: module not installed: Net:: Ident ( 'require' failed)
> [14661] dbg: diag: module not installed: IO:: Socket:: INET6 (
> 'require' failed)
> [14661] dbg: diag: module not installed: IO:: Socket:: SSL ( 'require'
> failed)
>
>
> They have some influence in learning?
All of those are modules that support optional features.

The IP::Country::Fast can influence learning, by providing additional
token data on what countries the message has been routed through, but
it's hardly critical.

> And how to verify that the recognition of spam in fact improved?
Look for higher BAYES_* rules hitting on spam, and lower ones on nonspam.
Re: sa-update [ In reply to ]
mouss at netoyen
Oct 23, 2008, 4:31 PM
Post #21 of 61 (10590 views)
Permalink
Jean-Paul Natola a écrit :
> Hi all,
>
> I've been out of the loop for a couple of months do a rollout, so I came back
> to my SA today as I have seen A LOT more spam coming in than normal, I
> upgraded to 3.2.5 today, and ran sa-update but , i dont seem to see any new
> rules, and i;m getting clobbered with spam.
>
>
> Has something cahnged? are the rules still going into
> /usr/local/etc/mail/spamassasin

no these are your custom rules.

sa-update rules go to /var/db/spamassassin/...


>
> I run site wide config
>
> freebsd 6.2
Re: sa-update [ In reply to ]
lcroker at megacable
Oct 23, 2008, 4:38 PM
Post #22 of 61 (10600 views)
Permalink
I did it today... I have the server in FREBsd and the new rules are
in /var/db/spamassassin/3.002005/updates_spamassassin_org. The
conventional rules are in /usr/local/share/spamassassin.

Maybe you can find any directory named spamassassin to check where
they are.

Regards.

On Thu, 2008-10-23 at 19:18 -0400, Jean-Paul Natola wrote:

> Hi all,
>
> I've been out of the loop for a couple of months do a rollout, so I came back
> to my SA today as I have seen A LOT more spam coming in than normal, I
> upgraded to 3.2.5 today, and ran sa-update but , i dont seem to see any new
> rules, and i;m getting clobbered with spam.
>
>
> Has something cahnged? are the rules still going into
> /usr/local/etc/mail/spamassasin
>
> I run site wide config
>
> freebsd 6.2
>
> TIA
>
> JP
>


Luis Croker
SCSA - SCNA
Administrador de Sistemas
Megacable Comunicaciones
GPG Key1024D/48C1764B
Key fingerprint = E8B6 E84F ECE4 661E 30C7 7208 042D BD09 48C1 764B

Attached Files:

RE: sa-update [ In reply to ]
jnatola at familycareintl
Oct 23, 2008, 4:43 PM
Post #23 of 61 (10625 views)
Permalink
I used to get about 19-15 spam messages in my box per week, now , eve today I
got 11-

and they are hardly hitting any rules, anything new (rbl's etc..) I should
look into?

________________________________

From: Luis Croker [mailto:lcroker@megacable.com.mx]
Sent: Thu 10/23/2008 19:38
To: Jean-Paul Natola
Cc: users@spamassassin.apache.org
Subject: Re: sa-update



I did it today... I have the server in FREBsd and the new rules are in
/var/db/spamassassin/3.002005/updates_spamassassin_org. The conventional
rules are in /usr/local/share/spamassassin.

Maybe you can find any directory named spamassassin to check where they
are.

Regards.

On Thu, 2008-10-23 at 19:18 -0400, Jean-Paul Natola wrote:

Hi all,

I've been out of the loop for a couple of months do a rollout, so I
came back
to my SA today as I have seen A LOT more spam coming in than normal,
I
upgraded to 3.2.5 today, and ran sa-update but , i dont seem to see
any new
rules, and i;m getting clobbered with spam.


Has something cahnged? are the rules still going into
/usr/local/etc/mail/spamassasin

I run site wide config

freebsd 6.2

TIA

JP



Luis Croker
SCSA - SCNA
Administrador de Sistemas
Megacable Comunicaciones <http://www.megacable.com.mx/>
GPG Key1024D/48C1764B <http://pgp.mit.edu/>
Key fingerprint = E8B6 E84F ECE4 661E 30C7 7208 042D BD09 48C1 764B
Re: sa-update [ In reply to ]
jk at jkart
Oct 23, 2008, 5:08 PM
Post #24 of 61 (10597 views)
Permalink
Am 24.10.2008 1:31 Uhr, schrieb mouss:
> Jean-Paul Natola a écrit :
>> Hi all,
>>
>> I've been out of the loop for a couple of months do a rollout, so I came back
>> to my SA today as I have seen A LOT more spam coming in than normal, I
>> upgraded to 3.2.5 today, and ran sa-update but , i dont seem to see any new
>> rules, and i;m getting clobbered with spam.
>>
>>
>> Has something cahnged? are the rules still going into
>> /usr/local/etc/mail/spamassasin
>
> no these are your custom rules.
>
> sa-update rules go to /var/db/spamassassin/...

But on Debian to /var/lib/spamassassin/.. ;)

>
>
>>
>> I run site wide config
>>
>> freebsd 6.2
>
>


--
mit freundlichem Gruss - with kind regard
Jim Knuth
#ICQ 277289867

Bitte keine geschaeftliche Anfragen.
Dies ist mein privater Account!
Please ask no business inquiries.
That is only my private account!
RE: sa-update [ In reply to ]
rdoyle at islandnetworks
Oct 23, 2008, 8:14 PM
Post #25 of 61 (10594 views)
Permalink
On Thu, 2008-10-23 at 19:43 -0400, Jean-Paul Natola wrote:
> I used to get about 19-15 spam messages in my box per week, now , eve today I
> got 11-
>
> and they are hardly hitting any rules, anything new (rbl's etc..) I should
> look into?
jm_sought rules are useful
http://wiki.apache.org/spamassassin/SoughtRules
1 2 3  View All

©2024 GT.net. A Gossamer Threads company.
5th Floor, 455 Granville St., Vancouver, BC V6C 1T1, Canada | Legal