Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email firstname.lastname@example.org
From: Jorey Bump (listjoreybump.com)
Date: Fri Jun 29 2007 - 09:32:01 CDT
Rich Shepard wrote:
> On Thu, 28 Jun 2007, Jorey Bump wrote:
>> I gave up creating SlackBuilds for postfix, as it only seemed to add more
>> work. I find that managing Postfix from source and following the upgrade
>> instructions works very smoothly on Slackware.
> OK. Since postfix is not part of the distribution or frequently upgraded,
> I see how this makes sense. Building the package takes no more time, but
> perhaps the actual upgrades do cause issues that require time to resume.
> So, back to my original question: 2.3.11 or 2.4.3 from 2.3.6? Does it
It's been a while since I made a major leap between versions, so I don't
know if there are any issues upgrading across that size of a gap (I
don't remember any in the past). The INSTALL document doesn't include
any warnings to that effect, it just says 'The non-interactive version
("make upgrade") needs the /etc/postfix/main.cf file from a previous
installation.'. Since you're upgrading from 2.3.x, most of the issues
will be addressed in the release notes. Read them carefully, as they
give specific information on steps needed to address any incompatibilities.
I highly recommend running with the latest stable version. When you've
finished upgrading, you might want to check the postconf(5) man page to
update any directives that have been renamed. It's also worth reviewing
your TLS settings, as a lot of development took place in that area.
The main advantage of using the Postfix upgrade procedure is that it
will run some sanity checks and update your configuration appropriately.
A lot of people get in trouble by just copying their configuration from
a backup of an older version.