From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <pmg-devel-bounces@lists.proxmox.com> Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 248471FF16B for <inbox@lore.proxmox.com>; Thu, 6 Feb 2025 16:17:09 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id DB1612AF28; Thu, 6 Feb 2025 16:17:06 +0100 (CET) From: Friedrich Weber <f.weber@proxmox.com> To: pmg-devel@lists.proxmox.com Date: Thu, 6 Feb 2025 16:16:20 +0100 Message-Id: <20250206151620.32482-1-f.weber@proxmox.com> X-Mailer: git-send-email 2.39.5 MIME-Version: 1.0 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.003 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 RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pmg-devel] [PATCH pmg-docs] pmg-mail-filter: clarify matching of Who objects 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> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pmg-devel-bounces@lists.proxmox.com Sender: "pmg-devel" <pmg-devel-bounces@lists.proxmox.com> In particular, explain that Who objects match against Envelope From and Envelope To, not the From: and To: mail headers. This is occasionally a source of confusion in enterprise support. Signed-off-by: Friedrich Weber <f.weber@proxmox.com> --- pmg-mail-filter.adoc | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/pmg-mail-filter.adoc b/pmg-mail-filter.adoc index 235f156..65d28b6 100644 --- a/pmg-mail-filter.adoc +++ b/pmg-mail-filter.adoc @@ -265,6 +265,16 @@ We have two important 'Who' objects called 'Blacklist' and 'Whitelist'. These are used in the default ruleset to globally block or allow specific senders. +Note that 'Who' objects match against the mail addresses given during the SMTP +dialog: + +* 'Who' objects in the 'FROM' category match against the mail address given in + the `MAIL FROM` command (the Envelope From). +* 'Who' objects in the 'TO' category match against the mail address given in + the `MAIL TO` command (the Envelope To). + +If you want to match against the `From:` or `To:` header fields of the mail, +use a 'What' object with type 'Match Field' instead. [[pmg_mailfilter_what]] 'What' objects -- 2.39.5 _______________________________________________ pmg-devel mailing list pmg-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pmg-devel