From: Stoiko Ivanov <s.ivanov@proxmox.com>
To: Shannon Sterz <s.sterz@proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH installer] install: set postfix config compatibility level to 3.6 to avoid warning
Date: Tue, 5 Aug 2025 12:58:32 +0200 [thread overview]
Message-ID: <20250805125832.1a35de75@rosa.proxmox.com> (raw)
In-Reply-To: <20250805095426.91412-1-s.sterz@proxmox.com>
Thanks for taking a look at this!
Put shortly don't see anything that should break with the updated
compatibility_level for all our products apart from PMG (see below):
Reviewed-by: Stoiko Ivanov <s.ivanov@proxmox.com>
For PMG it should work fine as well (mostly as a note to self for the
upcoming PMG 9.0): I quickly checked our use of the affected
config-options in the PMG config templates - and the only things that
might cause issues with PMG were:
* respectful_logging=yes (because of the log-tracker, but that seems a
non-issue from a quick grep there, and if not we need to fix it up there
anyways)
* xxx_security_level (client-side TLS) - currently this would change the
behavior of the TLS Settings - but if this should be problematic for any
deployment (where they need to actively disable outbound opportunistic
TLS) - I'd rather adapt our config with a new setting to explicitly
disable it.
On Tue, 5 Aug 2025 11:54:26 +0200
Shannon Sterz <s.sterz@proxmox.com> wrote:
> otherwise postfix will complain about using a backward compatible
> config. since we don't seem to use anything that would be problematic
> here anyway [1], just bump the version to avoid spamming the logs.
>
> [1]: https://www.postfix.org/COMPATIBILITY_README.html
>
> Signed-off-by: Shannon Sterz <s.sterz@proxmox.com>
> ---
>
> tested this on two nodes by adapting the config there and running
> `postfix reload`. setting this to 3.6 meant no more warnings, going back
> down to 2 would warn again.
>
> Proxmox/Install.pm | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Proxmox/Install.pm b/Proxmox/Install.pm
> index 3159dcc..f40d20d 100644
> --- a/Proxmox/Install.pm
> +++ b/Proxmox/Install.pm
> @@ -42,7 +42,7 @@ mynetworks = 127.0.0.0/8
> inet_interfaces = loopback-only
> recipient_delimiter = +
>
> -compatibility_level = 2
> +compatibility_level = 3.6
>
> _EOD
>
> --
> 2.47.2
>
>
>
> _______________________________________________
> pve-devel mailing list
> pve-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>
>
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-08-05 10:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-05 9:54 Shannon Sterz
2025-08-05 10:58 ` Stoiko Ivanov [this message]
2025-08-05 18:13 ` [pve-devel] applied: " Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250805125832.1a35de75@rosa.proxmox.com \
--to=s.ivanov@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.sterz@proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox