Bill Cole wrote:
On 2023-06-20 at 12:33:05 UTC-0400 (Tue, 20 Jun 2023 18:33:05 +0200)
Patrick Proniewski <pat...@patpro.net>
is rumored to have said:
On 20 Jun 2023, at 17:49, Bill Cole
<sausers-20150...@billmail.scconsult.com> wrote:
On 2023-06-20 at 09:39:04 UTC-0400 (Tue, 20 Jun 2023 15:39:04 +0200)
Patrick Proniewski <pat...@patpro.net>
is rumored to have said:
Hello,
I'm running amavisd-new (milter) with spamassassin 4.x on FreeBSD,
both from pkg, and I see the same problem. It appears that my
/var/amavis/tmp holds every single sspamassassin tmp file from the
day I've upgraded to 4.x.
Did you upgrade or reconfigure Amavis at the same time?
I did not upgrade. I did not reconfigure either.
Do you suggest I should deinstall / reinstall Amavisd-new?
Only if you'd prefer rebuilding the config from defaults instead of
trying to validate what you have. Or seek help from whatever channels
are available for Amavis.
I DO NOT KNOW that there is any particular way to make this happen, only
that if files are being left in the Amavis temp directory, something
closely tied to Amavis is causing them to land there and failing to
clean up. Despite the filenames, I'm skeptical that it is SA itself
creating these files, but rather suspect that something using SA and
seeing that as its temp directory (i.e. Amavis.) is causing the problem.
Easy for me to say, as I don't use Amavis. :)
I can say that I've had no similar problems on with such detritus
running SA4 via spamd/spamc on FreeBSD 12 or 13, nor when running it via
MIMEDefang on Darwin 15.
Just to put another data point in, I've had intermittent runs of
leftover temp files across several SA releases. Running spamd here so
it's nothing inherent with Amavis. Might be side effects of some blip
in processing with one or the other of Vipul's Razor, Pyzor, or a custom
clamd instance using only third-party and local spam-targeted sigs. To
date it's been rare enough I just clean them up by hand once in a while,
but the same cleanup could be dropped in cron.
-kgd
