From: Stoiko Ivanov <s.ivanov@proxmox.com>
To: pmg-devel@lists.proxmox.com
Subject: [PATCH pmg-api] config: do not shortcircuit smtp-welcomelist generation
Date: Tue, 9 Jun 2026 10:58:44 +0200 [thread overview]
Message-ID: <20260609085851.828503-1-s.ivanov@proxmox.com> (raw)
combining the results with ||= causes the write_smtp_welcomelist calls
not to be run, after the first one signals a change.
gather the combined changes in a different variable, to ensure each
config-file is actually created/written, as postfix refuses to run if
its config files are missing.
Fixes: de0ba685 ("fix #3991: record changes to the smtp-welcomelist and reload postfix")
Reported-by: Dominik Csapak <d.csapak@proxmox.com>
Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
---
src/PMG/Config.pm | 13 +++++++++----
1 file changed, 9 insertions(+), 4 deletions(-)
diff --git a/src/PMG/Config.pm b/src/PMG/Config.pm
index 2d2b6c83..ddbabe7e 100644
--- a/src/PMG/Config.pm
+++ b/src/PMG/Config.pm
@@ -1878,10 +1878,15 @@ sub rewrite_postfix_welcomelist {
}
my $changes = 0;
- $changes ||= $write_smtp_welcomelist->("/etc/postfix/senderaccess", $fromlist);
- $changes ||= $write_smtp_welcomelist->("/etc/postfix/rcptaccess", $tolist);
- $changes ||= $write_smtp_welcomelist->("/etc/postfix/clientaccess", $clientlist);
- $changes ||= $write_smtp_welcomelist->("/etc/postfix/postscreen_access", $clientlist, 'permit');
+ my $ret;
+ $ret = $write_smtp_welcomelist->("/etc/postfix/senderaccess", $fromlist);
+ $changes ||= $ret;
+ $ret = $write_smtp_welcomelist->("/etc/postfix/rcptaccess", $tolist);
+ $changes ||= $ret;
+ $ret ||= $write_smtp_welcomelist->("/etc/postfix/clientaccess", $clientlist);
+ $changes ||= $ret;
+ $ret ||= $write_smtp_welcomelist->("/etc/postfix/postscreen_access", $clientlist, 'permit');
+ $changes ||= $ret;
return $changes;
}
--
2.47.3
reply other threads:[~2026-06-09 8:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260609085851.828503-1-s.ivanov@proxmox.com \
--to=s.ivanov@proxmox.com \
--cc=pmg-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.