I had a server running dovecot-antispam for many, many years, and feared the loss of this functionality with the trixie release, however there is good news!
dovecot can be configured to natively handle precisely what this package
provides, via sieve integration. It's documented upstream, and works in
both 2.3¹ and 2.4².
I successfully configured it under bookworm (dovecot 2.3), removed
dovecot-antispam, and after satisfactory results, upgraded to trixie
(dovecot 2.4), had a bit of headache with the conf file migration, and
now it's working great!
FWIW, I was worried about downtime with a production system, so I took
quite a few extra steps to handle the migration. Debian, and these
packages in particular, are quite flexible, AWESOME!
* Rebuilt dovecot-antispam with bookworm-backports version of dovecot,
2.3.19.1 -> 2.3.21.1, since there is ABI incompatibility. This was
probably unnecessary (somehow I inferred the idea that I better be
on the latest 2.3.x version before continuing...), but rebuilding
the package was trivial.
* Upgraded to bookworm-backports versions of dovecot and [site-local]
dovecot-antispam packages on the production system, though
unnecessary, was trivial.
* Implemented the dovecot 2.3 spam-reporting documentation¹ replacing
the need for dovecot-antispam. This was really straight-forward, as
I had already been using sieve, and had minimum downtime on the
production system.
* In preparation for the 2.4 migration: Using a scratch trixie virtual
machine, installed the bookworm-backports version of dovecot (should
work with bookworm version too); Copied production conf files over
the fresh install - the result is non-functional (missing LDA), but
verifies daemon startup; Upgraded to trixie version; Manually
merged the *.ucf-dist files - this took quite a bit of time
deciphering the customizations that have been in place ~15 years,
reading docs, etc.; tar'd up the new conf files and threw away the
VM;
* On the production system: Package-pinned dovecot to the
bookworm-backports version; Upgraded the rest of the system to
trixie; Amazed this worked so well!
* Finally, on the production system: Unpacked the pre-migrated conf
files from the test VM; Removed package-pin and upgraded dovecot to
trixie version; Fought with some configuration problems related to
the 2.4 migration for a while, but had nothing to do with the
spam-reporting functionality; Viola!
¹ https://doc.dovecot.org/2.3/configuration_manual/howto/antispam_with_sieve/
² https://doc.dovecot.org/2.4.1/core/config/spam_reporting.html
--
Gerald Turner <[email protected]> Encrypted mail preferred!
OpenPGP: 4096R / CA89 B27A 30FA 66C5 1B80 3858 EC94 2276 FDB8 716D
signature.asc
Description: PGP signature
