[ATrpms-users] Building new MX servers using atrpms

[Michael Mansour]

Hi Jani,

Thanks for your response.

> Very first, start to use smart. It beats yum hands down.

I tried smart about 6 months ago and wasn't too impressed with it's 
features. I have wrapper scripts that I've made which use yum to query 
packages from different repo's I use, and when trying to translate those 
scripts to smart equivalents, smart didn't provide the featureset I needed.

That's not to say smart isn't good, but for my requirements it was still 
immature. I will wait about another year before looking at it again.

> Second, spamassassin won't catch much cheats alone. Very good result 
> you will get if you use amavisd-new what will run spamassassin,
>  clamav and dspam. After teaching a while dspam, it will catch most 
> of the spasm what spamassassing won't catch. And clamav will catch 
> virus mails.

I use MailScanner which does what you describe. I'm only interested in an SA 
upgrade.

> Too bad that there ain't anyone who has made good rpm packet of 
> dspam, so that's what you need to build yourself.

I haven't heard of dspam so not sure exactly how it'll fit into my setup 
(and whether I actually need or can use it), but I'll have a run through a 
little later to see what it's about.

Thanks again for your comments, but it still doesn't really answer my query 
below.

Michael.

> Pelikaista / Mediatraffic Oy
> Jani Partanen
> Battlefield 2 admin
> tel. +358 505 817 817
> e-mail: jiipee at pelikaista.net jiipee at sotapeli.fi
> 
> > -----Original Message-----
> > From: atrpms-users-bounces at atrpms.net [mailto:atrpms-users-
> > bounces at atrpms.net] On Behalf Of Michael Mansour
> > Sent: Wednesday, November 29, 2006 11:30 PM
> > To: atrpms-users at atrpms.net
> > Subject: [ATrpms-users] Building new MX servers using atrpms
> > 
> > Hi,
> > 
> > I'm in the process of building new MX servers.
> > 
> > I'm using SL44 (Scientific Linux 4.4 - RHEL 4 U4 derivative) which
> > contains
> > spamassassin-3.0.6-1.el4, this is quite old so I want to use the latest
> > 3.1.7 from atrpms.
> > 
> > For my older mail servers (still running SL4.4 with atrpms sa 3.1.7) I 
had
> > a
> > couple of issues during the time of release upgrades, and Axel mentioned
> > at
> > the time these issues arose from being "selective" in choosing which
> > packages I install from atrpms and which I don't.
> > 
> > I thought this was the right thing to do at the time, since I'm against
> > clobbering the filesystem and OS with conflicting packages from various
> > repo's. I primarily use Dag for specific packages which don't have
> > dependencies on other packages, Dries for perl packages no other repo 
has,
> > and ATrpms for SA, mutt, DCC, pyzor, razor-agents and yum (for my MX
> > servers
> > mostly).
> > 
> > So my question is, what is the right way to do this?
> > 
> > I build my boxes through kickstart, so after the box is built, do I 
simply
> > do a:
> > 
> > # yum --enablerepo=atrpms -y update spamassassin
> > 
> > and I'll be right? or do I do:
> > 
> > # yum --enablerepo=atrpms -y update
> > 
> > ?? which will go ahead and update every package to what's released from
> > atrpms??
> > 
> > I'm also ok with setting up a mirror of atrpms so I can do this locally
> > when
> > deploying/redploying servers.
> > 
> > Thanks.
> > 
> > Michael.
> > 
> > 
> > _______________________________________________
> > atrpms-users mailing list
> > atrpms-users at atrpms.net
> > http://lists.atrpms.net/mailman/listinfo/atrpms-users
------- End of Original Message -------