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
Juan Miscaro wrote:
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
Juan Miscaro [EMAIL PROTECTED] writes:
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?
Whitelist entries do expire after a while (a little more
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
On Thu, Sep 13, 2007 at 10:29:02AM -0400, Juan Miscaro wrote:
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
--- 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
6 matches
Mail list logo
