SpamAssassin 3.0.2

Yep - I've got it running on 2 DA boxes one a straight install one an upgrade - both work fine

Rob
 
also using 3.02 however I upgraded myself as I thought DA bundles with 2.x
 
Can u tell us how you upgrade Spam Assasin ?
I have DA 1.23.3 and use SpamAssassin 2.64 (2004-01-11) on a FREEBSD box.
 
Read the howto section, and yes for FreeBSD users you have an easy way out install the port.
 
You could always just edit: /usr/local/directadmin/scripts/spam.sh

1. Change the version number to 3.0.2
2. Change the download URL to the official SA download site.
Code:
WEBPATH=http://apache.ntcity.co.uk/spamassassin/source
3. Then run it to upgrade.
# /usr/local/directadmin/scripts/spam.sh


Manual install/upgrade is just as easy though. :)

# wget http://apache.ntcity.co.uk/spamassassin/source/Mail-SpamAssassin-3.0.2.tar.gz
# tar -xzf Mail-SpamAssassin-3.0.2.tar.gz
# rm -f Mail-SpamAssassin-3.0.2.tar.gz
# cd Mail-SpamAssassin-3.0.2
# perl Makefile.pl
# make
# make install
# /usr/bin/spamd -d -c -m 5


Later.....
 
Manual install and ports install on FreeBSD 5.3 did not work.
Editing the spam.sh script worked.
 
werwin01 said:
Manual install and ports install on FreeBSD 5.3 did not work.
Editing the spam.sh script worked.

yeah the spam.sh method will work better use that, I forgot the exact method I used to be honest.
 
Hmm,
I tried the spam.sh script.
It looked to go fine.
However, emails still read 3.01
I tried restarting but am not able to:

Could not create INET socket on 127.0.0.1:783: Address already in use

I just ran a kill -TERM on the parent spamd process and restarted. All is working
 
Last edited:
OK, it seems the upgrade work fine on Red Hat Enterprise AS3.

This is what I got on emails:
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on ...
X-Spam-Level: *
X-Spam-Status: No, score=1.6 required=5.0 tests=AWL,FORGED_RCVD_HELO,
HTML_90_100,HTML_MESSAGE,HTML_TAG_EXIST_MARQUEE,HTML_TAG_EXIST_TBODY
autolearn=no version=3.0.2

Why is the level * ?
 
Why is the level * ?

That's SA's representation of the numeric spam score in X-Spam-Status; it makes it easier to create filters based on a score; if you look for:

X-Spam-Level: ****

you'll catch all mail with a score of four or higher. It's easier for every mail client I've seen than parsing the numeric score.

(Or did you mean why did SA come up with a score of 1.6?)

Andy
 
Let me explain what I understand:

The greater the X-Spam-Level is (more **...) the greater the posibility to chch spam is (even with the risc of detecting as a SPAM the email which are good)

So how can I increase that spam level?

Anyway, my Threshold is 5.0 there in DirectAdmin SA setup page.
 
Well in Redhat 9.0 there are some problems:

I changed the version and stuff and this happens:

The error was:
version.h.pl: version.h.pl: version.h.pl: version.h.pl: version.h.pl: version.h.pl: version.h.pl: Can't locate Digest/SHA1.pm in @INC (@INC contains: ../lib /usr/lib/perl5/5.8.0/i386-linux-thread-multi /usr/lib/perl5/5.8.0 /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.0 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.0 /usr/lib/perl5/vendor_perl .) at ../lib/Mail/SpamAssassin/EvalTests.pm line 33.
BEGIN failed--compilation aborted at ../lib/Mail/SpamAssassin/EvalTests.pm line 33.
Compilation failed in require at ../lib/Mail/SpamAssassin/PerMsgStatus.pm line 56.
BEGIN failed--compilation aborted at ../lib/Mail/SpamAssassin/PerMsgStatus.pm line 56.
Compilation failed in require at ../lib/Mail/SpamAssassin.pm line 74.
BEGIN failed--compilation aborted at ../lib/Mail/SpamAssassin.pm line 74.
Compilation failed in require at version.h.pl line 27.
make: *** [spamc/Makefile] Error 2

Then i tryd it munualy:

[root@xerionhosting Mail-SpamAssassin-3.0.2]# perl Makefile.PL
What email address or URL should be used in the suspected-spam report
text for users who want more information on your filter installation?
(In particular, ISPs should change this to a local Postmaster contact)
default text: [the administrator of that system] [email protected]

Check network rules during 'make test' (test scripts may fail due to
network problems)? (y/n) [n] y

Checking if your kit is complete...
Looks good
Warning: prerequisite Digest::SHA1 0 not found.

Warning: I could not locate your pod2man program. Please make sure,
your pod2man program is in your PATH before you execute 'make'

Writing Makefile for Mail::SpamAssassin
Makefile written by ExtUtils::MakeMaker 6.03
[root@xerionhosting Mail-SpamAssassin-3.0.2]# make
Makefile:95: *** missing separator. Stop.

What could it be?
 
Hi,
I was looking this one and i am not sure, i have a RH9 box with DA and i am still using version 2.64, does anybody knows if i can upgrad to version 3.0.2? Where i can found the best "how to" to do that?

Thanks!!

:D
 
XerionHosting said:
Well in Redhat 9.0 there are some problems:

I changed the version and stuff and this happens:

The error was:
version.h.pl: version.h.pl: version.h.pl: version.h.pl: version.h.pl: version.h.pl: version.h.pl: Can't locate Digest/SHA1.pm in @INC (@INC contains: ../lib /usr/lib/perl5/5.8.0/i386-linux-thread-multi /usr/lib/perl5/5.8.0 /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.0 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.0 /usr/lib/perl5/vendor_perl .) at ../lib/Mail/SpamAssassin/EvalTests.pm line 33.
BEGIN failed--compilation aborted at ../lib/Mail/SpamAssassin/EvalTests.pm line 33.
Compilation failed in require at ../lib/Mail/SpamAssassin/PerMsgStatus.pm line 56.
BEGIN failed--compilation aborted at ../lib/Mail/SpamAssassin/PerMsgStatus.pm line 56.
Compilation failed in require at ../lib/Mail/SpamAssassin.pm line 74.
BEGIN failed--compilation aborted at ../lib/Mail/SpamAssassin.pm line 74.
Compilation failed in require at version.h.pl line 27.
make: *** [spamc/Makefile] Error 2

Then i tryd it munualy:

[root@xerionhosting Mail-SpamAssassin-3.0.2]# perl Makefile.PL
What email address or URL should be used in the suspected-spam report
text for users who want more information on your filter installation?
(In particular, ISPs should change this to a local Postmaster contact)
default text: [the administrator of that system] [email protected]

Check network rules during 'make test' (test scripts may fail due to
network problems)? (y/n) [n] y

Checking if your kit is complete...
Looks good
Warning: prerequisite Digest::SHA1 0 not found.

Warning: I could not locate your pod2man program. Please make sure,
your pod2man program is in your PATH before you execute 'make'

Writing Makefile for Mail::SpamAssassin
Makefile written by ExtUtils::MakeMaker 6.03
[root@xerionhosting Mail-SpamAssassin-3.0.2]# make
Makefile:95: *** missing separator. Stop.

What could it be?

Hi,

Same problem here of FC2. A solution anyone ?

Regards,
Erik
 
Back
Top