Update environment

diff --git a/mail.env b/mail.env
index 6650d48441918ba9efca5f1ba1fc74998bcf0dc9..fc7e9356b413e252431b4684eab3e4809691e6f0 100644 (file)
--- a/mail.env
+++ b/mail.env
@@ -118,7 +118,7 @@ ENABLE_POLICYD_SPF=1
 # Enables POP3 service
 # - **0** => Disabled
 # - 1     => Enabled
-ENABLE_POP3=0
+ENABLE_POP3=
 
 # Enables IMAP service
 # - 0     => Disabled
@@ -130,8 +130,9 @@ ENABLE_IMAP=1
 # **0** => Disabled
 ENABLE_CLAMAV=0
 
-# Add the value 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.
+# Add the value of this ENV as a prefix to the mail subject when spam is detected.
+# 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.
 SPAM_SUBJECT=
 
@@ -210,7 +211,7 @@ ENABLE_DNSBL=0
 #    cap_add:
 #      - NET_ADMIN
 # Otherwise, `nftables` won't be able to ban IPs.
-ENABLE_FAIL2BAN=1
+ENABLE_FAIL2BAN=0
 
 # Fail2Ban blocktype
 # drop   => drop packet (send NO reply)