docs: `mailserver.env` improve description for `SPAM_SUBJECT` (#4050)
Co-authored-by: Casper <casperklein@users.noreply.github.com>
This commit is contained in:
parent
eb165ded65
commit
f1df81a7e4
|
@ -130,8 +130,9 @@ ENABLE_IMAP=1
|
||||||
# **0** => Disabled
|
# **0** => Disabled
|
||||||
ENABLE_CLAMAV=0
|
ENABLE_CLAMAV=0
|
||||||
|
|
||||||
# Add the value as a prefix to the mail subject when spam is detected.
|
# Add the value of this ENV as a prefix to the mail subject when spam is detected.
|
||||||
# NOTE: By default spam is delivered to a junk folder, reducing the value of a subject prefix for spam.
|
# NOTE: This subject prefix may be redundant (by default spam is delivered to a junk folder).
|
||||||
|
# It provides value when your junk mail is stored alongside legitimate mail instead of a separate location (like with `SPAMASSASSIN_SPAM_TO_INBOX=1` or `MOVE_SPAM_TO_JUNK=0` or a POP3 only setup, without IMAP).
|
||||||
# NOTE: When not using Docker Compose, other CRI may not support quote-wrapping the value here to preserve any trailing white-space.
|
# NOTE: When not using Docker Compose, other CRI may not support quote-wrapping the value here to preserve any trailing white-space.
|
||||||
SPAM_SUBJECT=
|
SPAM_SUBJECT=
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue