Hello Victor!
Just by a chance I noticed this email and wanted to add a comment.
04.10.2022 02:52, Viktor Dukhovni wrote:
..
Perhaps you previously had a "backports" package that uses a non-default
release label, and it persisted across the upgrade... You may need to
also look at the configs (I
On Mon, Oct 03, 2022 at 08:43:18PM +, Martin wrote:
> yes, I'm afraid that's true, these are the contents of that old
> directory (I renamed it and put a symbolic link to the sbin directory carrying
> the current executables):
> root@jerakeen:/usr/libexec/postfix/sbin.OLD# find . -type f -prin
Martin:
> HI Wietse,
>
> yes, I'm afraid that's true, these are the contents of that old
> directory
All those binaries have mail_version=3.4.13, therefore none will work
Postfix 3.6 libraries.
> I assume there has been a kind of new configuration between old postfix
> version and the 3.6.4 one.
HI Wietse,
yes, I'm afraid that's true, these are the contents of that old
directory
(I renamed it and put a symbolic link to the sbin directory carrying
the current executables):
root@jerakeen:/usr/libexec/postfix/sbin.OLD# find . -type f -print |
while read file; do echo -n "$file -> "; strin
Am 03.03.2016 um 13:25 schrieb Wietse Venema:
If you don't want those lines to be logged, set the parameter
(relayhost, or whatever it is that needs to be kept), and set
"compatibility_level = 2".
thanks a lot, as I get no compatibility error/warning, I disabled now
the warning by setting the
ginal Message
From: Wietse Venema
Sent: Thursday, March 3, 2016 9:58 AM
To: Postfix users
Reply To: Postfix users
Cc: Wietse Venema; u...@porcupine.org
Subject: Re: Upgrade postfix 2.11 to 3.1
Matthias Fechner:
> Does this mean, I do not have to modify anything in the config?
> Regarding th
Matthias Fechner:
> Does this mean, I do not have to modify anything in the config?
> Regarding the page http://www.postfix.org/COMPATIBILITY_README.html
> postfix would log explicit lines if I have to touch anything.
Wietse:
> If you don't want those lines to be logged, set the parameter
> (relay
1, but the handwriting is on the wall. I gather you just do the upgrade and
see what breaks?
Sent from my BlackBerry 10 smartphone.
Original Message
From: Wietse Venema
Sent: Thursday, March 3, 2016 4:26 AM
To: Postfix users
Reply To: Postfix users
Subject: Re: Upgrade postfix 2.11 to 3.1
Matthias Fechner:
> Does this mean, I do not have to modify anything in the config?
> Regarding the page http://www.postfix.org/COMPATIBILITY_README.html
> postfix would log explicit lines if I have to touch anything.
If you don't want those lines to be logged, set the parameter
(relayhost, or wh
Dear all,
with postfix 3.1 some settings have changed and I'm not sure if I have
to touch my config.
I only see the following messages:
Mar 3 11:51:54 server postfix[75578]: Postfix is running with
backwards-compatible default settings
Mar 3 11:51:54 server postfix[75578]: See
http://www.p
On 31/10/2011 6:07 μμ, Amira Othman wrote:
I am trying to upgrade postfix version form 2.3 to 2.7 but each time I
finish installing rpm I get error
Since you are in CentOS (as you describe in earlier posts), I would
suggest you to follow these *easy* directions and upgrade to 2.8
* Amira Othman :
> Hi all
>
>
>
> I am trying to upgrade postfix version form 2.3 to 2.7 but each time I
> finish installing rpm I get error
>
> smtpd_sasl_auth_enable is true, but SASL support is not compiled in
I guess the version you're updating to has no SA
Am 31.10.2011 17:07, schrieb Amira Othman:
> I am trying to upgrade postfix version form 2.3 to 2.7 but each time I finish
> installing rpm I get error
>
> smtpd_sasl_auth_enable is true, but SASL support is not compiled in
>
> and when I run saslfinger –c I have nothing
Hi all
I am trying to upgrade postfix version form 2.3 to 2.7 but each time I
finish installing rpm I get error
smtpd_sasl_auth_enable is true, but SASL support is not compiled in
and when I run saslfinger -c I have nothing in authentication mechanisms. I
didn't compile rpm by mys
14 matches
Mail list logo
