On 05/01/2026 11:47, Wietse Venema via Postfix-users wrote:
That leaves an implementation based on emulation; I opted for a
variant with on-demand database re-indexing in the background. This
does not require that configuration files are updated, though making
such updates would save a few CPU cycles later.
An possible issue with this has just occurred to me. As previously
stated the stock EL10 packages do not support BDB but the GhettoForge
packages do, so if someone were to port their install to EL10 with the
stock postfix they might end up with a configuration that has hash:
entries (or default entries) but is in fact using cdb: because the
databases were "automatically" ported over.
Said user then, for whatever reason decides to switch to the GhettoForge
packages which *do* support BDB. The config still shows hash: entries
and so as a result they have been using and updating to cdb files for
some time but now postfix tries to read from .db files and either fails,
or has old data.
Granted this is not likely going to be an issue with EL10 because EL10
is never going to update the stock postfix to a version that has this
automatic db conversion feature (Red Hat will simply continue to
backport security and bug fixes), but it could happen in e.g. EL11 when
it gets released in a few years time.
This concerns me because I then have to either drop BDB support from the
GhettoForge packages (which I would rather not do when it is readily
available from EPEL) or I have to come up with some sort of other fix to
deal with this potential scenario in the future.
Peter
_______________________________________________
Postfix-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
