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 DD63D1FF13B for ; Wed, 03 Jun 2026 01:45:18 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 56DB01F6C3; Wed, 3 Jun 2026 01:45:18 +0200 (CEST) From: Thomas Lamprecht To: pmg-devel@lists.proxmox.com, Stoiko Ivanov Subject: applied: [PATCH pmg-api v3] fix #7407: cluster: report: increase maximal filesize to 4M Date: Wed, 3 Jun 2026 01:44:32 +0200 Message-ID: <178044386992.1710282.10866247529872677879.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260316121712.30273-1-s.ivanov@proxmox.com> References: <20260316121712.30273-1-s.ivanov@proxmox.com> 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: 1780443848231 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.005 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: S325VIUQCCISOEGJJKS76PRPVJDMDYJP X-Message-ID-Hash: S325VIUQCCISOEGJJKS76PRPVJDMDYJP X-MailFrom: t.lamprecht@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 Mon, 16 Mar 2026 13:16:27 +0100, Stoiko Ivanov wrote: > the postfix configuration files are read via PVE::INotify in our > stack and have no implicit limit. > > PMG::Cluster and PMG::Report do read the same file's contents using > `file_get_contents` with a limit (explicitly set, or implicit) of 1M. > > This causes the cluster-sync to fail in one reported deployment > hosting ~40k domains, with explicit transport entries and comments > (resulting in a 1.4M /etc/pmg/transport). > > [...] Applied, thanks! [1/1] fix #7407: cluster: report: increase maximal filesize to 4M commit: 69a62d286498cee24765d6bcdd3939534e224118