From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 278D39426F for ; Fri, 9 Feb 2024 13:55:12 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id BFDCB3969A for ; Fri, 9 Feb 2024 13:54:44 +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 ; Fri, 9 Feb 2024 13:54:43 +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 618C646834 for ; Fri, 9 Feb 2024 13:54:43 +0100 (CET) From: Dominik Csapak To: pmg-devel@lists.proxmox.com Date: Fri, 9 Feb 2024 13:54:37 +0100 Message-Id: <20240209125440.2572239-14-d.csapak@proxmox.com> X-Mailer: git-send-email 2.30.2 In-Reply-To: <20240209125440.2572239-1-d.csapak@proxmox.com> References: <20240209125440.2572239-1-d.csapak@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit 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: [pmg-devel] [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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Feb 2024 12:55:12 -0000 this section explains how multiple object categories and multiple objects interact with the rule matching. Signed-off-by: Dominik Csapak --- 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 -- 2.30.2