On Thu, Sep 13, 2007 at 10:29:02AM -0400, Juan Miscaro wrote:
As Craig & Peter mention, whitelisted server do expire. The defaults are
sensible, but do not apply for everyone. One server I deal with is one
such case, and I've increased the whitelist expiry in the -G option to
almost double the default. This has worked fine.
You should also check that you are logging in pf for port 25, and that
spamlogd is seeing it and updating the timestamps on your whitelist
entries.
--
Darrin Chandler | Phoenix BSD User Group | MetaBUG
dwchandler@stilyagin.com | http://phxbug.org/ | http://metabug.org/
http://www.stilyagin.com/ | Daemons in the Desert | Global BUG Federation
| Mariusz Kozlowski | [PATCH 01] kmalloc + memset conversion co kzalloc |
| Greg Kroah-Hartman | [PATCH 001/196] Chinese: Add the known_regression URI to the HOWTO |
| Vladislav Bolkhovitin | Re: Integration of SCST in the mainstream Linux kernel |
| Jeremy Allison | Re: [RFC] Heads up on sys_fallocate() |
git: | |
| Gerrit Renker | [PATCH 0/37] dccp: Feature negotiation - last call for comments |
| Natalie Protasevich | [BUG] New Kernel Bugs |
| David Miller | Re: [GIT]: Networking |
| Jeff Garzik | Re: [bug?] tg3: Failed to load firmware "tigon/tg3_tso.bin" |
