> Well for the record, just adding "-u root" into the line in the scanner
> script that calls spamc fixed the problem. Qmailq couldn't bind to ports.
> It's odd because it should bind to the port while still running as root
and
> only change to qmailq after that point (at least that's how the cod
Well in my installation, I did in fact have to add -u root to get it to
work.
It would not work otherwise. When I just ran spamc -f it failed, when I
added spamc -f -u root it worked. I can't argue with results.
I don't know why my installation seems to be different, but I have seen
other peop
I am having a difficult time configuring spamproxyd to work with my
Postfix system. It seems to me as if I am invoking (spawning) spamproxyd
incorrectly. When I test SA via command line, things work fine. Any help
would be appreciated.
-- mail.log exerpt-
Feb 12 08:20:08