From: Stoiko Ivanov <s.ivanov@proxmox.com>
To: Dylan Whyte <d.whyte@proxmox.com>
Cc: pmg-devel@lists.proxmox.com
Subject: [pmg-devel] applied: [PATCH pmg-docs] pmgconfig: Link to SA rule writing documentation
Date: Tue, 11 Jan 2022 18:45:08 +0100 [thread overview]
Message-ID: <20220111184508.7087e8c2@rosa.proxmox.com> (raw)
In-Reply-To: <20220111153035.2628380-1-d.whyte@proxmox.com>
huge thanks for addressing this so quickly - applied
with Signed-off-by you added (I hope this is alright with you)
On Tue, 11 Jan 2022 16:30:35 +0100
Dylan Whyte <d.whyte@proxmox.com> wrote:
> 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
prev parent reply other threads:[~2022-01-11 17:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 15:30 [pmg-devel] " Dylan Whyte
2022-01-11 17:45 ` Stoiko Ivanov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220111184508.7087e8c2@rosa.proxmox.com \
--to=s.ivanov@proxmox.com \
--cc=d.whyte@proxmox.com \
--cc=pmg-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox