add 'pmg-scores.cf' to config file section

[pmg-docs.git] / pmgconfig.adoc

diff --git a/pmgconfig.adoc b/pmgconfig.adoc
index 620401881b8c8380e7520902049740fc6d9237ae..9ccd97827e4b4423c5ff56e4594ed5abe339e7a7 100644 (file)
--- a/pmgconfig.adoc
+++ b/pmgconfig.adoc
@@ -73,6 +73,10 @@ The cluster setup.
 
 The list of relay domains.
 
+`/etc/pmg/dkim/domains`::
+
+The list of domains for outbound DKIM signing.
+
 `/etc/pmg/fetchmailrc`::
 
 Fetchmail configuration (POP3 and IMAP setup).
@@ -105,6 +109,9 @@ GUI user configuration.
 
 Custom {spamassassin} setup.
 
+`/etc/mail/spamassassin/pmg-scores.cf`::
+
+Custom {spamassassin} rule scores.
 
 Keys and Certificates
 ---------------------
@@ -129,6 +136,10 @@ Internally used to generate CSRF tokens.
 
 Key and certificate (combined) to encrypt mail traffic (TLS).
 
+`/etc/pmg/dkim/<selector>.private`::
+
+Key for DKIM signing mails with selector '<selector>'.
+
 
 Service Configuration Templates
 -------------------------------
@@ -403,7 +414,7 @@ Controls whether outbound mail should get DKIM signed.
 Selector::
 
 The selector used for signing the mail. The private key used for signing is
-saved under `/etc/pmg/yourselector.private`. You can display the DNS TXT
+saved under `/etc/pmg/dkim/yourselector.private`. You can display the DNS TXT
 record which you need to add to all domains signed by {pmg} by clicking on the
 'View DNS Record' Button.
 
@@ -529,22 +540,29 @@ include::pmg.virusquar-conf-opts.adoc[]
 Custom SpamAssassin configuration
 ---------------------------------
 
-This is only for advanced users. To add or change the Proxmox
-{spamassassin} configuration please login to the console via SSH. Go
-to directory `/etc/mail/spamassassin/`. In this directory there are several
-files (`init.pre`, `local.cf`, ...) – do not change them.
+This is only for advanced users. {spamassassin}'s rules and their associated
+scores get updated regularly and are trained on a huge corpus, which gets
+classified by experts. In most cases adding a rule for matching a particular
+keyword is the wrong approach, leading to many false positives. Usually bad
+detection rates are better addressed by properly setting up DNS than by adding
+a custom rule - watch out for matches to 'URIBL_BLOCKED' in the logs or
+spam-headers - see the {spamassassin_dnsbl}.
+
+To add or change the Proxmox {spamassassin} configuration please login to the
+console via SSH. Change to the `/etc/mail/spamassassin/` directory. In this
+directory there are several files (`init.pre`, `local.cf`, ...) - do not change
+them, as they will be overwritten by any {spamassassin} rule update.
 
-To add your special configuration, you have to create a new file and
-name it `custom.cf` (in this directory), then add your
-configuration there. Be aware to use the {spamassassin}
-syntax, and test with
+To add your special 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 with
 
 ----
 # spamassassin -D --lint
 ----
 
 If you run a cluster, the `custom.cf` file is synchronized from the
-master node to all cluster members.
+master node to all cluster members automatically.
 
 
 [[pmgconfig_custom_check]]