Bill Cole wrote:
On 2024-03-21 at 11:57:43 UTC-0400 (Thu, 21 Mar 2024 11:57:43 -0400)
Kris Deugau <kdeu...@vianet.ca>
is rumored to have said:
Bill Cole wrote:
I'm not sure how I've not noticed before, but unless I'm missing
something, there is no way to replicate the [block,welcome]list
functionalities of the spamassassin script when using the spamc/spamd
interface.
Does anyone see it hiding somewhere that I don't?
Does anyone have any rationale for this missing functionality?
I don't expect that it would be difficult to add. (Something I've
believed every time I've taken on a coding task...)
I'm pretty sure you're doing something wrong (maybe a
missing/commented loadplugin entry somewhere?
Maybe you've misunderstood my question. The spamc/spamd system uses
whatever AWL or TxRep DB is configured in evaluating messages and does
the automated part of managing those. The spamassassin-run man page
refers to spamd in the description of -W, -R, and various
--{add,remove}_*list options, but I see no way that they are relevant to
spamd.
Ahhh, OK, completely different subsystem. I misread because I don't use
that functionality at all - on the rare occasions I've wanted to
manipulate AWL data at that fine-grained a level, I "just" dive into the
backing DB and hand-bodge it directly.
I think you're looking for something relating to the -l flag to spamd,
but on reading the man page detail I'm not sure it hooks into AWL,
TXRep, or any similar components - only Bayes and "remote database" (eg
Razor or pyzor).
-l, --allow-tell
Allow learning and forgetting (to a local Bayes database),
reporting and revoking (to a remote database) by spamd. The client
issues a TELL command to tell what type of message is being
processed and whether local (learn/forget) or remote
(report/revoke) databases should be updated.
At a quick first dive, you're probably looking around line 2260 in
spamd, either adding some new logic branches right in spamd or adding
another mode to SpamAssassin/Reporter.pm.
I don't see anything closer.
-kgd
