check tmp path in all software used, this includes how perl versions
handle tmp dirs and files, in your case its amavisd that create dirs,
and its amavisd that tells spamassassin in with dir to scan email with
embed spamassassin engine in amavisd, check if other spamscanners
works in amavisd, eg change from spamassassin to spamdclient, and then
start spamd
does this leave temp files still ?
is cpan latest trunk version ?, i fear its not
This is problem not in amavis or system but in spamassassin-4.
Problem not exists in this sam machine in older spamassasin like
spamassasin-3.x
I tested via configurations
1)dovecot10 + spamassasin-3.x - problem not exists
2)dovecot11 + spamassasin-3.x - problem not exists
3)dovecot10 + spamassasin-4.x - problem exists
4)dovecot11 + spamassasin-4.x - problem exists
all dovecot have this same amavisd-new-2.11.1
If there was a problem in the path /tmp and/or amavis configuration, the
problem would be everywhere, not just with only in spamassassin-4.x
Again it says that spamassassin-4.x deletes teporary files but not all
and it creates more than it deletes
It seems as if for some reason specific files (e-mails) could not be deleted
ergo
Problem is in binary spamassassin-4.x
--
