bogofilter 1.3.0.rc2 now available, release candidate (fixes LMDB 1.0.0 database support)

[Steffen Nurpmeso]

Matthias Andree via bogofilter-announce wrote in
 <alDUSFaaK7v7PK48 at ryzen.an3e.de>:
 |bogofilter 1.3.0.rc2 is now available from
 ...
 |This fixes LMDB 1.0.0 compatibility (1.3.0.rc1 and older won't
 |read or write anything with LMDB 1.0.0 because they believe the maximum
 |key size were 0 - arguably an LMDB 1.0.0 documentation bug and breaking
 |API change, but easily fixed for us),
 ...

Sorry for this again, i have opened

  https://bugs.openldap.org/show_bug.cgi?id=10534

  ...
 |WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING
 |------------------------------------------------------------------------
 |POTENTIAL FOR DATA CORRUPTION DURING UPDATES
  ...

But to note that you possibly want to wait, i saw Howard Chu
speaking on postfix-devel, even though on something different, he
release[sd] 1.0.1

  https://marc.info/?t=178363071700003&r=1&w=2

  ...
 | 2026-07-02
 | * Add support for breaking changes in LMDB 1.0.0.  bogofilter's
 |   LMDB driver in 1.3.0.rc1 and older would reject all database
 |   transactions because it believed database lookup keys were too
 |   large.  Cause is an undocumented API change where we can only
 |   query the maximum key size after OPENING a database environment,
 |   not, as documented in 1.0.0 and 0.9.X before, after already
 |   creating it.
  ...

And i think it was always like that, but falsely documented.
It just never sprang into existence bevcause of how LMDB was used
i would think.  Sorry for this again.

Great we get a bogofilter update!!

--steffen
|
|Der Kragenbaer,                The moon bear,
|der holt sich munter           he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)