From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <d.csapak@proxmox.com> Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 298F0BB897 for <pmg-devel@lists.proxmox.com>; Mon, 18 Dec 2023 14:34:15 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 12D041BF16 for <pmg-devel@lists.proxmox.com>; Mon, 18 Dec 2023 14:34:15 +0100 (CET) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for <pmg-devel@lists.proxmox.com>; Mon, 18 Dec 2023 14:34:14 +0100 (CET) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id D15A3480D1; Mon, 18 Dec 2023 14:34:13 +0100 (CET) Message-ID: <d81be6eb-733f-48bc-add3-efd20cfb5af0@proxmox.com> Date: Mon, 18 Dec 2023 14:34:13 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Beta Content-Language: en-US To: Stoiko Ivanov <s.ivanov@proxmox.com> Cc: pmg-devel@lists.proxmox.com References: <20230630082748.1875726-1-d.csapak@proxmox.com> <ZXyCY2sdhuJznlOv@rosa.proxmox.com> <ZXyHfI7O1PnuX3bz@rosa.proxmox.com> From: Dominik Csapak <d.csapak@proxmox.com> In-Reply-To: <ZXyHfI7O1PnuX3bz@rosa.proxmox.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.020 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 T_SCC_BODY_TEXT_LINE -0.01 - Subject: Re: [pmg-devel] [PATCH pmg-api v2 1/2] fix #4811: rule db: test regex validity on save X-BeenThere: pmg-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox Mail Gateway development discussion <pmg-devel.lists.proxmox.com> List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pmg-devel>, <mailto:pmg-devel-request@lists.proxmox.com?subject=unsubscribe> List-Archive: <http://lists.proxmox.com/pipermail/pmg-devel/> List-Post: <mailto:pmg-devel@lists.proxmox.com> List-Help: <mailto:pmg-devel-request@lists.proxmox.com?subject=help> List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pmg-devel>, <mailto:pmg-devel-request@lists.proxmox.com?subject=subscribe> X-List-Received-Date: Mon, 18 Dec 2023 13:34:15 -0000 On 12/15/23 18:06, Stoiko Ivanov wrote: > After testing this a bit more I realized that anchored regexes, don't die > on '^*foo$' (the quite common case of mistaking regex for globs (especially > for filenames) - the warning is printed to the journal - but I can happily > store it (additionally the eval-block in the what/who_match never dies - > and the 'invalid regex:' does not get printed. > > maybe we could improve this even further by die'ing upon a warning when > saving the regex? - then the question is if we want to add the eval+warning > code in the who/what_match subs at all (afaict this would only add 'invalid > regex:' to the same log-line. can we check if the regex match warns though? how would we do that? > > In any case - thanks for the patch - I never took the time to find out why > some invalid-regexes cause pmg-smtp-filter to exit+respawn, and some others > don't ;) > > > On Fri, Dec 15, 2023 at 05:44:19PM +0100, Stoiko Ivanov wrote: >> Thanks for the patch, this definitely improves UX! >> >> one tiny nit in-line (I'll gladly change that upon applying directly, but >> just don't want to miss anything): >> ..snip..