[pmg-devel] [PATCH pmg-docs] partially fix #3979: config: custom.cf: document service restart

[Stoiko Ivanov]

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 at 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