From: Stoiko Ivanov <s.ivanov@proxmox.com>
To: pmg-devel@lists.proxmox.com
Subject: [pmg-devel] [PATCH pmg-api 2/2] user accesslists: reword logging and hits for SA 4.0
Date: Mon, 28 Nov 2022 19:17:29 +0100 [thread overview]
Message-ID: <20221128181729.63076-3-s.ivanov@proxmox.com> (raw)
In-Reply-To: <20221128181729.63076-1-s.ivanov@proxmox.com>
This commit adapts the sa-hits and the logging for the user
block/welcomelist to be consistent with the terms used in the
SpamAssassin 4.0 release, avoiding racially charged terms.
This patch is a (small part) of the fix for #3755, which will be
addressed along with the upgrade to SpamAssassin 4.0 (to be consistent
with the (quite well thought-through) namings used by SA)
keeping the USER_IN_BLACKLIST hit when loading the descriptions
catches mails put in quarantine before the patched version was
installed.
Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
---
src/PMG/RuleDB/Spam.pm | 8 ++++----
src/PMG/Utils.pm | 3 ++-
2 files changed, 6 insertions(+), 5 deletions(-)
diff --git a/src/PMG/RuleDB/Spam.pm b/src/PMG/RuleDB/Spam.pm
index d7bfb63..14d7bea 100644
--- a/src/PMG/RuleDB/Spam.pm
+++ b/src/PMG/RuleDB/Spam.pm
@@ -204,7 +204,7 @@ sub what_match_targets {
if ($queue->{blackwhite}->{$pmail} &&
($list = $queue->{blackwhite}->{$pmail}->{whitelist}) &&
check_addrlist($list, $queue->{all_from_addrs})) {
- syslog('info', "%s: sender in user (%s) whitelist",
+ syslog('info', "%s: sender in user (%s) welcomelist",
$queue->{logid}, encode('UTF-8', $pmail));
} else {
$target_info->{$t}->{marks} = []; # never add additional marks here
@@ -219,11 +219,11 @@ sub what_match_targets {
sa_score => 100,
sa_max => $self->{level},
sa_data => [{
- rule => 'USER_IN_BLACKLIST',
+ rule => 'USER_IN_BLOCKLIST',
score => 100,
desc => PMG::Utils::user_bl_description(),
}],
- sa_hits => 'USER_IN_BLACKLIST',
+ sa_hits => 'USER_IN_BLOCKLIST',
};
my $list;
@@ -233,7 +233,7 @@ sub what_match_targets {
check_addrlist($list, $queue->{all_from_addrs})) {
$target_info->{$t}->{marks} = [];
$target_info->{$t}->{spaminfo} = $info;
- syslog ('info', "%s: sender in user (%s) blacklist",
+ syslog ('info', "%s: sender in user (%s) blocklist",
$queue->{logid}, encode('UTF-8',$pmail));
}
}
diff --git a/src/PMG/Utils.pm b/src/PMG/Utils.pm
index b9b1478..10193f6 100644
--- a/src/PMG/Utils.pm
+++ b/src/PMG/Utils.pm
@@ -1167,7 +1167,7 @@ sub bencode_header {
}
sub user_bl_description {
- return 'From: address is in the user black-list';
+ return 'From: address is in the user block-list';
}
sub load_sa_descriptions {
@@ -1207,6 +1207,7 @@ sub load_sa_descriptions {
$res->{'ClamAVHeuristics'}->{desc} = "ClamAV heuristic tests";
$res->{'USER_IN_BLACKLIST'}->{desc} = user_bl_description();;
+ $res->{'USER_IN_BLOCKLIST'}->{desc} = user_bl_description();;
return $res;
}
--
2.30.2
next prev parent reply other threads:[~2022-11-28 18:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 18:17 [pmg-devel] [PATCH pmg-api 0/2] fix deprecation warning for user blocklist hits Stoiko Ivanov
2022-11-28 18:17 ` [pmg-devel] [PATCH pmg-api 1/2] user-bl: use custom description of USER_IN_BLACKLIST consistently Stoiko Ivanov
2022-11-28 18:17 ` Stoiko Ivanov [this message]
2022-11-29 15:07 ` [pmg-devel] applied-series: [PATCH pmg-api 0/2] fix deprecation warning for user blocklist hits Thomas Lamprecht
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=20221128181729.63076-3-s.ivanov@proxmox.com \
--to=s.ivanov@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.