> Well in my installation, I did in fact have to add -u root to get it to > work.
Then your setup is flaky. > 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. It probably has something to do with creating user preference files... and since spamc is called from qmail-scanner as qmailq, it is unable to create user prefs for qmailq. There are alot of things I dont know here about your setup, but that would be my first guess. Do you launch your spamd with the -c flag? Just curious. > I don't know why my installation seems to be different, but I have seen > other people with posts like mine on the qmail-scanner mail list so I know > I'm not alone. I'm sure there is an answer for this, and adding -u root is not the correct one, because like I said, -u root has nothing to do with what user is binding. Also, spamc cannot increase it's permission level to root if ran by qmailq unless it was SETUID.... which it is not. I'll tell you 100% that -u root is NOT the correct fix.... Dallas > > -----Original Message----- > From: Dallas Engelken > To: Woodworth, Eric > Cc: [EMAIL PROTECTED] > Sent: 2/11/02 8:14 PM > Subject: Re: [SAtalk] Has anybody gotten SA to work with Qmail and Qmail s > canner? > > > 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 code > looks > > to me) but as long as it's working I'm happy. > > > > Thanks for the help and suggestions. > > > > qmailq doesnt need to bind a port. the port is binded when run spamd, > not > spamc. spamc is just the client that makes a socket to the open port > spamd > runs on. > > i launch spamd as root with > root@localhost# spamd -d > > then, i call spamc with the -f flag only from qmail-scanner which > everyone > knows runs as qmailq. you do not need to add a -u root to spamc to make > this work... > > > -u username: specify the username for spamd to process this message > under > this basically tells spamd which user is calling it, that way spamd know > which .spamassassin files to process. now if you look at your logs, > it'll > look like every message was processed for root if you do it that way. > > Dallas > > > _______________________________________________ > Spamassassin-talk mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/spamassassin-talk _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
