Re: hardening FreeBSD for Spamassassin
jdow wrote: From: Alex Zbyslaw [EMAIL PROTECTED] jdow wrote: http://www.surl.org/. You mean http://www.surbl.org/ The other URL works but isn't very useful :-) I did indeed mess up and leave out the b. Mea culpa. I should add thanks for the interesting post and useful information. For someone like me, without the time to keep up with all the latest trends in spam killing it's nice to be fed these tidbits every now and again. --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: hardening FreeBSD for Spamassassin
On Thu, Dec 08, 2005 at 01:56:52AM +0200, Vahric MUHTARYAN wrote: And I want to handle 130,000 mail/hour with using 2 or 4 P4 server with raid1 and 2 or 4 gb ram . Try pf + spamd (the FreeBSD port of the OpenBSD app) to cut out as much mail as possible before it hits spamassassin. m ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: hardening FreeBSD for Spamassassin
From: Vahric MUHTARYAN [EMAIL PROTECTED]
Hi Everybody ,
I think too many people know too many appliance choosing freebsd
for OS, also they are hardening FreeBSD and specialize for they works .
Anybody know or Did this like hardening on FreeBSD for getting better
performans, I'm using FreeBSD closer 2 year I didn't see any problem about
performans but is there any hint for hardening FreeBSD , I know some tuning
paramters have but I talking about different thing . You know spam programs
CPU intersive , I searched on google and I saw many hardening title but
their point is security not performans .
I think you are referring to tuning rather than hardening. A rough
interpretation of hardening with respect to speed would mean
making the machine work more. That would make it run slower. {^_-}
If you mean tuning to get more performance out of SpamAssassin I'd
need to get some basics handled first. What version of SpamAssassin
are you running? How are you using it? (Are you using spamc/spamd?
Are you using one of the milters that daemonizes spamassassin itself
without using spamc and spamd?) If you are using spamc and spamd
what are the parameters you use for each and what tool calls spamc?
(I use procmail on that other 'x OS at the moment, for example.)
Are you using per user preferences, rules, and Bayes or are you using
system wide via SQL? And so forth. If you are using spamc/spamd then
tuning is direct via the commands to spamd as you daemonize it. For
this the spamassassin user's mailing list is quite helpful. It is
the user's list at spamassassin.apache.org. If you are using some
other tool or milter you might need to deal with that tool's support
groups for the best help.
If you have DNS tests available make sure these tests are not
blocked and are not timing out. spamassassin -t -D testfile
with some handy email test file can give an informative readout
in this regard.
Be aware that spamassassin can use a lot of memory. And it is a bit of
a resource hog if you run a lot of the SpamAssassin Rules Emporium
rule sets. (Search for SARE or the full name. Their rule sets are
VERY useful.) Of course, you get into a tradeoff situation between
resource usage and the quality of the spam detection. I'm silly enough
to run about 40 or so rule sets with per user rules, per user Bayes,
and all that, a pretty much worst case setup on a 2 GHz Athlon with
1 gigabyte of memory. It takes about 3.4 clock seconds to run a single
test using spamc/spamd. Using spamassassin itself adds the overhead of
starting perl and all that. This takes about 5.3 seconds total. Since
the machine is otherwise very lightly loaded this is no big deal for
about 1300 emails processed per day on about 6 user accounts.
And to wrap up this rather long message I'll note that very often the
easiest SpamAssassin tuneup for speed involves adding more memory. If
SpamAssassin finds itself swapping for any reason it gets REALLY slow.
And I do note I am not quite running stock out of the box SpamAssassin.
I do not use automatic anything with it. Loren and I have carefully
trained SpamAssassin manually and get excellent results. And since Loren
is one of the SARE ninjas he needed some special tweaks inside SA that
really should not affect its performance except out at the fifth
decimal place. I mention this in the interests of truth in advertising
as it were.
So if you are not stuck within AmavisD or something like that the SA
user's list may be a big help. Otherwise speak with the AmavisD folks.
And do make sure you have plenty of ram and reasonable expectations for
your particular machine speeds. SA needs memory and CPU cycles.
{^_^} Joanne
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: hardening FreeBSD for Spamassassin
Thanks Joanne ,
Exactly I red Spamassassin FAQ and they said that 20-30 MB memory
must for each child process also iowait and CPU is really important but
mailn purpose is RAM, you are right ...
And sorry I heared but I did not use exactly spamc spamd , also I
will care about your words and advise about mailing list , but my questions
is not fully How fast can I run SA , my question is get out something from
FreeBSD which is not need for only SA run on system, I mean optimizing
system for only special works , maybe more little kernel , maybe it looks
like freebsd from screch (I think wrong word )...or maybe How can I
optimize and have more small and faster running FreeBSD OS ...
And I want to handle 130,000 mail/hour with using 2 or 4 P4 server
with raid1 and 2 or 4 gb ram .
Thanks again :)
Vahric
-Original Message-
From: jdow [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 08, 2005 1:21 AM
To: Vahric MUHTARYAN; freebsd-questions@freebsd.org
Subject: Re: hardening FreeBSD for Spamassassin
From: Vahric MUHTARYAN [EMAIL PROTECTED]
Hi Everybody ,
I think too many people know too many appliance choosing
freebsd
for OS, also they are hardening FreeBSD and specialize for they works .
Anybody know or Did this like hardening on FreeBSD for getting better
performans, I'm using FreeBSD closer 2 year I didn't see any problem about
performans but is there any hint for hardening FreeBSD , I know some
tuning
paramters have but I talking about different thing . You know spam
programs
CPU intersive , I searched on google and I saw many hardening title but
their point is security not performans .
I think you are referring to tuning rather than hardening. A rough
interpretation of hardening with respect to speed would mean
making the machine work more. That would make it run slower. {^_-}
If you mean tuning to get more performance out of SpamAssassin I'd
need to get some basics handled first. What version of SpamAssassin
are you running? How are you using it? (Are you using spamc/spamd?
Are you using one of the milters that daemonizes spamassassin itself
without using spamc and spamd?) If you are using spamc and spamd
what are the parameters you use for each and what tool calls spamc?
(I use procmail on that other 'x OS at the moment, for example.)
Are you using per user preferences, rules, and Bayes or are you using
system wide via SQL? And so forth. If you are using spamc/spamd then
tuning is direct via the commands to spamd as you daemonize it. For
this the spamassassin user's mailing list is quite helpful. It is
the user's list at spamassassin.apache.org. If you are using some
other tool or milter you might need to deal with that tool's support
groups for the best help.
If you have DNS tests available make sure these tests are not
blocked and are not timing out. spamassassin -t -D testfile
with some handy email test file can give an informative readout
in this regard.
Be aware that spamassassin can use a lot of memory. And it is a bit of
a resource hog if you run a lot of the SpamAssassin Rules Emporium
rule sets. (Search for SARE or the full name. Their rule sets are
VERY useful.) Of course, you get into a tradeoff situation between
resource usage and the quality of the spam detection. I'm silly enough
to run about 40 or so rule sets with per user rules, per user Bayes,
and all that, a pretty much worst case setup on a 2 GHz Athlon with
1 gigabyte of memory. It takes about 3.4 clock seconds to run a single
test using spamc/spamd. Using spamassassin itself adds the overhead of
starting perl and all that. This takes about 5.3 seconds total. Since
the machine is otherwise very lightly loaded this is no big deal for
about 1300 emails processed per day on about 6 user accounts.
And to wrap up this rather long message I'll note that very often the
easiest SpamAssassin tuneup for speed involves adding more memory. If
SpamAssassin finds itself swapping for any reason it gets REALLY slow.
And I do note I am not quite running stock out of the box SpamAssassin.
I do not use automatic anything with it. Loren and I have carefully
trained SpamAssassin manually and get excellent results. And since Loren
is one of the SARE ninjas he needed some special tweaks inside SA that
really should not affect its performance except out at the fifth
decimal place. I mention this in the interests of truth in advertising
as it were.
So if you are not stuck within AmavisD or something like that the SA
user's list may be a big help. Otherwise speak with the AmavisD folks.
And do make sure you have plenty of ram and reasonable expectations for
your particular machine speeds. SA needs memory and CPU cycles.
{^_^} Joanne
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: hardening FreeBSD for Spamassassin
You are going to have to trim numbers of messages before you get to
SpamAssassin, I am afraid. Is this number after any greylisting you
may have operational? If not then do look into greylisting. It is a
very powerful technique to prefilter your incoming email at the
connection level. If the address is recognize the email is received
immediately. If it is not recognized the email is temporarily failed.
Currently spammers do not retry in such cases. So at least for now this
will be a very effective tool to trim down the number of messages your
SpamAssassin install has to filter.
You will have to trim the number of rule sets you use to a bare
minimum. They do take time to run. If I extrapolate my system's
usage and configuration to a 4 processor 3GHz level machine I am
still about an order of magnitude shy of your requirements as I
am currently configured. So the level of rules trimming would be
daunting indeed. (But at least I have not missed a genuine spam
detection in two weeks now. And I've only had about 5 very spammy
looking kernel mailing list type messages that false alarmed. It
is hard to deal with filtering lists that just look like spam and
do not filter incoming messages. {^_-})
As for trimming FreeBSD to a minimum the usual litanies exist, do
not start any services you do not need. One BIG hog in this regard,
obviously, is X11. If it is not absolutely needed don't start it.
You should not even have it on the system. Only you know if nfs
is required in your setup or not, of course. So you must make the
assessment of is this needed for yourself. With four gigabytes
of ram and (only) four processors you're probably not memory
limited on a CPU intensive operation. So kernel trimming is
probably not going to be a high benefit process, at a guess.
Oh yes, one thing you DO want to run is your own DNS server
implementation of the SURBL lists. That volume of email quite
justifies requesting Jeff allow you to download his database to
your machine periodically. That will GREATLY speed up the DNS
tests, of course. You might check this out at http://www.surl.org/.
Jeff's a good fellow with a STRONG no collateral damage ethic.
Go for greylisting first then Jeff's database downloads.
{^_^}
- Original Message -
From: Vahric MUHTARYAN [EMAIL PROTECTED]
Thanks Joanne ,
Exactly I red Spamassassin FAQ and they said that 20-30 MB memory
must for each child process also iowait and CPU is really important but
mailn purpose is RAM, you are right ...
And sorry I heared but I did not use exactly spamc spamd , also I
will care about your words and advise about mailing list , but my questions
is not fully How fast can I run SA , my question is get out something from
FreeBSD which is not need for only SA run on system, I mean optimizing
system for only special works , maybe more little kernel , maybe it looks
like freebsd from screch (I think wrong word )...or maybe How can I
optimize and have more small and faster running FreeBSD OS ...
And I want to handle 130,000 mail/hour with using 2 or 4 P4 server
with raid1 and 2 or 4 gb ram .
Thanks again :)
Vahric
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: hardening FreeBSD for Spamassassin
From: Alex Zbyslaw [EMAIL PROTECTED]
jdow wrote:
http://www.surl.org/.
You mean http://www.surbl.org/
The other URL works but isn't very useful :-)
I did indeed mess up and leave out the b. Mea culpa.
{^_^}
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: hardening FreeBSD for Spamassassin
That's quite alot of messages to shift - you don;'t mention message size
either.
BUT you'll local caches of any URI-RBLs you want to use. A local DCC server.
I'd ask on the spamassassin users list, but you prob looking at multiple
machines just for the scanning never mind the local zone files etc (will
also help with down time issues).
---
Martin
On 12/7/05, Vahric MUHTARYAN [EMAIL PROTECTED] wrote:
Thanks Joanne ,
Exactly I red Spamassassin FAQ and they said that 20-30 MB memory
must for each child process also iowait and CPU is really important but
mailn purpose is RAM, you are right ...
And sorry I heared but I did not use exactly spamc spamd , also
I
will care about your words and advise about mailing list , but my
questions
is not fully How fast can I run SA , my question is get out something from
FreeBSD which is not need for only SA run on system, I mean optimizing
system for only special works , maybe more little kernel , maybe it looks
like freebsd from screch (I think wrong word )...or maybe How can I
optimize and have more small and faster running FreeBSD OS ...
And I want to handle 130,000 mail/hour with using 2 or 4 P4 server
with raid1 and 2 or 4 gb ram .
Thanks again :)
Vahric
-Original Message-
From: jdow [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 08, 2005 1:21 AM
To: Vahric MUHTARYAN; freebsd-questions@freebsd.org
Subject: Re: hardening FreeBSD for Spamassassin
From: Vahric MUHTARYAN [EMAIL PROTECTED]
Hi Everybody ,
I think too many people know too many appliance choosing
freebsd
for OS, also they are hardening FreeBSD and specialize for they works .
Anybody know or Did this like hardening on FreeBSD for getting better
performans, I'm using FreeBSD closer 2 year I didn't see any problem
about
performans but is there any hint for hardening FreeBSD , I know some
tuning
paramters have but I talking about different thing . You know spam
programs
CPU intersive , I searched on google and I saw many hardening title but
their point is security not performans .
I think you are referring to tuning rather than hardening. A rough
interpretation of hardening with respect to speed would mean
making the machine work more. That would make it run slower. {^_-}
If you mean tuning to get more performance out of SpamAssassin I'd
need to get some basics handled first. What version of SpamAssassin
are you running? How are you using it? (Are you using spamc/spamd?
Are you using one of the milters that daemonizes spamassassin itself
without using spamc and spamd?) If you are using spamc and spamd
what are the parameters you use for each and what tool calls spamc?
(I use procmail on that other 'x OS at the moment, for example.)
Are you using per user preferences, rules, and Bayes or are you using
system wide via SQL? And so forth. If you are using spamc/spamd then
tuning is direct via the commands to spamd as you daemonize it. For
this the spamassassin user's mailing list is quite helpful. It is
the user's list at spamassassin.apache.org. If you are using some
other tool or milter you might need to deal with that tool's support
groups for the best help.
If you have DNS tests available make sure these tests are not
blocked and are not timing out. spamassassin -t -D testfile
with some handy email test file can give an informative readout
in this regard.
Be aware that spamassassin can use a lot of memory. And it is a bit of
a resource hog if you run a lot of the SpamAssassin Rules Emporium
rule sets. (Search for SARE or the full name. Their rule sets are
VERY useful.) Of course, you get into a tradeoff situation between
resource usage and the quality of the spam detection. I'm silly enough
to run about 40 or so rule sets with per user rules, per user Bayes,
and all that, a pretty much worst case setup on a 2 GHz Athlon with
1 gigabyte of memory. It takes about 3.4 clock seconds to run a single
test using spamc/spamd. Using spamassassin itself adds the overhead of
starting perl and all that. This takes about 5.3 seconds total. Since
the machine is otherwise very lightly loaded this is no big deal for
about 1300 emails processed per day on about 6 user accounts.
And to wrap up this rather long message I'll note that very often the
easiest SpamAssassin tuneup for speed involves adding more memory. If
SpamAssassin finds itself swapping for any reason it gets REALLY slow.
And I do note I am not quite running stock out of the box SpamAssassin.
I do not use automatic anything with it. Loren and I have carefully
trained SpamAssassin manually and get excellent results. And since Loren
is one of the SARE ninjas he needed some special tweaks inside SA that
really should not affect its performance except out at the fifth
decimal place. I mention this in the interests of truth in advertising
as it were.
So if you are not stuck within AmavisD or something like
