From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Shannon Sterz <s.sterz@proxmox.com>
Subject: [pve-devel] applied: [PATCH installer] install: set postfix config compatibility level to 3.6 to avoid warning
Date: Tue, 5 Aug 2025 20:13:26 +0200 [thread overview]
Message-ID: <175441760484.3446383.3189643465053858721.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250805095426.91412-1-s.sterz@proxmox.com>
On Tue, 05 Aug 2025 11:54:26 +0200, Shannon Sterz 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
>
>
> [...]
Applied, thanks!
[1/1] install: set postfix config compatibility level to 3.6 to avoid warning
commit: 6bc500651b0b3f3290e73a98ead558c8d57bf75d
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-08-05 18:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-05 9:54 [pve-devel] " Shannon Sterz
2025-08-05 10:58 ` Stoiko Ivanov
2025-08-05 18:13 ` Thomas Lamprecht [this message]
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=175441760484.3446383.3189643465053858721.b4-ty@proxmox.com \
--to=t.lamprecht@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