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 97FA460AEB for ; Tue, 11 Jan 2022 16:39:34 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 8E44F20934 for ; Tue, 11 Jan 2022 16:39:04 +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 id E182420929 for ; Tue, 11 Jan 2022 16:39:02 +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 C269946C48 for ; Tue, 11 Jan 2022 16:30:41 +0100 (CET) From: Dylan Whyte To: pmg-devel@lists.proxmox.com Date: Tue, 11 Jan 2022 16:30:35 +0100 Message-Id: <20220111153035.2628380-1-d.whyte@proxmox.com> X-Mailer: git-send-email 2.30.2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.430 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% 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 URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [custom.cf, postfix.org] Subject: [pmg-devel] [PATCH pmg-docs] pmgconfig: Link to SA rule writing documentation 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: Tue, 11 Jan 2022 15:39:34 -0000 Adds a link to SpamAssassin's rule syntax documentation to the section "Custom SpamAssassin Configuration". Also clarifies that the name of a custom spam score should be the name of the corresponding SpamAssassin rule. --- asciidoc/asciidoc-pmg.conf | 1 + pmgconfig.adoc | 8 ++++---- 2 files changed, 5 insertions(+), 4 deletions(-) diff --git a/asciidoc/asciidoc-pmg.conf b/asciidoc/asciidoc-pmg.conf index 2789e16..a0b998f 100644 --- a/asciidoc/asciidoc-pmg.conf +++ b/asciidoc/asciidoc-pmg.conf @@ -11,6 +11,7 @@ manmanual=Proxmox Mail Gateway Documentation max-width=55em spamassassin=https://spamassassin.apache.org[SpamAssassin(TM)] spamassassin_dnsbl=https://cwiki.apache.org/confluence/display/SPAMASSASSIN/DnsBlocklists[SpamAssassin DNSBL documentation] +spamassassin_rule_syntax=https://cwiki.apache.org/confluence/display/SPAMASSASSIN/writingrules[SpamAssassin rule syntax] postfix=http://www.postfix.org[Postfix] postfix_tls_readme=http://www.postfix.org/TLS_README.html[Postfix TLS Readme] postfix_afterqueue=http://www.postfix.org/FILTER_README.html[Postfix After-Queue Content Filter] diff --git a/pmgconfig.adoc b/pmgconfig.adoc index 8f0826b..b19cbb5 100644 --- a/pmgconfig.adoc +++ b/pmgconfig.adoc @@ -666,7 +666,7 @@ The system logs all the rules which a particular mail hits. Analyzing the logs c lead to finding such a pattern in your environment. You can adjust the score of a rule by creating a new 'Custom Rule Score' entry -in the GUI. +in the GUI and entering a {spamassassin} rule as the name. NOTE: In general, it is strongly recommended not to make large changes to the default scores. @@ -739,9 +739,9 @@ them, as `init.pre`, `v310.pre`, `v320.pre`, `local.cf` will be overwritten by the xref:pmgconfig_template_engine[template engine], while the others can get updated by any {spamassassin} package upgrade. -To add your custom configuration, you have to create a new file and name it -`custom.cf` (in this directory), then add your configuration there. Make sure -to use the correct {spamassassin} syntax, and test it with: +To add your custom configuration, you have to create a new file named +`custom.cf` (in `/etc/mail/spamassassin/`), then add your configuration there. +Make sure to use the correct {spamassassin_rule_syntax} and test it with: ---- # spamassassin -D --lint -- 2.30.2