Date: Thu, 8 Dec 2005 07:07:33 +0000 From: Martin Hepworth <maxsec@gmail.com> To: Vahric MUHTARYAN <vahric@doruk.net.tr> Cc: jdow <jdow@earthlink.net>, freebsd-questions@freebsd.org Subject: Re: hardening FreeBSD for Spamassassin Message-ID: <72cf361e0512072307n338075bcj90946d5087863051@mail.gmail.com> In-Reply-To: <20051207235016.24EE643D81@mx1.FreeBSD.org> References: <040501c5fb84$f4907590$1225a8c0@kittycat> <20051207235016.24EE643D81@mx1.FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <vahric@doruk.net.tr> 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 fro=
m
> 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 serve=
r
> with raid1 and 2 or 4 gb ram .
>
> Thanks again :)
> Vahric
>
> -----Original Message-----
> From: jdow [mailto:jdow@earthlink.net]
> Sent: Thursday, December 08, 2005 1:21 AM
> To: Vahric MUHTARYAN; freebsd-questions@freebsd.org
> Subject: Re: hardening FreeBSD for Spamassassin
>
> From: "Vahric MUHTARYAN" <vahric@doruk.net.tr>
>
> > 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 "
> freebsd-questions-unsubscribe@freebsd.org"
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?72cf361e0512072307n338075bcj90946d5087863051>