From 5a482118b8e3ec47d5c35012f48a8988b9af748a Mon Sep 17 00:00:00 2001 From: James Lu Date: Sat, 20 Oct 2018 11:58:36 -0700 Subject: [PATCH] example-conf: describe more thoroughly how antispam handles unsupported punishments --- example-conf.yml | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/example-conf.yml b/example-conf.yml index bd43d81..1d1d0e1 100644 --- a/example-conf.yml +++ b/example-conf.yml @@ -951,8 +951,12 @@ stats: # Sets the punishment that Antispam's text spamfilter should use. # Valid values include "kill", "kick", "ban", "quiet", and combinations of these strung # together with "+" (e.g. "kick+ban"). Defaults to "kick+ban+block" if not set. - # If you want Antispam to also monitor PM spam, you will want to change this to something - # not channel-specific (such as "kill" or "block"). + # If you want to use Antispam with PM monitoring (see the "watch_pms" option below), you + # will want to include at least one punishment that is not channel-specific + # ("kill" or "block"). + # Punishments not supported in a context or network (e.g. kicking for PM spam or "quiet" + # on a network that doesn't support it) will be silently dropped if others succeed. + # If no punishments succeed, then a warning will be logged. #punishment: kick+ban+block # Sets the kick / kill message used when the text spamfilter is triggered.