On 2024-03-21 at 13:21:54 UTC-0400 (Thu, 21 Mar 2024 18:21:54 +0100) <giova...@paclan.it> is rumored to have said:
> On 3/20/24 21:58, 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...) >> > are you referring to spamassassin -W/-R options that are not present on > spamc(1) ? Yes, (plus all of the related --*-list commands.) It seems to me that it would require extension of the spamc/spamd protocol and cargo-culting some code from spamassassin to spamd. Looking to provide a more elegant solution to 'strong' feedback than giving scanning-client machines direct access to the reputation DB. For example, the script I have that handles user-identified escaped spam includes this ugly snippet: spamassassin --remove-from-welcomelist < $spam spamc -L spam < $spam spamassassin --add-to-blocklist < $spam This only works because the local spamassassin and remote spamd share access to the same reputation DB. This is not optimal. -- Bill Cole b...@scconsult.com or billc...@apache.org (AKA @grumpybozo and many *@billmail.scconsult.com addresses) Not Currently Available For Hire
signature.asc
Description: OpenPGP digital signature
