Hi,
I would love to have an extra option '--check-socket-user' or similar
and let spamd check(or solely use) the uid of the spamc process but
ignoring any false"-u someotheruser" settings.
I have heard from one of our sys-admins the following:
If $client is a socket that has been generated with
Hi Douglas,
Douglas Kirkland schrieb :
[...]
> And the world could end. What happens if some user messes with
> somebody elses stuff? That what logs are for and boot the user. You
> are god of the servers. Oh sorry, back to the real world. Give them
> guild line in the spamc line on how it w
Hi Brad,
Brad Koehn schrieb :
>
> On Dec 30, 2003, at 5:45 PM, Hans Gerber wrote:
> >
> >>> We only want spamd to listen on '--socketpath=path'. Spamc should
> >be>> invoked from within .procmailrc.
> >>
> >> I could not get this m
Hi Douglas,
Douglas Kirkland schrieb :
> Why does it matter if one of your users uses some other user's
> user_prefs file. As far as I am concerned I do not care if one of my
> users uses another user's user_prefs file. They would only hurt
> themselves by using some other user_prefs file. You
Hello,
Hans Gerber schrieb :
> Now there is also the 'spamd --auth-ident' option available. Now my
> question: Is anyone using this option and can it assure that spamd
> wont use any but the user_prefs of the user that is calling spamc?
So far I am not able to get -
Hello to everyone,
We are running a server with some dozens of users with shell
access. Up to now everyone has the ability to call spamassassin from
within .procamilrc. This gives us quite some load for multiple
spamassassin processes.
Now we are evaluating the possible use of spamd. Our users ho
