pat...@patpro.net skrev den 2023-06-21 13:33:
June 21, 2023 12:59 PM, "Matija Nalis" <mnalis-sa-l...@voyager.hr>
wrote:
Another way to prove that the problem is exclusively in spamassassin
is to reproduce the problem ONLY with spamassassin (i.e. without
dovecot, amavisd, etc. being involved at all) - e.g. by manually
running "spamassassin -t /tmp/blah.mbox" and showing that it creates
and leaves behind some temporary files.
Fully agree with that.
More importantly, when one uses Amabosd-new with Spamassassin, there
is no spamassassin running, Amavisd-new loads the SA lib and uses the
code. So may be there is a mismatch between Amavisd-new and the new
code of SA 4.x.
spamassassin spamd/spamc might use another $HOME then amavisd-new
i just ask people to check it
in @spam_scanners amavisd.conf it defaults to spamassassin, but change
this to spamdclient and start spamd in spamassassin, if this still leave
tmp files, create a bug for spamassassin
running spamassassin as root changes all problems
more info from OP please
