I think I might have found the problem:
The directory /var/run/spamass/
Had owner group set at "spamass-milter:root". I changed that to
"spamass-milter:smmta". Also the permissions were set to drwxr-xr-x and I
changed that to drwxr-sr-x.
I will see if that will solve the problem.
Ken
On Wed, 15 Jun 2011, User for SpamAssassin Mail List wrote:
Also this is my /etc/default/spamass-milter
OPTIONS="-u nobody -i 127.0.0.1,209.102.124.20 -r 9 -M"
What strikes me odd is that the message that was stopped the milter had its
id set to "spamass-milter"
Jun 15 06:27:31 mail spamd[981]: spamd: connection from localhost [127.0.0.1]
at port 42127
Jun 15 06:27:31 mail spamd[981]: spamd: setuid to spamass-milter succeeded
The message that did not get stopped the milter had its id set the target
email id:
Jun 15 08:08:10 mail spamd[20901]: spamd: connection from localhost
[127.0.0.1] at port 55987
Jun 15 08:08:10 mail spamd[20901]: spamd: setuid to user succeeded
Both of the actual targets were real users (not aliases). And I cannot see
anywhere it should be set to "spamass-milter" when I have the -u nobody
option set in the default/spamass-milter file.
Ken
On Thu, 16 Jun 2011, Mihamina Rakotomandimby wrote:
On Wed, 15 Jun 2011 21:15:06 -0400
Ryan Pavely <para...@nac.net> wrote:
but doesn't that log show it was identified as spam?
it does...
--
RMA.
