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 [212.224.123.68])
by lore.proxmox.com (Postfix) with ESMTPS id 480651FF16B
for <inbox@lore.proxmox.com>; Thu, 14 Nov 2024 16:03:21 +0100 (CET)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
by firstgate.proxmox.com (Proxmox) with ESMTP id 30AFC335D9;
Thu, 14 Nov 2024 16:03:23 +0100 (CET)
From: Stoiko Ivanov <s.ivanov@proxmox.com>
To: pmg-devel@lists.proxmox.com
Date: Thu, 14 Nov 2024 16:02:34 +0100
Message-Id: <20241114150234.31256-1-s.ivanov@proxmox.com>
X-Mailer: git-send-email 2.39.5
MIME-Version: 1.0
X-SPAM-LEVEL: Spam detection results: 0
AWL 0.072 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] partially fix #3979: config:
custom.cf: document service restart
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>
creating custom spamassassin configuration might be an advanced topic,
but documenting the needed steps in PMG should let users focus more on
the rules than finding out what else needs to be done.
only partially fixes the request, I still don't think that adding
an edit window for custom.cf to the GUI makes sense, and adding
custom.cf as template (to automatically pick up changes faster/on
pmgconfig sync), seems not really fitting.
Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
---
I remebered seeing the bugzilla entry recently, while skimming over a thread
in the forum with (different) issues with custom.cf. Thought I'll document
this right away before trying to remember if/how this is handled the next
time a similar request comes up.
pmgconfig.adoc | 13 +++++++++++--
1 file changed, 11 insertions(+), 2 deletions(-)
diff --git a/pmgconfig.adoc b/pmgconfig.adoc
index a9377c5..a932a50 100644
--- a/pmgconfig.adoc
+++ b/pmgconfig.adoc
@@ -778,8 +778,17 @@ Make sure to use the correct {spamassassin_rule_syntax} and test it with:
# spamassassin -D --lint
----
-If you run a cluster, the `custom.cf` file is synchronized from the
-master node to all cluster members automatically.
+The change to the configuration will be picked up when `pmg-smtp-filter` gets
+restarted. To directly have it enabled you need to restart manually, after
+editing the custom configuration:
+
+----
+# systemctl restart pmg-smtp-filter.service
+----
+
+If you run a cluster, the `custom.cf` file is synchronized from the master node
+to all cluster members and the relevant services are restarted automatically on
+the cluster members.
To adjust the score assigned to a particular rule, you
can also use the xref:pmgconfig_spamdetector_customscores[Custom Rule Score]
--
2.39.5
_______________________________________________
pmg-devel mailing list
pmg-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pmg-devel