Apply suggestions from code review
Co-authored-by: Brennan Kinney <5098581+polarathene@users.noreply.github.com>
This commit is contained in:
Georg Lauterbach
GitHub
parent
9d828c51ec
commit
322480235f
|
|
@ -77,9 +77,9 @@ The most noteworthy change of this release is the update of the container's base
|
|||
- **Tests:**
|
||||
- Refactored helper methods for sending e-mails with specific `Message-ID` headers and the helpers for retrieving + filtering logs, which together help isolate logs relevant to specific mail when multiple mails have been processed within a single test. ([#3786](https://github.com/docker-mailserver/docker-mailserver/pull/3786))
|
||||
- **Rspamd**:
|
||||
- The `rewrite_subject` action, is now disabled by default. It has been replaced with the new `SPAM_SUBJECT` environment variable, which implements the functionality via a Sieve script instead in favor of being anti-spam service agnostic ([3820](https://github.com/docker-mailserver/docker-mailserver/pull/3820))
|
||||
- `RSPAMD_NEURAL` was added and is disabled by default. If switched on it wil enable the experimental Rspamd Neural network module to add a layer of analysis to spam detection using neural network technology. ([3833](https://github.com/docker-mailserver/docker-mailserver/pull/3833))
|
||||
- The symbol weights of SPF, DKIM and DMARC have been adjusted again, on the one hand to fix a bug, on the other hand to include more appropriate combinations of symbols ([3913](https://github.com/docker-mailserver/docker-mailserver/pull/3913))
|
||||
- The `rewrite_subject` action, is now disabled by default. It has been replaced with the new `SPAM_SUBJECT` environment variable, which implements the functionality via a Sieve script instead which is anti-spam service agnostic ([#3820](https://github.com/docker-mailserver/docker-mailserver/pull/3820))
|
||||
- `RSPAMD_NEURAL` was added and is disabled by default. If switched on it will enable the experimental Rspamd "Neural network" module to add a layer of analysis to spam detection ([#3833](https://github.com/docker-mailserver/docker-mailserver/pull/3833))
|
||||
- The symbol weights of SPF, DKIM and DMARC have been adjusted again. Fixes a bug and includes more appropriate combinations of symbols ([#3913](https://github.com/docker-mailserver/docker-mailserver/pull/3913))
|
||||
|
||||
### Fixes
|
||||
|
||||
|
|
|
|||
|
|
@ -102,12 +102,9 @@ DMS does not supply custom values for DNS servers to Rspamd. If you need to use
|
|||
|
||||
!!! warning
|
||||
|
||||
Rspamd heavily relies on a functioning DNS. In case your DNS does not work, you will encounter issues in the form of
|
||||
Rspamd heavily relies on a properly working DNS server that it can use to resolve DNS queries. If your DNS server is misconfigured, you will encounter issues when Rspamd queries DNS to assess if mail is spam. Legitimate mail is then unintentionally marked as spam or worse, rejected entirely.
|
||||
|
||||
1. e-mails being marked as spam when they actually are not spam;
|
||||
2. e-mails being rejected because Rspamd is confident that the e-mails are spam, when they actually are not spam.
|
||||
|
||||
An example here are the SPF, DKIM and DMARC checks, all of which are based on DNS records. These checks have a symbol for DNS temporary errors, with a non-zero weight - i.e., they will increase the spam score of the e-mail. This is undesirable, especially because mechanisms like SPF, DKIM and DMARC are frequently used to avoid spam.
|
||||
When Rspamd is deciding if mail is spam, it will check DNS records for SPF, DKIM and DMARC. Each of those has an associated symbol for DNS temporary errors with a non-zero weight assigned. That weight contributes towards the spam score assessed by Rspamd which is normally desirable - provided your network DNS is functioning correctly, otherwise when DNS is broken all mail is biased towards spam due to these failed DNS lookups.
|
||||
|
||||
!!! danger
|
||||
|
||||
|
|
|
|||
|
|
@ -2,10 +2,9 @@
|
|||
# https://github.com/docker-mailserver/docker-mailserver/issues/3690
|
||||
# for understanding this file and its scores' values.
|
||||
#
|
||||
# This configuration is not 100% compliant with RFC7489. This is intentional!
|
||||
# Rspamd has more symbols than just the ones defined in this file alone. Aligning
|
||||
# 100% to RFC7489 is therefore not desirable as other symbols will change the
|
||||
# overall spam score anyway.
|
||||
# This configuration is not 100% compliant with RFC7489.
|
||||
# This is intentional! Rspamd has additional symbols than those defined in this file.
|
||||
# 100% compliance is not desirable as those symbols will change the overall spam score.
|
||||
|
||||
symbols = {
|
||||
# SPF
|
||||
|
|
|
|||
Loading…
Reference in New Issue