--- Bob Beck <[EMAIL PROTECTED]> wrote:
>
> 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 <[EMAIL PROTECTED]> [2007-09-13 09:38]:
> > 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?
Let it be known that everything was working in the past 70 days as well
as when I inspected the server due to the complaints. I simply lost a
lot of my dynamicallly whitelisted hosts (if not all of them; not
sure). So I am currently re-validating senders right now. I did find
a mention of possible corruption of the spamdb database in the
changelog for 4.1 -> 4.2:
RELIABILITY FIX: Bugs in spamd(8) could corrupt the database.
I'm not sure if I have fallen victim to this.
- Juan
Be smarter than spam. See how smart SpamGuard is at giving junk email the
boot with the All-new Yahoo! Mail at http://mrd.mail.yahoo.com/try_beta?.intl=ca
