spamassassin (4.0.0-2) unstable; urgency=medium

  spamd now enables a number of hardening flags in the systemd service.
  Among these settings is ProtectSystem=full, which runs spamd in a
  private kernel mount namespace into which a number of system paths are
  mounted read-only.  This does not impact spamd's operation in the
  default configuration, but if you've configured spamd such that it
  relies on the ability to write to locations under nonstandard
  locations, such as /usr, you may need to adjust the hardening flags to
  permit write access to this location.

  For additional details, see SANDBOXING in systemd.exec(5).

 -- Noah Meyerhans <noahm@debian.org>  Sat, 31 Dec 2022 20:05:33 -0800

spamassassin (4.0.0~0.0svn1883440-2) experimental; urgency=medium

  The spamd service is now distributed in a dedicated spamd binary package.
  The spamassassin package declares a Recommends relationship on the spamd
  package, which means it will be installed in the default apt configuration.

  If you do not wish to run the spamd service, you should simply remove the
  spamd package.

  NOTE: If you are upgrading from earlier spamassassin versions and have made
  customizations to the spamd configuration in  /etc/default/spamassassin, by
  providing systemd drop-in unit configuration, or by editing
  /etc/init.d/spamassassin, you will need to migrate your changes to
  /etc/default/spamd or a spamd drop-in directory.

 -- Noah Meyerhans <noahm@debian.org>  Sun, 29 Nov 2020 14:47:37 -0800
