On 2002-12-31 10:50:57 -0500, Dan Schwartz wrote:
> :0fw
:0fw: spamc.lock
> * < 10
> | spamc
Otherwise each mail will spawn a new instance of procmail and
spamc immediately. That means 100 instances if 100 mails arrive
at a time. Makes for a nice DOS. :-)
Best regards
Martin
--
> Yeah, you're wrong. spamc will automagically pass the username it's
> executing as to spamd. So spamc -u $LOGNAME is identical to spamc.
> spamc -u somethingelse is however not the same as spamc by itself. So
> the distinction is based on what userID spamc is running as. I myself
Well, I d
Yeah, you're wrong. spamc will automagically pass the username it's
executing as to spamd. So spamc -u $LOGNAME is identical to spamc.
spamc -u somethingelse is however not the same as spamc by itself. So
the distinction is based on what userID spamc is running as. I myself
use spamc -u becau
> (Get rid of -u $LOGNAME -- it's deprecated anyways)
Depending on your settings, the -u option may be the ONLY way for
spamc/spamd to create the user_pref files.
And the setting I am thinking about is when the user's dir are NFS
mounted on the mail server, from another machine, and that they ar
On Sat, Mar 30, 2002 at 09:13:58AM -0500, Jeffrey Bacon wrote:
> So you've got it running on a LInix box? I'm having a devil of a time
> gettig mail to be delivered after running ti through spamc on my Red Hat
> box. Could you just check to see if my setup is the same as yours?
>
> /etc/procm
That could be equivalent to my set-up. I start spamd from /etc/rc.d/
init.d/spamassassin, which basicly runs "spamd -d -u spamd", where the
spamd user has no privileges. I've attached my procmail recipe.
Good luck...
On 30 March 2002 at 9:13, Jeffrey Bacon <[EMAIL PROTECTED]> wrote:
So you'v
So you've got it running on a LInix box? I'm having a devil of a time
gettig mail to be delivered after running ti through spamc on my Red Hat
box. Could you just check to see if my setup is the same as yours?
/etc/procmailrc:
SHELL=/bin/sh
VERBOSE=yes
LOGABSTRACT=all
LOGFILE=/var/log/procmai
Permissions are readable by all. The test example you show
works just fine. It's only from procmail that spamrc doesn't
seem to connect to spamd [on my Solaris 2.8 box installed in
my account space]. The whole thing works just dandy installed
in system
Check perms. When I installed this puppy a few days back (Yep, a newbie),
the perms on the *.cf files were set in such a way that spamd could not
read them (readable only by root). Once that was fixed spamc/spamd started
working.
I also wound up changing the daemon line in the init script, a
