partially fix #3979: config: custom.cf: document service restart

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>
This commit is contained in:
Stoiko Ivanov 2024-11-14 16:02:34 +01:00 committed by Thomas Lamprecht
parent 59fbee4e6e
commit 238f9f39e1

View File

@ -778,8 +778,17 @@ Make sure to use the correct {spamassassin_rule_syntax} and test it with:
# spamassassin -D --lint # spamassassin -D --lint
---- ----
If you run a cluster, the `custom.cf` file is synchronized from the The change to the configuration will be picked up when `pmg-smtp-filter` gets
master node to all cluster members automatically. 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 To adjust the score assigned to a particular rule, you
can also use the xref:pmgconfig_spamdetector_customscores[Custom Rule Score] can also use the xref:pmgconfig_spamdetector_customscores[Custom Rule Score]