Hello all, About a year ago I set up a mail server on CentOS using this howto: http://wanderingbarque.com/howtos/mailserver/mailserver.html I managed to add amavisd-new with clamav and spamassassin. It runs very well, but it runs on CentOS 5.2, and if I try to upgrade, amavisd-new and clamav break. we are now also at the point where a backup mx will need to be implemented. If necessary I am willing to implement a new mail server and a new backup mx. What I would like to know is what solution you guys would recommend for the mail server and the backup MX? Any pointers would be greatly appreciated. Regards, Coert
I use Mailscanner with postfix and Mailwatch to manage quarantine etc; http://mailscanner.info/ On the backup MX, I just use postfix and some basic anti-spam stuff. Very little gets through and even less gets through to the primary. I am aware that some spam techniques go straight to the backup MX because most people don't set it up quite as well as the primary. YMMV. I also used to use greylisting, which does reduce spam, but, unfortunately it also reduces valid mail ;-) In the end I'd rather suffer a few spams getting through compared to the delayed receipt of important emails. Brian. On Mon, May 10, 2010 at 9:01 PM, Coert <lgroups at waagmeester.co.za> wrote:> Hello all, > > About a year ago I set up a mail server on CentOS using this howto: > http://wanderingbarque.com/howtos/mailserver/mailserver.html > I managed to add amavisd-new with clamav and spamassassin. > It runs very well, but it runs on CentOS 5.2, and if I try to upgrade, > amavisd-new and clamav break. > we are now also at the point where a backup mx will need to be implemented. > > If necessary I am willing to implement a new mail server and a new > backup mx. > > What I would like to know is what solution you guys would recommend for > the mail server and the backup MX? > > Any pointers would be greatly appreciated. > > Regards, > Coert > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20100510/212950b9/attachment-0001.html>
On 5/10/2010 8:02 AM, Brian McKerr wrote:> I use Mailscanner with postfix and Mailwatch to manage quarantine etc; > > http://mailscanner.info/ > > On the backup MX, I just use postfix and some basic anti-spam stuff. > Very little gets through and even less gets through to the primary. I > am aware that some spam techniques go straight to the backup MX > because most people don't set it up quite as well as the primary. YMMV. > > I also used to use greylisting, which does reduce spam, but, > unfortunately it also reduces valid mail ;-) In the end I'd rather > suffer a few spams getting through compared to the delayed receipt of > important emails. > > Brian.Another vote here for Mailscanner + Postfix. Add a few RBL's into your postfix config and spam will be at a minimum. -- Ryan Manikowski ]] Devision Media Services LLC [[ www.devision.us ryan at devision.us | 716.771.2282
Coert wrote:> Hello all, > > About a year ago I set up a mail server on CentOS using this howto: > http://wanderingbarque.com/howtos/mailserver/mailserver.html > I managed to add amavisd-new with clamav and spamassassin. > It runs very well, but it runs on CentOS 5.2, and if I try to upgrade, > amavisd-new and clamav break. > we are now also at the point where a backup mx will need to be implemented. > > If necessary I am willing to implement a new mail server and a new > backup mx. > > What I would like to know is what solution you guys would recommend for > the mail server and the backup MX? > > Any pointers would be greatly appreciated. > > Regards, > CoertI would follow the CentOS Wiki HowTo docs for Postfix, which are currently maintained for CentOS 5: http://wiki.centos.org/HowTos#head-0facb50d5796bee0bd394636c32ffa9a997a6ab5 http://wiki.centos.org/HowTos/postfix http://wiki.centos.org/HowTos/Amavisd If things break, report it and I'll fix the documentation. I'm running that setup so I do tend to notice when things break. I've recently updated to the latest amavisd-new, clamav and spamassassin - all largely without issue but I would always advise you read the release notes and track their respective mailing lists for potential issues.
Am 10.05.2010 14:02, schrieb Brian McKerr:> I use Mailscanner with postfix and Mailwatch to manage quarantine etc; > > http://mailscanner.info/I don't intend to start a flamewar, but given Wieste's repeated warnings on the Postfix mailinglist[1] and expressed on http://www.postfix.org/addon.html as "mailscanner system, works with Postfix and other MTAs. WARNING: This software uses unsupported methods to manipulate Postfix queue files directly. This will result in corruption or loss of mail. The mailscanner authors have sofar refused to discuss a proper access API or protocol." I call that combination not being best practice. Regards Alexander [1] http://readlist.com/lists/postfix.org/postfix-users/7/36311.html
Am 10.05.10 13:01, schrieb Coert:> Hello all, > > About a year ago I set up a mail server on CentOS using this howto: > http://wanderingbarque.com/howtos/mailserver/mailserver.html > I managed to add amavisd-new with clamav and spamassassin. > It runs very well, but it runs on CentOS 5.2, and if I try to upgrade, > amavisd-new and clamav break.Oh please don't say what happens. If you use amavisd-new and clamav from rpmforge (or from epel), they don't break when updating. And please don't tell me you ran clamav non-updated since CentOS 5.2 - it had several security issues since then. Ralph
Been using sendmail-clamav-mimedefang-greylist combo for years and have never had a problem. Standard package: sendmail-devel-8.13.8-2.el5 sendmail-cf-8.13.8-2.el5 sendmail-doc-8.13.8-2.el5 sendmail-8.13.8-2.el5>From rpmforge:mimedefang.2.68-1.el5 clamd-0.96-2.el5 clamav-0.96-2.el5 clamav-milter-0.96-2.el5 milter-greylist.3.0-2.el5 The important settings to get this to work: sendmail.mc: INPUT_MAIL_FILTER(`greylist', `S=local:/var/milter-greylist/milter-greylist.sock, F=T, T=S:3m;R:3m') INPUT_MAIL_FILTER(`mimedefang', `S=unix:/var/spool/MIMEDefang/mimedefang.sock, F=T, T=S:3m;R:3m') INPUT_MAIL_FILTER(`clamav',`S=local:/var/clamav/clamav_milter.sock, F=T, T=S:4m;R:4m')dnl clamav-milter.conf: MilterSocket unix:/var/clamav/clamav_milter.sock clamd.conf: LocalSocket /var/clamav/clamd_local.sock /etc/rc.d/init.d/mimedefang: SPOOLDIR='/var/spool/MIMEDefang' SOCKET=${SOCKET:=$SPOOLDIR/$prog.sock} /etc/mail/greylist.conf: socket "/var/milter-greylist/milter-greylist.sock" As for the secondary MX (on a different host) running the same OS just copy ALL the config, its that easy. However, on the PRIMARY host you need to make sure that the SECONDARY MX has access to hand over mail. Jobst On Mon, May 10, 2010 at 01:01:13PM +0200, Coert (lgroups at waagmeester.co.za) wrote:> Hello all, > > About a year ago I set up a mail server on CentOS using this howto: > http://wanderingbarque.com/howtos/mailserver/mailserver.html > I managed to add amavisd-new with clamav and spamassassin. > It runs very well, but it runs on CentOS 5.2, and if I try to upgrade, > amavisd-new and clamav break. > we are now also at the point where a backup mx will need to be implemented. > > If necessary I am willing to implement a new mail server and a new > backup mx. > > What I would like to know is what solution you guys would recommend for > the mail server and the backup MX? > > Any pointers would be greatly appreciated. > > Regards, > Coert > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos-- When the Pope visits a country he really likes, does he french kiss the ground????????? | |0| | Jobst Schmalenbach, jobst at barrett.com.au, General Manager | | |0| Barrett Consulting Group P/L & The Meditation Room P/L |0|0|0| +61 3 9532 7677, POBox 277, Caulfield South, 3162, Australia
>-----Original Message----- >If necessary I am willing to implement a new mail server and a new >backup mx. > >What I would like to know is what solution you guys would >recommend for >the mail server and the backup MX? > >Any pointers would be greatly appreciated. >Running a backup or secondary MX at this point is largely a waste of time. The only thing a backup MX gets you is an increase in spam. Most MTAs will retry sending every couple of hours. So if your MX is down for a while, it's not really a big issue. I run a cluster of sendmail servers (at MX 0) with spamassassin and clamav, and it works quite well. Provides redundnacy and scalability, without the nonsense of a backup mx. The last "backup" MX I ran was probably retired at least two years ago, and even then it was well past pointless and irrelevant. Cheers, Dan
On Monday, May 10, 2010 07:01 PM, Coert wrote:> Hello all, > > About a year ago I set up a mail server on CentOS using this howto: > http://wanderingbarque.com/howtos/mailserver/mailserver.html > I managed to add amavisd-new with clamav and spamassassin. > It runs very well, but it runs on CentOS 5.2, and if I try to upgrade, > amavisd-new and clamav break. > we are now also at the point where a backup mx will need to be implemented.I run postfix with clamd and spamd 'plugged in' via milter. Amavis is a dog. Mind you, I repackage more recent versions of postfix and I have to likewise do the milters for clamav and spamassassin.> > If necessary I am willing to implement a new mail server and a new > backup mx. > > What I would like to know is what solution you guys would recommend for > the mail server and the backup MX?'Backup mx' should always have access at least to the same user address table that the primary uses. Or just run two identical mx's with the same priority.