On Mon, May 2, 2011 at 2:39 PM, Ned Slider <n...@unixmail.co.uk> wrote: > There was a (Red Hat/CentOS) security update to Postfix issued almost 3 > months after the upstream release of 5.6: > > https://rhn.redhat.com/errata/RHSA-2011-0422.html > > However, because CentOS were slow with the release of 5.6, the base update > from 5.5 to 5.6, and subsequent errata to 5.6 were all rolled out > simultaneously, including the Postfix update.
Ah, yep! That would explain it! > To exclude postfix updates, you'd need to add the exclude line to both the > [base] and [updates] sections of your /etc/yum.repos.d/CentOS-Base.repo > config file. From your description I'd guess you've perhaps only excluded > postfix from [base] and not [updates]. I actually didn't have it in either - I was under the (apparently false) impression that just putting the exclude in yum.conf would apply to any repo. It's in the CentOS-Base.repo file in [base] and [updates] now, tho. Thank you. :) > Looking at the install scripts run from the Postfix RPM package in CentOS, > looks like it's reset itself as the default Postfix install as you've > surmised. > > Running 'rpm -q postfix' would confirm if the latest Postfix RPM package > slipped through your net during the 5.6 update. Yep! % rpm -q postfix postfix-2.3.3-2.2.el5_6 Thanks for the excellent detective work, Ned. :) SteveJ
