--On August 19, 2015 at 5:47:44 PM +0000 Viktor Dukhovni
<[email protected]> wrote:
On Wed, Aug 19, 2015 at 12:30:55PM -0500, Paul Schmehl wrote:
When it is broken, you need to fix it, not comment it out, *and*
when commenting out multi-line entries in master.cf, you have to
comment out *each* line, not just the first.
Normally that's what I try to do. In this case I was stumped.
After I got the server working properly again, I began sifting through logs
trying to see if there were any clues. I found this in the messages log:
/var/log/messages:Aug 19 14:43:21 mail postfix/pipe[17690]: fatal:
get_service_attr: unknown username: filter
Very weird. That user was created in 2012:
/var/log/userlog:2012-09-27 22:46:45 [root:groupadd] filter(1004)
/var/log/userlog:2012-09-27 22:46:45 [root:useradd]
filter(1004):filter(1004):User &:/home/filter:/bin/bash
/var/log/userlog:2012-09-27 22:46:45 [root:useradd] filter(1004) home
/home/filter made
/var/log/userlog:2012-09-27 22:47:22 [root:usermod]
filter(1004):filter(1004):User &:/home/filter:/bin/sh
And still exists:
# grep filter /etc/passwd
filter:*:1004:1004:User &:/home/filter:/bin/sh
So why postfix thought the user didn't exist is a mystery, but that's why
the filter was no longer working.
> Do you want that "filter.sh" script to scan all inbound mail or not?
Of course I do, but it wasn't working, which is why I removed it.
Well, that can't work, because you're configured to use it.
Yes, I wanted spam filtering. And I didn't understand why something that
had "just worked" for 3 years suddenly failed. The answer is because
Postfix thought the user no longer existed, but I can't tell you why
Postfix thinks that. It works now piping directly through spamd.
Paul Schmehl ([email protected])
Independent Researcher
