..
I intend to upgrade Postfix version 2.5.5 to 2.7.1.
Are there incompatibilities or specific path for upgrade ?
Or any manual re-configuration to be done ?
..
This server is a Debian Lenny and upgrade will be done via the Debian
lenny-backports
repository usage wich included Postfix v2.7.1
On 01/12/2010, at 23:40, Stan Hoeppner wrote:
> Victor Duchovni put forth on 12/1/2010 3:41 PM:
>> It would be unwise of LaMont or Debian, having selected a particular
>> Postfix 2.x release (say 2.7) to not track the patch updates from time to
>> time. I understand that Debian stable or backports
Victor Duchovni put forth on 12/1/2010 3:41 PM:
> On Wed, Dec 01, 2010 at 03:11:12PM -0600, Stan Hoeppner wrote:
>
>> Victor Duchovni put forth on 12/1/2010 2:28 PM:
>>> On Wed, Dec 01, 2010 at 09:19:52PM +0100, Bruno Costacurta wrote:
>>>
>>>> I intend
On Wed, Dec 01, 2010 at 03:11:12PM -0600, Stan Hoeppner wrote:
> Victor Duchovni put forth on 12/1/2010 2:28 PM:
> > On Wed, Dec 01, 2010 at 09:19:52PM +0100, Bruno Costacurta wrote:
> >
> >> I intend to upgrade Postfix version 2.5.5 to 2.7.1.
> >
> > May a
Victor Duchovni put forth on 12/1/2010 2:28 PM:
> On Wed, Dec 01, 2010 at 09:19:52PM +0100, Bruno Costacurta wrote:
>
>> I intend to upgrade Postfix version 2.5.5 to 2.7.1.
>
> May as well use 2.7.2.
The OP sticks to Debian Stable and Backports packages Viktor, as I do.
We&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 01.12.2010 21:49, Stan Hoeppner a écrit :
> Bruno Costacurta put forth on 12/1/2010 2:19 PM:
>> Hello,
>>
>> I intend to upgrade Postfix version 2.5.5 to 2.7.1.
>> Are there incompatibilities or specific path for up
Bruno Costacurta put forth on 12/1/2010 2:19 PM:
> Hello,
>
> I intend to upgrade Postfix version 2.5.5 to 2.7.1.
> Are there incompatibilities or specific path for upgrade ?
> Or any manual re-configuration to be done ?
I performed this exact backports upgrade about a week ag
On Wed, Dec 01, 2010 at 09:19:52PM +0100, Bruno Costacurta wrote:
> I intend to upgrade Postfix version 2.5.5 to 2.7.1.
May as well use 2.7.2.
> Are there incompatibilities or specific path for upgrade ?
The Postfix 2.7 source code includes:
RELEASE_NOTES
RELEASE_NOT
Hello,
I intend to upgrade Postfix version 2.5.5 to 2.7.1.
Are there incompatibilities or specific path for upgrade ?
Or any manual re-configuration to be done ?
At the end of this email I posted my postconf -n
Thanks for info.
* note :
I know the famous "if it is not broken, do not f
On 07/29/2010 05:07 PM, donovan jeffrey j wrote:
Jul 29 10:20:08 mx2 postfix/smtpd[63722]: connect from
mail2.beth.k12.pa.us[192.227.0.10]
Jul 29 10:20:08 mx2 postfix/smtpd[63722]: 15B7551C06DA:
client=mail2.beth.k12.pa.us[192.227.0.10]
Jul 29 10:20:08 mx2 postfix/cleanup[63726]: 15B7551C06DA:
donovan jeffrey j:
> thanks for the reply, i did the update and have no errors on postfix check.
>
> i have setup a test on my mx server to transport mail for
> lukeskywal...@beth.k12.pa.us to mx2.beth.k12.pa.us ( my new 10.6 filter )
>
> so far my mail2 primary mx can send to the filter (mx2).
On Jul 29, 2010, at 9:33 AM, Wietse Venema wrote:
> donovan jeffrey j:
>>
>> On Jul 29, 2010, at 7:16 AM, Wietse Venema wrote:
>>
>>> The simplest way to upgrade an existing configuration is:
>>>
>>> - Back up the new main.cf, master.cf, postfix-files, postfix-script
>>> and post-install files
donovan jeffrey j:
>
> On Jul 29, 2010, at 7:16 AM, Wietse Venema wrote:
>
> > The simplest way to upgrade an existing configuration is:
> >
> > - Back up the new main.cf, master.cf, postfix-files, postfix-script
> > and post-install files.
> >
> > - Install the old main.cf and old master.cf an
On Jul 29, 2010, at 7:16 AM, Wietse Venema wrote:
> The simplest way to upgrade an existing configuration is:
>
> - Back up the new main.cf, master.cf, postfix-files, postfix-script
> and post-install files.
>
> - Install the old main.cf and old master.cf and any files that
> you have added to
donovan jeffrey j:
> version 2.5.5,
>
> greetings
> im upgrading a couple of xserves to 10.6 from 10.4. the main.cf
> used to be pretty straight forward. The default main.cf on 10.6
> snow leopard server has overwhelmed my old eyeballs. may new lines
> most i understand but
version 2.5.5,
greetings
im upgrading a couple of xserves to 10.6 from 10.4. the main.cf used to be
pretty straight forward. The default main.cf on 10.6 snow leopard server has
overwhelmed my old eyeballs. may new lines most i understand but they pretty
much list every option known to man
Scott Haneda:
> On May 23, 2009, at 5:10 PM, Wietse Venema wrote:
>
> > Scott Haneda:
> >> I have a test server about ready to become a live server, version
> >> 2.5.5. Is it correct that prior to the 2.6 release, that 2.5.7 would
> >> be the latest I wan
Scott Haneda wrote:
> Thank you Wietse. One point of clarification please. If 2.5.7 has
> defect back ports from 2.6, then that equates to new features brought
> into 2.5.7?
Wietse said:
"Postfix 2.5.7 has 'defect fixes' back-ported from Postfix 2.6.0."
[Emphasis added] Note that he says "de
On May 23, 2009, at 5:10 PM, Wietse Venema wrote:
Scott Haneda:
I have a test server about ready to become a live server, version
2.5.5. Is it correct that prior to the 2.6 release, that 2.5.7 would
be the latest I want to run?
Unlike other products, you are not expected to stop using
Scott Haneda:
> I have a test server about ready to become a live server, version
> 2.5.5. Is it correct that prior to the 2.6 release, that 2.5.7 would
> be the latest I want to run?
Unlike other products, you are not expected to stop using Postfix
version X when Postfix versi
I have a test server about ready to become a live server, version
2.5.5. Is it correct that prior to the 2.6 release, that 2.5.7 would
be the latest I want to run?
I see http://www.postfix.org/announcements/postfix-2.5.7.html shows
what I would call minor issues for the 2.5.7 release set
21 matches
Mail list logo
