[ATrpms-users] Building new MX servers using atrpms

Jani Partanen jiipee at sotapeli.fi
Wed Nov 29 22:48:11 CET 2006


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

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.

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


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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: jiipee at pelikaista.net.vcf
Type: text/x-vcard
Size: 564 bytes
Desc: not available
Url : http://lists.atrpms.net/pipermail/atrpms-users/attachments/20061129/97deaebd/attachment.vcf 


More information about the atrpms-users mailing list