On Sat, Jan 05, 2019 at 07:58:45AM +0100, debian-bugreports...@sethdepot.org wrote: > > Instead I worked around this issue with the following change in the > postinst script /var/lib/dpkg/info/spamassassin.postinst > Line 38 > su - $OWNER -c "sa-update \ > --gpghomedir /var/lib/spamassassin/sa-update-keys \ > --import /usr/share/spamassassin/GPG.KEY" > Replace: "su - $OWNER -c " --> "sudo -u $OWNER sh -c" > > sudo does work with disabled accounts, su doesn't
Probably better to use start-stop-daemon, as the daily cron job does, rather than take the extra dependency on sudo. But yes, this seems like a reasonable fix. I assume you haven't noticed any other issues with spamassassin when running with its shell set to /usr/sbin/nologin? noah
