> > >You forgot spamlogd > > I did not, it starts automatically when spamd_grey is enabled in >Oh. Sorry. I didn's see it in your ps grep. I see it with the same >ps grep on my system. > >dumbcat[root]# ps aux | grep spamd >_spamd 14450 0.0 0.1 9040 1376 ?? Is Tue12AM 1:53.41 spamd: (pf ><spamd-white> update) (spamd) >_spamd 25485 0.0 0.8 8968 9592 ?? S Tue12AM 0:50.54 >/usr/libexec/spamd -g >_spamd 10132 0.0 0.1 8968 1272 ?? I Tue12AM 0:00.60 spamd: >(/var/db/spamd update) (spamd) >_spamd 14234 0.0 0.1 536 1216 ?? Ss Tue12AM 0:09.53 >/usr/libexec/spamlogd >root 11990 0.0 0.0 1008 0 p1 R+ 7:36AM 0:00.00 grep spamd >(ksh) Now this is funny, as my spamlogd runs ar root.
# ps aux | grep spam _spamd 6455 ... 3:20PM 1:23.34 spamd: (pf <spamd-white> update) (spamd) _spamd 26548 ... 3:20PM 0:05.24 /usr/libexec/spamd -v -g _spamd 21456 ... 3:20PM 0:00.00 spamd: (/var/db/spamd update) (spamd) root 6596 ... 3:21PM 0:01.31 /usr/libexec/spamlogd This is OpenBSD 4.0-stable (GENERIC) with all 4.0 patches applied. I've just checked on working spamd setup (with greylisting enabled) on 3.9-stable box spamlogd also runs as root. $ cat /etc/rc | grep "\$OpenBSD" # $OpenBSD: rc,v 1.290 2006/09/01 01:18:02 mpf Exp $ $ cat /etc/rc.conf | grep "\$OpenBSD" # $OpenBSD: rc.conf,v 1.116 2006/06/02 21:32:50 mcbride Exp $ Though I'm pretty sure that spamlogd doesn't have anything to do with my my problems, whitelisting outgoing connections is next step to do. p.
