Hi,
I have been performance testing with amavisd-new and -lite and SA 2.61 and
perl 5.6.1 on a FreeBSD 5.1 platform before replacing some production
servers. Using postal to generate test traffic, the best performance I
have been able to obtain is ~325msgs/mins with a 3ghz p4, 1gb ram box
On Wed, 24 Dec 2003, Wendel, Jesse wrote:
Okay - well, I followed your suggestion and gave it a shot.
Below is the entire /etc/rc.d/init.d/spamassassin file as
modified - SPAMDOPTIONS=-d -c -a -m5 -H -i 0.0.0.0 -
after which I restarted the service.
It still isn't working.
Try
I'd like to try some of the custom rules sets such as bigevil but not
commit them to /etc/mail/spamassassin until I've tested them personally.
Must I copy all the files into ~/.spamassassin/user_prefs, or can I drop
them into ~/.spamassassin as I would with the system-wide
At Thu Dec 25 20:41:28 2003, Kenneth Porter wrote:
I'd like to try some of the custom rules sets such as bigevil but not
commit them to /etc/mail/spamassassin until I've tested them personally.
Must I copy all the files into ~/.spamassassin/user_prefs, or can I drop
them into
--On Thursday, December 25, 2003 9:41 PM + Martin Radford
[EMAIL PROTECTED] wrote:
The only configuration file that is read in ~/.spamassassin is
user_prefs.
Is there some directive one can put in user_prefs to include another
file, so that I don't need to dump all the different rule sets
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday 25 December 2003 12:41, Kenneth Porter wrote:
I'd like to try some of the custom rules sets such as bigevil but not
commit them to /etc/mail/spamassassin until I've tested them personally.
Must I copy all the files into
I got a spam today where the X-Originating-IP header wasn't a number. Hotmail
always puts the dotted quad in the header.
I wrote a rule to match this - I hope it's useful.
header XORIG_IP_NOT_NUMBER X-Originating-IP !~ /\[[\d\.]*]/
describe XORIG_IP_NOT_NUMBERThe X-Originating-IP
--On Thursday, December 25, 2003 7:01 PM -0800 Douglas Kirkland
[EMAIL PROTECTED] wrote:
My understanding is that put the bigevil rule set into user_prefs will
not work. The only way I know how to test the rule set is to setup a
test server and try it. The rule set will have to be put the
