On Thu, Jul 11, 2002 at 01:19:11PM -0700, Bob Sully wrote:

| The problem appears to be that spamd runs as root...

This is necessary so that it can setuid() to the proper user.

| spamc runs as the user.  It appears that the user's user_prefs file
| is read (hence its entry in the header) but the message is processed
| as root, using root's user_prefs file.

That is sure to happen if
    1)  spamc is run as root
and
    2)  no user to run as is specified (-u)

| This happens with about half of the messages from whitelisted
| senders.  The rest of the messages are processed correctly.  Odd.

| I believe the problem can be fixed by allowing spamd to run as the user,
| rather than root (this would also get rid of the "falling back to nobody"
| messages in the logs.

Actually, this is a real bug.  Ever since I upgraded to 2.30 (or was
it 2.31; in any case I'm using 2.31 now) I get that warning for
_every_ message, even though I do specify what user to run as.  I even
used tcpflow to ascertain that spamc did tell spamd what user to drop
to.  spamd ignores that, however.

| I haven't looked through the source, and I'm not a Perl programmer, so
| will leave the details to the maintainers.  Just thought I'd toss this out
| for discussion.

I'm not a perl programmer either.  Someone needs to put this in
bugzilla, though.  (I don't like bugzilla's UI, and I'm not near a
handy web browser, do you want to submit it?)

-D

-- 
 
Stay away from a foolish man,
for you will not find knowledge on his lips.
        Proverbs 14:7
 
http://dman.ddts.net/~dman/

Attachment: msg07362/pgp00000.pgp
Description: PGP signature

Reply via email to