Mailinglist Archive: opensuse (2271 mails)
| < Previous | Next > |
Re: [SLE] Two spamasssassin issues
- From: Mark Crean <mcrean@xxxxxxxxxxxxxx>
- Date: Mon, 12 Apr 2004 21:34:08 +0100
- Message-id: <407AFD40.8010505@xxxxxxxxxxxxxx>
John Andersen wrote:
[snip]
>>Is there a way to make an rpm out of this - I'd like to keep the rpm
>> database happy.
>
>Not that I know of, because the CPAN install is totally automated.
>On the other hand, there is no reason to keep rpm aware of the
>change if you never install with rpm in the first place.
Dunno if this will help anyone:
First, it's easy to upgrade spamassassin using rpm. Download the source tar.gz for the latest version (2.63), then use the spec file from the 2.60 src.rpm on SuSE ftp (or the original one on the install disks) and alter a few things, like the version name. Building against this spec file produces the two rpms (spamassassin 2.63 and perl-spamassassin 2.63).
Second, to improve the spam-catching rate, I'd had to install a bunch of custom rules.cf files from the spamassassin sites. It doesn't take spammers long to work out ways round the current version of spamassassin, and then the hit rate starts to go down.
Some of the third-party rule sets are very effective at dealing with the latest tricks. With the custom rules and a few of my own, my hit rate is now up there at nearly 100% again. I've never used razor because the addition of custom rules seems to have plugged the gap.
Never had a problem with bayes db here. It's always worked.
Just my 2 cents.
:)
Fish
[snip]
>>Is there a way to make an rpm out of this - I'd like to keep the rpm
>> database happy.
>
>Not that I know of, because the CPAN install is totally automated.
>On the other hand, there is no reason to keep rpm aware of the
>change if you never install with rpm in the first place.
Dunno if this will help anyone:
First, it's easy to upgrade spamassassin using rpm. Download the source tar.gz for the latest version (2.63), then use the spec file from the 2.60 src.rpm on SuSE ftp (or the original one on the install disks) and alter a few things, like the version name. Building against this spec file produces the two rpms (spamassassin 2.63 and perl-spamassassin 2.63).
Second, to improve the spam-catching rate, I'd had to install a bunch of custom rules.cf files from the spamassassin sites. It doesn't take spammers long to work out ways round the current version of spamassassin, and then the hit rate starts to go down.
Some of the third-party rule sets are very effective at dealing with the latest tricks. With the custom rules and a few of my own, my hit rate is now up there at nearly 100% again. I've never used razor because the addition of custom rules seems to have plugged the gap.
Never had a problem with bayes db here. It's always worked.
Just my 2 cents.
:)
Fish
| < Previous | Next > |