On 2022-04-01 at 14:31:32 UTC-0400 (Fri, 01 Apr 2022 20:31:32 +0200)
Benny Pedersen <m...@junc.eu>
is rumored to have said:
bug in spamassassin 3.4.6, BLOCKLIST_TO dont work, but BLACKLIST_TO do
work but says depricated
That's a lousy bug report. It's both (1) untrue (or at least grossly
imprecise) and (2) not in Bugzilla.
BLOCKLIST_TO is not a thing. Never has been. Probably never will be.
There will likely be a config directive 'blocklist_to' replacing the
current 'blacklist_to' in 4.0.
USER_IN_BLOCKLIST_TO is a rule which works JUST FINE.
USER_IN_BLACKLIST_TO also exists and still works but is deprecated.
So: what **PRECISELY** are you complaining about???
is this one solved in 3.4.7 ?
Who has ever said there would BE a 3.4.7???
I would argue against any release that does not include all of what is
now the tip of the trunk in subversion, which expects to see release as
4.0.0. 3.4.4 should have been the terminal 3.x release, 3.4.5 was
labeled as such, and 3.4.6 only exists to address a severe problem found
right after 3.4.5 was released.
I believe that Henrik has backported some of the fixes that he's done
for 4.x into the 3.4 branch, but aside from that I don't think any
contributors have done anything to that branch since the 3.4.6 release.
If any of the other active contributors really thinks that it is a
useful expenditure of *their* time/energy for them to prepare and
publish a 3.4.7 release from what is now in the 3.4 branch I would not
veto it, but I would grumble disagreeably.
--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Not Currently Available For Hire
