From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 7F0771FF13C for ; Thu, 11 Jun 2026 13:28:41 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 625FC37D9C; Thu, 11 Jun 2026 13:28:41 +0200 (CEST) Message-ID: <6ca6386f-972e-44dc-981c-2c934a04e811@proxmox.com> Date: Thu, 11 Jun 2026 13:28:07 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Beta Subject: Re: [PATCH pmg-docs] pmgconfig: note pmg-smtp-filter needs restart for custom check script To: Thomas Lamprecht , pmg-devel@lists.proxmox.com References: <20260611093908.1421564-1-d.csapak@proxmox.com> <0f5d0733-a29b-4a5a-9651-8bfef4f0a5f2@proxmox.com> Content-Language: en-US From: Dominik Csapak In-Reply-To: <0f5d0733-a29b-4a5a-9651-8bfef4f0a5f2@proxmox.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1781177239849 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.049 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: XAZRXTBVNUI2PGICGJSJBPUIHYVSMI4V X-Message-ID-Hash: XAZRXTBVNUI2PGICGJSJBPUIHYVSMI4V X-MailFrom: d.csapak@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox Mail Gateway development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On 6/11/26 12:40 PM, Thomas Lamprecht wrote: > On 11/06/2026 11:38, Dominik Csapak wrote: >> It's implied by other parts of the docs, but not explicitely stated, so >> do that to avoid confusion. > > Should we rather handle that automatically too like Stoiko's 'log-headers' > patch? we could, but makes less sense IMO since the user has to be on the cli anyway for putting the script somewhere? if we'd put it on the gui, i'd say yes definitely, but currently it won't gain us much. We'd then have to either * write another note to do 'pmgconfig sync' (maybe with '--restart 1' ?) * or add a new 'pmgconfig set' command to the cli (which would be beneficial in any case i guess) and document that in the docs. > >> >> Signed-off-by: Dominik Csapak >> --- >> pmgconfig.adoc | 7 +++++++ >> 1 file changed, 7 insertions(+) >> >> diff --git a/pmgconfig.adoc b/pmgconfig.adoc >> index 00a988e..34dbecc 100644 >> --- a/pmgconfig.adoc >> +++ b/pmgconfig.adoc >> @@ -1011,6 +1011,13 @@ section: admin >> The location of the custom check executable can also be set there with the key >> `custom_check_path` and defaults to `/usr/local/bin/pmg-custom-check`. >> >> +To enable the changes to the custom check configuration, `pmg-smtp-filter` has >> +to be restarted: >> + >> +---- >> +# systemctl restart pmg-smtp-filter.service >> +---- >> + >> NOTE: The custom check executable runs as the unprivileged >> `pmg-smtp-filter` daemon user. It cannot elevate privileges with tools >> like `sudo`, as the service runs with the systemd `NoNewPrivileges` >