Le 03/09/2021 à 14:13, Reindl Harald a écrit :
On 03.09.21 11:23, Jean-François Bachelet wrote:
Le 03/09/2021 à 09:11, Bob Proulx a écrit :
Jean-François Bachelet wrote:
Le 02/09/2021 à 13:07, Antony Stone a écrit :
How did you install it?
'apt install' spamassassin spamc (as all the other stuff that
works on that server.)
At that moment permissions were correct and everything was set to work
correctly.
then,
user create
'useradd -u 5001 -g spamd -s /sbin/nologin -d /var/lib/spamassassin
spamd'
mkdir /var/lib/spamassassin
chown -R spamd:spamd /var/lib/spamassassin
At that moment the installation was broken by these actions!
Permissions and ownership were set so as to prevent it from working.
ok, so what should be the right things to do here ? without
explaining what's wrong that doesn't help.
for the sake of god don't change things you do not understand - the
distribution prepared everything so that it works out of the box on
thousands of setups, you touch everything left and right and then ask
the *upstream* community how to fix what you broke
work out of the box when installed standalone... yes.
but is the integration with a bunch of others that need to run in close
cooperation automatically handled by the individual installers in all
situations/operating systems flavours ? really ?
even if that woul dhave worked shortly there are good chances that
cron-scripts and package-scripts later would touch the permsisions
again because they look like need to be fixed
I've just picked the latest tuto I found for
postfix/clamav/spamassassin/amavis-new integration. if it are so wrong
why aren't it been corrected since it was published ?
btw, doesn't we all learn from our errors ? ^^)
Jeff
