From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Jonas Theisen <j.theisen@proxmox.com>
Subject: Re: applied: [PATCH pve-manager v2] api: nodes: dns: restart postfix after changing name servers
Date: Tue, 10 Nov 2026 20:22:46 +0100 [thread overview]
Message-ID: <93ffabec-33e5-4899-9f20-95ec832194b9@proxmox.com> (raw)
In-Reply-To: <179433798766.1308914.125002100282336285.b4-ty@b4>
Am 10.11.26 um 20:16 schrieb Thomas Lamprecht:
> On Tue, 10 Nov 2026 10:31:57 +0100, Jonas Theisen wrote:
>> Postfix runs its SMTP client in a chroot and copies /etc/resolv.conf
>> into it only when the instance starts. A running postfix therefore
>> keeps using the old name servers after a DNS settings change,
>> which can make mail delivery fail until the next restart.
>>
>> Use try-restart on postfix.service after writing the new settings, so
>> postfix is only restarted if it is running.
>> A failed restart only warns, since the DNS settings were already
>> written.
>>
>> [...]
>
> Applied, thanks!
>
> [1/1] api: nodes: dns: restart postfix after changing name servers
> https://git.proxmox.com/?p=pve-manager.git;a=commitdiff;h=47df03e04a471b9041f5217dbe887d9ee890ac0b
what I forgot to mention:
I dropped the patch changelog from the commit message, that doesn't belong
in the permanent git history, it's rather relevant for development and
review of a series – else series with lots of churn and double digits would
consist mostly of changelogs from unrelated versions. If you place these in
the diff-stat section, i.e below "---" like
```
---
changes since v1:
...
PVE/API2/Nodes.pm | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/PVE/API2/Nodes.pm b/PVE/API2/Nodes.pm
```
It will be visible on list but ignored by git on apply.
As I was touching this anyway I also merged "nodes dns" into one tag
(the idea is to have a rough subsystem like tag not a direct mapping
of the file or api path with s!/!:! applied) and used a Link trailer
for the forum link – again, only because I touched the commit message
anyway, else I would not had bothered, these are tiny and partially
subjective nits.
prev parent reply other threads:[~2026-11-10 19:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 9:31 [PATCH pve-manager v2] api: nodes: dns: restart postfix after changing name servers Jonas Theisen
2026-11-10 19:13 ` applied: " Thomas Lamprecht
2026-11-10 19:22 ` 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=93ffabec-33e5-4899-9f20-95ec832194b9@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=j.theisen@proxmox.com \
--cc=pve-devel@lists.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