On Tue, Nov 02, 2010 at 01:21:03PM -0400, Linux Addict wrote:

> >> > No. Do an upgrade. If installing from source:
> >> >
> >> >       Read the RELEASE_NOTES file for 2.6 and 2.7, then:
> >> >
> >> >       % make
> >> >       % su root
> >> >       # postfix stop
> >> >       # make upgrade
> >> >       # postfix start
> >> >
> >> > If installing from a well constructed package:
> >> >
> >> >       Read the RELEASE_NOTES file for 2.6 and 2.7, then:
> >> >
> >> >       # postfix stop
> >> >       # some-command-to-install-updated-package
> >> >       # postfix start
> >> >
> >> > In either case, save the updated main.cf and master.cf files that
> >> > are automatically upgraded as part of the install process.
> >> >
> >> > If the package is not well constructed:
> >> >
> >> >       Read the RELEASE_NOTES file for 2.6 and 2.7, then:
> >> >
> >> >       # postfix stop
> >> >
> >> >       # mkdir -p /etc/postfix/cfsavedir
> >> >       # cp /etc/postfix/main.cf /etc/postfix/master.cf \
> >> >               /etc/postfix/cfsavedir/
> >> >
> >> >       # some-command-to-install-updated-poorly-constructed-package
> >> >
> >> >       # cp /etc/postfix/cfsavedir/main.cf /etc/postfix/cfsavedir/
> >> master.cf \
> >> >               /etc/postfix/
> >> >       # postfix set-permissions upgrade-configuration
> >> >
> >> >       # postfix start
> >> >
> >> > A package is not well contstructed if it fails to preserve and upgrade
> >> > your existing main.cf and master.cf files.
> 
> Sorry about beating the dead horse, but just came to know that there are few
> 2.2 postfix instances which needs to upgraded to 2.7  as well. Does upgrade
> stands true for 2.2 to 2.7 or install a clean 2.7 and just port the postconf
> -n will suffice?

The same instructions apply, only now you have additional sets of
RELEASE_NOTES files to read. Everything from 2.3-2.7.

Do NOT use old main.cf/master.cf files unmodified with new Postfix
releases. The "postfix upgrade-configuration" command upgrades your
main.cf and master.cf files.

Note that 2.2 did not have a "data_directory". So you may need 
to move some volatile state files and change their ownership.
See the RELEASE_NOTES.

-- 
        Viktor.

Reply via email to