On Wed, 11 Dec 2024 21:50:53 +0100,
Tim van der Molen <t...@kariliq.nl> wrote:
>
> Kirill A. Korinsky (2024-12-09 19:17 +0100):
> > Fixing permission at /var/spool/spamassassin/spampd looks too complicated,
> > because we run spamassassin's spamd at one user, and mail/spampd from
> > another one. Insted magic of permission or moving files in rc-script...,
> > I've add pkg/MESSAGE with instruction how to move the data.
>
> I'm probably missing something, but I don't understand why you mention
> spamassassin's spamd. What is wrong with the following change?
>
I was wrong. Sorry. Spamassassin uses /var/db/spamassassin, and not
/var/spool/spamassassin.
> Index: pkg/PLIST
> ===================================================================
> RCS file: /cvs/ports/mail/spampd/pkg/PLIST,v
> diff -p -u -r1.5 PLIST
> --- pkg/PLIST 8 Nov 2022 11:14:52 -0000 1.5
> +++ pkg/PLIST 11 Dec 2024 20:01:11 -0000
> @@ -8,3 +8,5 @@ sbin/spampd
> @owner _spampd
> @group _spampd
> @sample /var/spampd/
> +@mode 0700
> +@sample /var/spool/spamassassin/spampd/
>
Well, PLIST states:
@comment homedir needed to store the .spamassassin bayes DB
@extraunexec rm -rf /var/spampd/.spamassassin
and based on that, I think that /var/spool/spamassassin/spampd/ is an
unexpected place that was used due to missed chunk in patch, and the
intended and correct place is /var/spampd, which also looks logical because
it keeps data in the user's homedir.
--
wbr, Kirill
