From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <s.ivanov@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 CFE0293A0B for <pmg-devel@lists.proxmox.com>; Tue, 20 Feb 2024 15:47:52 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id B99549B69 for <pmg-devel@lists.proxmox.com>; Tue, 20 Feb 2024 15:47:52 +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>; Tue, 20 Feb 2024 15:47:52 +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 0489F43FC3 for <pmg-devel@lists.proxmox.com>; Tue, 20 Feb 2024 15:47:52 +0100 (CET) Date: Tue, 20 Feb 2024 15:47:51 +0100 From: Stoiko Ivanov <s.ivanov@proxmox.com> To: Dominik Csapak <d.csapak@proxmox.com> Cc: pmg-devel@lists.proxmox.com Message-ID: <20240220154751.4d259298@rosa.proxmox.com> In-Reply-To: <20240209125440.2572239-14-d.csapak@proxmox.com> References: <20240209125440.2572239-1-d.csapak@proxmox.com> <20240209125440.2572239-14-d.csapak@proxmox.com> X-Mailer: Claws Mail 4.1.1 (GTK 3.24.38; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.084 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: [pmg-devel] applied: [PATCH pmg-docs 1/2] rule system: add a small section about matching rules 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: Tue, 20 Feb 2024 14:47:52 -0000 Thanks for the patch! applied! On Fri, 9 Feb 2024 13:54:37 +0100 Dominik Csapak <d.csapak@proxmox.com> wrote: > this section explains how multiple object categories and multiple > objects interact with the rule matching. > > Signed-off-by: Dominik Csapak <d.csapak@proxmox.com> > --- > pmg-mail-filter.adoc | 17 +++++++++++++++++ > 1 file changed, 17 insertions(+) > > diff --git a/pmg-mail-filter.adoc b/pmg-mail-filter.adoc > index 3aafe4c..57b8a15 100644 > --- a/pmg-mail-filter.adoc > +++ b/pmg-mail-filter.adoc > @@ -58,6 +58,23 @@ You can also disable a rule completely, which is mostly useful for > testing and debugging. The 'Factory Defaults' button allows you to > reset the filter rules. > > +Application of Rules > +-------------------- > + > +When there is more than one object category or multiple objects configured > +within a single rule, the following logic is used to determine if the rule > +should be applied: > + > +* Within one category (WHAT/FROM/TO/WHEN), all objects are logical-or linked, > + meaning that only one object of any one object group from the same category > + has to match for the whole category to match. > + > +* FROM/TO/WHAT/WHEN category match results are logical-and linked, so all > + categories that have at least one object in them must match for the rule to > + match. > + > +When these conditions are met, all configured actions are executed. > + > > [[pmg_mailfilter_action]] > 'Action' - objects