spamlogd not only needs to be running, but it needs to

see the connections - your pf rules need to log them correctly.
	The best way to see if this is happening is to fire

off some debug level syslogging, and see if spamlogd is logging lines

for the hosts that connect in. You should see lines like this where

your debug level syslogs are going.
Sep 13 07:03:49 mailcarp1 spamlogd[16523]: inbound 199.185.137.3
	if you don't spamlogd ain't seeing them. check your pf rules.
* Juan Miscaro  [2007-09-13 09:38]:

quoted text
> My OpenBSD 4.0 mail filter (running amavisd-new) has been up and

> running well for 70 days.  I received a complaint of delays this

> morning.  Indeed, I see that servers which had been whitelisted by

> spamd were no longer so.  I verified that spamlogd is still running.

> Does anyone have any ideas how this could have happened?

>

> - Juan

>

>

>       Ask a question on any topic and get answers from real people. Go to Yahoo! Answers and share what you know at http://ca.answers.yahoo.com

> 

--

#!/usr/bin/perl

if ((not 0 && not 1) !=  (! 0 && ! 1)) {

   print "Larry and Tom must smoke some really primo stuff...\n";

}