SpamAssassin 3.1.6 released

Thanks,
3.1.6 includes a large number of bug fixes and documentation updates.
Here is an abbreviated changelog (since 3.1.5) for major updates (see
the Changes file for a complete list):

- bug 4940: fixes to bug in date handling affecting DATE_IN_FUTURE_*
and DATE_IN_PAST_* rules when more than one Resent-Date header is
present
- bug 5044: include local site config in sa-update lint checks
- bug 5081: fix race condition in spamd preforking code that sometimes
left one child process running after SIGHUPing spamd
- bug 5076: unescape hash characters in the config
- bug 5077: fix false SPF_SOFTFAIL's when SPF queries timeout
- bug 5080: update RCVD_ILLEGAL_IP evaltest to properly deal with 127/8
- bug 5089: enable adding headers with single digit zero value
- bug 5098: add support for ecelerity Received headers
- bug 5101: fix a bug, introduced in 3.1.5, in mbx code
- bug 5105: M::SA::Client doesn't always catch failed connection to
spamd, fixed
Click to expand...


Wael
 
Guys,

I have uptaded the new version. But how can i check that my SpamAssassin works?

When i check the email ( source) i see this:

Received: from mail by server2.powerdomein.nl with spam-scanned (Exim 4.63)
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on
server2.powerdomein.nl
X-Spam-Level:
X-Spam-Status: No, score=-0.4 required=10.0 tests=AWL,BAYES_00,
FORGED_RCVD_HELO,HTML_FONT_LOW_CONTRAST,HTML_MESSAGE,MIME_HTML_ONLY,
NO_REAL_NAME autolearn=no version=3.1.0

Can some tell me how to use 3.1.17?
 
edit the file spam.sh in /usr/local/directadmin/scripts/

just the version
and after type ./spam.sh in the same directory
 
I did... I download first the tar.gz file and dan run the script.

The script installed some files..

This is what i get:
Writing Makefile for IO::Socket::SSL
Manifying blib/man3/IO::Socket::SSL.3pm
Manifying blib/man3/IO::Socket::SSL.3pm
Writing /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi/auto/IO/Socket/SSL/.packlist
Appending installation info to /usr/lib/perl5/5.8.5/i386-linux-thread-multi/perllocal.pod
File already exists: Mail-SpamAssassin-3.1.17.tar.gz

gzip: stdin: unexpected end of file
tar: Child returned status 1
tar: Error exit delayed from previous errors
chown: cannot access `Mail-SpamAssassin-3.1.17': No such file or directory
./spam.sh: line 132: cd: /usr/local/directadmin/scripts/packages/Mail-SpamAssassin-3.1.17: No such file or directory
Can't open perl script "Makefile.PL": No such file or directory.
Use -S to search $PATH for it.
make: *** No targets specified and no makefile found. Stop.
make: *** No rule to make target `install'. Stop.
 
ok try this :

cd /usr/local/directadmin/scripts/packages/

rm -rf Mail-SpamAssassin-3.1.7*

wget http://apache.mirrors.northco.net/spamassassin/source/Mail-SpamAssassin-3.1.7.tar.gz

after it type it :

cd /usr/local/directadmin/scripts/

and

pico spam.sh

and change the version to VERSION=3.1.7
(after it quit and save)

and type :

./spam.sh

and

service exim restart when its gone..
 
Last edited:
SpamAssassin Upgrade Problems

I just followed the instructions to upgrade to the latest version of SpamAssassin and now some of my users are getting mail bounced back with the following message...

Code: 
An error was detected while processing a file of BSMTP input.
The error message was:

  421 Lost incoming connection

The SMTP transaction started in line 0.
The error was detected in line 4.
0 previous messages were successfully processed.
The rest of the batch was abandoned.
421 Lost incoming connection
Transaction started in line 0
Error detected in line 4

Also, I see that spamd seems to be going crazy, using as much as 80% of my cpu at times.

This problem never occured until performing this upgrade. Has anyone else had this problem and if so what did you do to resolve it?

Thanks in advance.

Roark Holz
 
have you tried to install it via cpan, the easiest way ?

# cpan
cpan> install Mail::SpamAssassin
quit
#

notice some old files can cause problem in
/etc/mail/spamassassin
and
/usr/share/spamassassin

you can delete them before updating
(sample for redhat system)
 
Thanks, for now I have just commented out the spamassassin lines in exim.conf, restarted exim and killed all of the spamd processes.

Not a fix as I no longer have spamassassin but better than valid emails getting rejected.

I hope that the above is all I need to do to truly disable spamassassin.

I'll have to test this more later as I have to leave.

Thanks again.

If anyone else has any other ideas I'd still love to hear them.
 
I have had this very same problem now for a year, i can NOT figure out what is causing this.
 
If you search these forums for BSMTP you'll see that lots of folk have reported this problem. You'll probably also see where I feel it may just be a problem where spamd is being overwhelmed.

You should also find a post from the past day or two where someone appears to have solved the problem and I've asked for more details.

Jeff
 
Thanks, I read up on that (I had disabled SA since last march and hadn't had time to look at it). I went ahead and followed those instructions in regards to removing the v310.pre file to see if that makes an affect. So fari nthe last few hours of having SA upgrades/on and having Exim 4.63 installed, I haven't received any BSMTP errors.... yet.
 
Did you have a later version of the file? And if so, did you leave it?

Please keep us posted.

Thanks.

Jeff
 
I saw a v310.pre and v312.pre files. Before installing SpamAssasin 3.1.7, I went in and cleaned out EVERYTHING from the /etc/mail/spamassassin directory. Then I installed/compiled SpamAssassin 3.1.7 per the DA ./spam.sh script file. Afterwards I noticed that both the v310 and v312 were back in that folder. I simply removed the v310.pre file, added a few new rulesets from SARE, and did the --lint command.

So far in 12 hours, not a single BSMTP 421 error. I took the risk of running this on my main server with business clients, and they all are reporting working email this morning.
 
You must log in or register to reply here.
Back
Top