On Sun, Sep 25, 2011 at 9:46 AM, Reindl Harald <h.rei...@thelounge.net> wrote: > > > Am 25.09.2011 17:51, schrieb John Hinton: >> On 9/25/2011 10:56 AM, /dev/rob0 wrote: >>> On Sunday 25 September 2011 07:27:59 Phill Edwards wrote: >>>>> Where did you look? A source install of Postfix using default >>>>> paths places an /etc/postfix/aliases file. >>>> I installed from CentOS RPMs. The version I have is >>>> postfix-2.3.3-2.3.el5_6. >>> FYI that version was EOL in 2009. >> Note that CentOS is a clone of RedHat. Redhat has always has the motto of >> staying with base version numbering for >> packages contained in the original release... or at least when possible. >> They then 'backport' all security fixes >> to these old numbered versions. Why? Well, after running RedHat based >> servers for a bit over 15 years, I can >> count on one hand the number of times updates broke something. Config files >> don't change, or if they do, they are >> written as filename.rpmnew and you are warned. Rarely do you have to do >> anything about these. > > all correct > > but that means that recent documentations and howtos for complexer setups > are useless for RHEL/CentOS if you are not using a recent build what > is done in few minutes in the case of postfix > > i have not seen any problem upgrading postfix in the last 5 years > on a lot of machines and with the complexest configurations you > can imagine
+1. Anyone running RedHat/CentOS really should consider upgrading to the latest Postfix. This procedure has been tested personally by me and performed at least hundreds (maybe thousands?) of times, based on the traffic to the article: http://stevejenkins.com/blog/2011/01/building-postfix-2-8-on-rhel5-centos-5-from-source/ It's targeted directly at users running Postfix 2.3 on RedHat/CentOS who want to upgrade to Postfix 2.8. Nothing will break. It just works. SteveJ
