Got this report this morning from all 3 of my spamassassin servers, all
running 3.0
Is this ruleset no longer supported for 3.0?
===
Lint output: warning: description for SARE_URI_GEOCIT_NUM is over 50 chars
lint: 1 issues detected. please rerun with debug enabled for more
inform
For those of you running large sites ( we have about 12,000 users, with
210,000 messages a day) what do you have for a bayes_expiry_max_db_size?
Also is there any way to see the count of spam and ham messages that are in
the bayes database, I can't seem to find any info on that. I want to make
s
We are moving from mailscanner to amavisd-new because of lots more
flexibility. Currently we are running sendmail to amavisd-new to sendmail to
dbmail, is working great processing about 120,000 messages a day broke out
over 2 servers and a database server for dbmail. Initially we had some
hang-ups
Amavisd-new launches spamassasin in perl form rather then use spamd.
The fedora core machines running amavisd-new are both 2.4 dual xeons with
4gb of memory
Amavisd-new virus scanning and spam scanning with spamassasin is using about
18% cpu, and for everything we have about 1.8gb of memory in us
will also probably install Maia Mailguard after the patch for the new
amavisd-new becomes available. This will allow us to quarantine items and
allow each one of our users to view any quarantine items and have them
delivered to their inbox if they really want them.
Andrew Ott
-Original Message
