And it is even mentioned in the UPGRADE notes:
- The HashBL plugin in 342.pre is now enabled by default.
(sad typo in the filename)
On Wed, Dec 28, 2022 at 04:21:45PM +0200, Henrik K wrote:
>
> This was discussed and approved in some of the 4.0.0 bugs. There should be
> no need to revisit it. It still wouldn't make sense to have loadplugin
> HashBL in two *.pre files.
>
> On Wed, Dec 28, 2022 at 09:18:51AM -0500, Kevin A. McGrail wrote:
> > Wow, as it's enabled in v342.pre, that would imply it was enabled in 3.4.2.?
> > We should not have changed a past pre file for the 4.0.0 release IMO but
> > added it to the 4.0.0.pre file.? Such is life.? Should we fix it for 4.0.1?
> >
> > On 12/28/2022 9:07 AM, Henrik K wrote:
> > > Just keep in mind that HashBL is only enabled for fresh 4.0.0 installs, it
> > > wasn't default previously.
> >
> > --
> > Kevin A. McGrail
> > KMcGrail@Apache.org
> >
> > Member, Apache Software Foundation
> > Chair Emeritus Apache SpamAssassin Project
> > https://www.linkedin.com/in/kmcgrail - 703.798.0171
- The HashBL plugin in 342.pre is now enabled by default.
(sad typo in the filename)
On Wed, Dec 28, 2022 at 04:21:45PM +0200, Henrik K wrote:
>
> This was discussed and approved in some of the 4.0.0 bugs. There should be
> no need to revisit it. It still wouldn't make sense to have loadplugin
> HashBL in two *.pre files.
>
> On Wed, Dec 28, 2022 at 09:18:51AM -0500, Kevin A. McGrail wrote:
> > Wow, as it's enabled in v342.pre, that would imply it was enabled in 3.4.2.?
> > We should not have changed a past pre file for the 4.0.0 release IMO but
> > added it to the 4.0.0.pre file.? Such is life.? Should we fix it for 4.0.1?
> >
> > On 12/28/2022 9:07 AM, Henrik K wrote:
> > > Just keep in mind that HashBL is only enabled for fresh 4.0.0 installs, it
> > > wasn't default previously.
> >
> > --
> > Kevin A. McGrail
> > KMcGrail@Apache.org
> >
> > Member, Apache Software Foundation
> > Chair Emeritus Apache SpamAssassin Project
> > https://www.linkedin.com/in/kmcgrail - 703.798.0171