From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 47A391FF13B for ; Mon, 08 Jun 2026 13:30:35 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id DBC131A77C; Mon, 8 Jun 2026 13:30:34 +0200 (CEST) From: Stoiko Ivanov To: pmg-devel@lists.proxmox.com Subject: [PATCH pmg-api/pmg-docs/pmg-gui 0/4] tracking-center: make input-base configurable Date: Mon, 8 Jun 2026 13:29:38 +0200 Message-ID: <20260608112952.679449-1-s.ivanov@proxmox.com> X-Mailer: git-send-email 2.47.3 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1780918157019 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.086 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 URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [mailtracker.pm,config.pm] Message-ID-Hash: MS7CXBTF7YMOTE2V2NXBN3SZCHLIMX22 X-Message-ID-Hash: MS7CXBTF7YMOTE2V2NXBN3SZCHLIMX22 X-MailFrom: s.ivanov@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: The recently added input-base parameter for pmg-log-tracker: 9816d19 ("fix #3657: allow scanning a configurable rotated log series") can be used to change the default location the tracking center uses for its logs - but setting it in pmg.conf user can directly benefit from that instead of manually patching MailTracker.pm, or wrapping pmg-log-tracker in a script that changes the input file/input-base. tested by setting the parameter via gui, navigating to the tracking center, and watching execsnopp-bpfcc for the commands which are executed. pmg-api: Stoiko Ivanov (2): config: add log-tracker-base key fix #3657: api: tracking center: explicitly set input base from config src/PMG/API2/MailTracker.pm | 5 +++++ src/PMG/Config.pm | 7 +++++++ 2 files changed, 12 insertions(+) pmg-gui: Stoiko Ivanov (1): fix #2091: system options: add log-tracker-base textrow js/SystemOptions.js | 6 ++++++ 1 file changed, 6 insertions(+) pmg-docs: Stoiko Ivanov (1): pmg-log-tracker: mention that input-base can be configured via GUI pmg-log-tracker.adoc | 3 +++ 1 file changed, 3 insertions(+) Summary over all repositories: 4 files changed, 21 insertions(+), 0 deletions(-) -- Generated by murpp 0.12.0