Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: SpamAssassin: users

updates

 

 

SpamAssassin users RSS feed   Index | Next | Previous | View Threaded


bernardrule at hotmail

Nov 23, 2008, 3:46 PM

Post #1 of 17 (2089 views)
Permalink
updates

hi
i am not very technical so please help

i have a debian server with spammassassin 3.000003. i guess this has never
been updated

do i just use the cmd

sa-update && service spamassassin restart

what do i need to do?

how often should i update after it is updated?

can it be scheduled to be automatic?

will i loose any configuration on the system?

there are local email accounts which are popped by a windows server

are the updates primarly for improving what and how SA detects spam?
--
View this message in context: http://www.nabble.com/updates-tp20652630p20652630.html
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.


guenther at rudersport

Nov 23, 2008, 4:15 PM

Post #2 of 17 (2011 views)
Permalink
Re: updates [In reply to]

On Sun, 2008-11-23 at 15:46 -0800, bernier wrote:
> hi
> i am not very technical so please help
>
> i have a debian server with spammassassin 3.000003. i guess this has never
> been updated

sa-update isn't available with 3.0.3, it has been added since 3.1.0.

> do i just use the cmd
>
> sa-update && service spamassassin restart
>
> what do i need to do?
>
> how often should i update after it is updated?
>
> can it be scheduled to be automatic?
>
> will i loose any configuration on the system?

No.

> there are local email accounts which are popped by a windows server
>
> are the updates primarly for improving what and how SA detects spam?

It's used to update the stock rules (and third-party rule-sets), and
it's purpose is to fix issues with the rules and improve the rules
without the need to push a full new SA release. It does not harm your
configuration or touch custom modifications in any way (given you placed
those properly in /etc/mail/spamassassin and did not mess with the stock
rules).

http://wiki.apache.org/spamassassin/RuleUpdates

Well, if you could use it...


--
char *t="\10pse\0r\0dtu\0.@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<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}


martin at gregorie

Nov 23, 2008, 4:28 PM

Post #3 of 17 (2026 views)
Permalink
Re: updates [In reply to]

On Sun, 2008-11-23 at 15:46 -0800, bernier wrote:
> hi
> i am not very technical so please help
>
> i have a debian server with spammassassin 3.000003. i guess this has never
> been updated
>
> do i just use the cmd
>
Use cron to do a periodic update. Here's my set-up:

I put a file called sa_update in /etc/cron.weekly.

=============== sa_update ===================
#!/bin/bash
#
# Update the Spamassassin rules
#
sau=/usr/bin/sa-update

if [ -x $chkd ]
then
$sau
err=$?
case $err in
0) echo "Spamassassin rules update completed.";
service spamassassin restart;
echo "Spamassassin restarted." ;;

1) echo "No Spamassassin rule updates available.";;

2) echo "Spamassassin rules updates available";
echo "Site pre files lint check failed.";
echo "Fix the files and try again.";;

*) echo "Spamassassin rules update failed: error=$err"
esac
else
echo "Error: $sau does not exist"
exit 0
fi
=============================================

This runs once a week, which is often enough since a rules update only
appears every few weeks.

As you can see, if the rules were updated it restarts the spamassassin
service (which runs spamd) with the 'service' command. Otherwise it just
reports what happened.

In any case, the report is mailed to root.


Martin


mkettler_sa at verizon

Nov 23, 2008, 6:19 PM

Post #4 of 17 (2022 views)
Permalink
Re: updates [In reply to]

bernier wrote:
> hi
> i am not very technical so please help
>
> i have a debian server with spammassassin 3.000003. i guess this has never
> been updated
>
> do i just use the cmd
>
> sa-update && service spamassassin restart
>
> what do i need to do?
>

No. sa-update only updates the ruleset. It does not update the main code
(ie: the engine). For that, you need to download and install a newer
version (you can just install on top of the existing one).

> how often should i update after it is updated?
>
sa-update? I'd run it once a day. However, if you stick with 3.0.x you
can run it once and never again. It's highly doubtful there will be a
rule update to the 3.0 rulesets. We're on 3.2.5 these days, and 3.3.0 is
in the works.
> can it be scheduled to be automatic?
>
Sure, you can cron-job it.
> will i loose any configuration on the system?
>
Only if someone has mistakenly edited the default rules, instead of
using local.cf to over-ride them.

> there are local email accounts which are popped by a windows server
>
> are the updates primarly for improving what and how SA detects spam?
>
They're half of what SA uses to detect spam. The other half is the code
base (Most of the header parsing and HTML decoding happens here).


uhlar at fantomas

Nov 24, 2008, 12:28 AM

Post #5 of 17 (2005 views)
Permalink
Re: updates [In reply to]

On 23.11.08 15:46, bernier wrote:
> i have a debian server with spammassassin 3.000003. i guess this has never
> been updated

upgrade the server, 3.0.3 was default afaik in sarge, which is obsolete and
unsupported. Is not possible, there was newer version in volatile and even
newer in volatile-sloppy, seems it's still there.

> do i just use the cmd
>
> sa-update && service spamassassin restart

sa-update is supported since SA 3.1. I don't have "service" on my debian
system and use "/etc/init.d/spamassassin reload" instead.

> how often should i update after it is updated?

whenever an update comes out. Some people try it daily.

> can it be scheduled to be automatic?

yes.

> will i loose any configuration on the system?

no.

> are the updates primarly for improving what and how SA detects spam?

yes.

--
Matus UHLAR - fantomas, uhlar [at] fantomas ; 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.
"The box said 'Requires Windows 95 or better', so I bought a Macintosh".


bernard.rule at 3-sixty

Nov 25, 2008, 2:27 PM

Post #6 of 17 (1995 views)
Permalink
Re: updates [In reply to]

what do i need to do to change to a the new version? please let me know the
commands
will it change any configurations etc?

* Bernard Rule
* Technical Consultant

* 3-Sixty NZ Limited*
Information Technology Specialists*
Project Management Software and IT Support
* www.teamworksPM.co.nz <http://www.teamworkspm.co.nz/>
www.3-sixty.co.nz

Mobile +64 (0)292 360 361
Office +64 (0)9 473 9744
Email bernard.rule [at] 3-sixty <paul.sharp [at] 3-sixty>

--------------------------------------------------------------

CAUTION - This message may contain privileged and confidential information
intended only for the use of the addressee named above. If you are not the
intended recipient of this message you are hereby notified that any use,
dissemination, distribution or reproduction of this message is prohibited.
If you have received this message in error please notify 3 Sixty NZ
immediately. Any views expressed in this message are those of the individual
sender and may not necessarily reflect the views of 3 Sixty NZ Limited.

Please consider the environment before printing this e-mail notice.

SaaS Project Management

Resource Planning

Collaboration

Timesheets

Issue and Risks

Hosted or Install onsite

www.teamworkspm.co.nz



Iplanware's *Official Gold Partner*

Asia Pacific Region



On Mon, Nov 24, 2008 at 9:28 PM, Matus UHLAR - fantomas
<uhlar [at] fantomas>wrote:

> On 23.11.08 15:46, bernier wrote:
> > i have a debian server with spammassassin 3.000003. i guess this has
> never
> > been updated
>
> upgrade the server, 3.0.3 was default afaik in sarge, which is obsolete and
> unsupported. Is not possible, there was newer version in volatile and even
> newer in volatile-sloppy, seems it's still there.
>
> > do i just use the cmd
> >
> > sa-update && service spamassassin restart
>
> sa-update is supported since SA 3.1. I don't have "service" on my debian
> system and use "/etc/init.d/spamassassin reload" instead.
>
> > how often should i update after it is updated?
>
> whenever an update comes out. Some people try it daily.
>
> > can it be scheduled to be automatic?
>
> yes.
>
> > will i loose any configuration on the system?
>
> no.
>
> > are the updates primarly for improving what and how SA detects spam?
>
> yes.
>
> --
> Matus UHLAR - fantomas, uhlar [at] fantomas ; 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.
> "The box said 'Requires Windows 95 or better', so I bought a Macintosh".
>


mr88talent at gmail

Nov 27, 2008, 8:07 AM

Post #7 of 17 (1972 views)
Permalink
Re: updates [In reply to]

On 11/25/08, bernard rule <bernard.rule [at] 3-sixty> wrote:
> what do i need to do to change to a the new version? please let me know the commands
> will it change any configurations etc?
>
> Bernard Rule
> Technical Consultant
>

How are you integrating SA? At this time installing from
http://www.backports.org/dokuwiki/doku.php would be the least
disruptive to your system. You should 'simulate' installation with the
-s switch to see what will get upgraded (perl for example). For
example, once the backports source is in sources.list (see
http://www.backports.org/dokuwiki/doku.php?id=instructions):

apt-get -s -t etch-backports install spamassassin

However, yes, configuration changes will be needed.
http://svn.apache.org/repos/asf/spamassassin/branches/3.2/UPGRADE
http://spamassassin.apache.org/full/3.2.x/doc/

For instance, the DCC plugin may need to be enabled by editing
v310.pre and in local.cf you should explicitly set trusted_networks.
If you previously installed the ImageInfo plugin, you would need to
remove it prior to upgrading. Same goes for FuzzyOcr.

If you are using amavisd-new, and upgrade from 20030616-p10 to a new
version without knowing some important things in advance, the
installation with leave you with blank configuration files, dpkg
errors and an amavisd-new that will not start (meaning mail will stop
flowing).

Understand that on Debian, any 2.x.x version of amavisd-new no longer
uses amavisd.conf, but instead spreads its configuration over a number
of files:

/usr/share/amavis/conf.d/10-debian_scripts
/usr/share/amavis/conf.d/20-package
/etc/amavis/conf.d/01-debian
/etc/amavis/conf.d/05-domain_id
/etc/amavis/conf.d/05-node_id
/etc/amavis/conf.d/15-av_scanners
/etc/amavis/conf.d/15-content_filter_mode
/etc/amavis/conf.d/20-debian_defaults
/etc/amavis/conf.d/25-amavis_helpers
/etc/amavis/conf.d/30-template_localization
/etc/amavis/conf.d/50-user

(note that most changes to the configuration will be made in
/etc/amavis/conf.d/50-user)

Here is a hint to avoid amavisd-new upgrade issues:
http://marc.info/?l=amavis-user&m=114918487508776

Generally, since you are still on sarge, this could range from being a
fairly straightforward upgrade to a major undertaking that leaves you
with an unusable system. Have fun with all that.

--
Gary V


dan.mcdonald at austinenergy

Apr 12, 2012, 7:29 AM

Post #8 of 17 (1398 views)
Permalink
Re: updates [In reply to]

On 4/12/12 6:22 AM, "Kevin A. McGrail" <KMcGrail [at] PCCC> wrote:

> Updates are not publishing because of a lack of corpora to test the rules
> against. Sorry, known issue.

Can you remind me how far below the threshold we are for corpora? If I hand
qualify another couple of thousand hams or so would that be significant? Or
is our deficit significantly larger than that?

> Regards,
> KAM
>
> joea <joea [at] j4computers> wrote:
>> when running sa-update in debug, always end up with this:
>>
>> channel: current version is 895075, new version is 895075, skipping channel
>>
>> Are there no updates, or am I misconfigured for rules updates?
>


jhardin at impsec

Apr 12, 2012, 8:50 AM

Post #9 of 17 (1394 views)
Permalink
Re: updates [In reply to]

On Thu, 12 Apr 2012, Daniel McDonald wrote:

> On 4/12/12 6:22 AM, "Kevin A. McGrail" <KMcGrail [at] PCCC> wrote:
>
>> Updates are not publishing because of a lack of corpora to test the rules
>> against. Sorry, known issue.
>
> Can you remind me how far below the threshold we are for corpora? If I hand
> qualify another couple of thousand hams or so would that be significant? Or
> is our deficit significantly larger than that?

If you visit ruleqa.spamassassin.org and hover over a hit% in the Ham
column it will tell you the size of the corpus; same for spam.

The current corpora are ham=50658, spam=245341.

I don't remember what the thresholds currently are, but the numbers used
in the past have been a multiple of 50k, so 100k, 150k, 200k or 250k.
Darxus, you're more in tune with this than I am, what are the current
thresholds?

We probably need at least 50k more ham for ruleqa to start pushing rule
updates again. Of course, the more the better.

--
John Hardin KA7OHZ http://www.impsec.org/~jhardin/
jhardin [at] impsec FALaholic #11174 pgpk -a jhardin [at] impsec
key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79
-----------------------------------------------------------------------
...to announce there must be no criticism of the President or to
stand by the President right or wrong is not only unpatriotic and
servile, but is morally treasonous to the American public.
-- Theodore Roosevelt, 1918
-----------------------------------------------------------------------
Tomorrow: Thomas Jefferson's 269th Birthday


darxus at chaosreigns

Apr 12, 2012, 9:40 AM

Post #10 of 17 (1398 views)
Permalink
Re: updates [In reply to]

On 04/12, John Hardin wrote:
> >Can you remind me how far below the threshold we are for corpora? If I hand
> >qualify another couple of thousand hams or so would that be significant? Or
> >is our deficit significantly larger than that?

> The current corpora are ham=50658, spam=245341.
>
> I don't remember what the thresholds currently are, but the numbers
> used in the past have been a multiple of 50k, so 100k, 150k, 200k or
> 250k. Darxus, you're more in tune with this than I am, what are the
> current thresholds?

Thresholds for both are 150000. Graph here, updated weekly:
http://www.chaosreigns.com/dnswl/tot.svg
According to that, we're at 29003 spams. That matches the latest net run,
which it's based on: http://ruleqa.spamassassin.org/20120407-r1310705-n
So as of Saturday, we're at 19.3% of the spam corpora we need.

Spam age limit is 2 months.

The dev list gets an alert every day (from me) if updates haven't been
generated. It says:

"SpamAssassin version 3.3.2 has not had a rule update since 2012-02-25."

It's pretty obnoxious, but I think it's a big enough problem to justify it
being posted once a day (and I'm apparently not the only one).


New contributors aren't currently allowed due to
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6694
which has restricted visibility due to being a security bug. For the past
69 days, it has been waiting for a reply from Warren Togami to okay
declaring it not actually a security problem (which I am in favor of).
It seems this requires another member of the PMC (project management
committee) to step in and declare this not a security bug. Or for someone
with sufficient access to otherwise "fix" it, which I suspect is a very
small set of people.

Once that's cleared up, new people would be able to contribute data
(just logs of rule hits, not actual email) via
https://wiki.apache.org/spamassassin/NightlyMassCheck

--
"Go forth, and be excellent to one another." - http://www.jhuger.com/fredski.php
http://www.ChaosReigns.com


joea at j4computers

Apr 12, 2012, 10:34 AM

Post #11 of 17 (1392 views)
Permalink
Re: updates [In reply to]

>
>"SpamAssassin version 3.3.2 has not had a rule update since 2012-02-25."
>

From this, should I conclude there will be no updates to earlier versions (3.2.x for instance) ? Must I upgrade in order to update?


joe a.


darxus at chaosreigns

Apr 12, 2012, 10:37 AM

Post #12 of 17 (1395 views)
Permalink
Re: updates [In reply to]

On 04/12, joea wrote:
> >"SpamAssassin version 3.3.2 has not had a rule update since 2012-02-25."
>
> From this, should I conclude there will be no updates to earlier versions (3.2.x for instance) ? Must I upgrade in order to update?

No, I thought it was overly verbose to say it actually says:

SpamAssassin version 3.3.0 has not had a rule update since 2012-02-25.
SpamAssassin version 3.3.1 has not had a rule update since 2012-02-25.
SpamAssassin version 3.3.2 has not had a rule update since 2012-02-25.


All 3.3.x versions use the same rules.

--
"But do you have any idea how many SuperBalls you could buy if you
actually applied yourself in the world? Probably eleven, but you should
still try." - http://hyperboleandahalf.blogspot.com/
http://www.ChaosReigns.com


jhardin at impsec

Apr 12, 2012, 12:22 PM

Post #13 of 17 (1395 views)
Permalink
Re: updates [In reply to]

On 04/12, John Hardin wrote:

> The current corpora are ham=50658, spam=245341.

Duh. I got those reversed... :)

--
John Hardin KA7OHZ http://www.impsec.org/~jhardin/
jhardin [at] impsec FALaholic #11174 pgpk -a jhardin [at] impsec
key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79
-----------------------------------------------------------------------
Tomorrow: Thomas Jefferson's 269th Birthday


KMcGrail at PCCC

Apr 12, 2012, 1:28 PM

Post #14 of 17 (1396 views)
Permalink
Re: updates [In reply to]

Darxus, any chance you can add this information to the warning notice?
And I don't think it's obnoxious because once we get things working
again, it should be non-existent!

I'm cc'ing Warren again but perhaps someone has a phone number for
Warren so we can call him and see if he'll green light releasing the
security issue?

> Thresholds for both are 150000. Graph here, updated weekly:
> http://www.chaosreigns.com/dnswl/tot.svg
> According to that, we're at 29003 spams. That matches the latest net run,
> which it's based on: http://ruleqa.spamassassin.org/20120407-r1310705-n
> So as of Saturday, we're at 19.3% of the spam corpora we need.
>
> Spam age limit is 2 months.
>
> The dev list gets an alert every day (from me) if updates haven't been
> generated. It says:
>
> "SpamAssassin version 3.3.2 has not had a rule update since 2012-02-25."
>
> It's pretty obnoxious, but I think it's a big enough problem to justify it
> being posted once a day (and I'm apparently not the only one).
>
>
> New contributors aren't currently allowed due to
> https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6694
> which has restricted visibility due to being a security bug. For the past
> 69 days, it has been waiting for a reply from Warren Togami to okay
> declaring it not actually a security problem (which I am in favor of).
> It seems this requires another member of the PMC (project management
> committee) to step in and declare this not a security bug. Or for someone
> with sufficient access to otherwise "fix" it, which I suspect is a very
> small set of people.
>
> Once that's cleared up, new people would be able to contribute data
> (just logs of rule hits, not actual email) via


KMcGrail at PCCC

Apr 12, 2012, 1:30 PM

Post #15 of 17 (1393 views)
Permalink
Re: updates [In reply to]

On 4/12/2012 1:34 PM, joea wrote:
>> "SpamAssassin version 3.3.2 has not had a rule update since 2012-02-25."
>>
> > From this, should I conclude there will be no updates to earlier versions (3.2.x for instance) ? Must I upgrade in order to update?
Err, 3.3.0 was the first that included sa-update...



And yes, 3.2.x is EOL.

http://wiki.apache.org/spamassassin/ReleaseGoals


Release Support

A major release is supported for no less than 6 months after the release
of the next major release.

This means that as of July 27, 2010, all versions prior to 3.3.0 are
considered unsupported and when 3.4.0 is released, 3.3.X will be
supported for at least 6 more months.


joea at j4computers

Apr 12, 2012, 3:18 PM

Post #16 of 17 (1390 views)
Permalink
Re: updates [In reply to]

>>> On 4/12/2012 at 4:30 PM, "Kevin A. McGrail" <KMcGrail [at] PCCC> wrote:
> On 4/12/2012 1:34 PM, joea wrote:
>>> "SpamAssassin version 3.3.2 has not had a rule update since 2012-02-25."
>>>
>> > From this, should I conclude there will be no updates to earlier versions
> (3.2.x for instance) ? Must I upgrade in order to update?
> Err, 3.3.0 was the first that included sa-update...
>
>
>
> And yes, 3.2.x is EOL.
>
> http://wiki.apache.org/spamassassin/ReleaseGoals
>
>
> Release Support
>
> A major release is supported for no less than 6 months after the release
> of the next major release.
>
> This means that as of July 27, 2010, all versions prior to 3.3.0 are
> considered unsupported and when 3.4.0 is released, 3.3.X will be
> supported for at least 6 more months.

heh, well . . . for convenience, I just installed what "came with" the OS distribution, but can see I will need to do something . . . soon.

It does tell me 3.2.4 yet "sa-update" works. Runs, anyway. sa-update -V says "sa-update version svn607589"

joe a.


jhardin at impsec

Apr 13, 2012, 4:52 PM

Post #17 of 17 (1384 views)
Permalink
Re: updates [In reply to]

On Thu, 12 Apr 2012, Kevin A. McGrail wrote:

> Darxus, any chance you can add this information to the warning notice?

+1 for thresholds and current corpora size in that notice.

> And I don't think it's obnoxious because once we get things working
> again, it should be non-existent!

Agreed.

--
John Hardin KA7OHZ http://www.impsec.org/~jhardin/
jhardin [at] impsec FALaholic #11174 pgpk -a jhardin [at] impsec
key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79
-----------------------------------------------------------------------
Usually Microsoft doesn't develop products, we buy products.
-- Arno Edelmann, Microsoft product manager
-----------------------------------------------------------------------
Today: Thomas Jefferson's 269th Birthday

SpamAssassin users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.