On Sep 28, 2006, at 1:39 AM, Rickard Borgmdster wrote:
If that is the case, it's terrific :-) But it still doesn't take
care of
the "fastlane", so that whitelisted host doesn't have to go trough the
greylist process. Or does it?
That's because the "fastlane" is a separate issue. If you want a
specific host to avoid the greylisting process, as well as a larger
blacklist entry, use the spamdb (8) command to add a whitelist entry
for it. The whitelist entry in spamd.conf will ensure that your host
doesn't go into the blacklist table, and manually whitelisting it
with spamdb will bypass the greylisting process.
Incidentally, if you want to set up a list of networks that never hit
spamd, you can do that in pf. The following snippet comes from my
pf.conf, with the mail server running on the same box. The
"nogreylist" file contains a list of networks that use mail server
farms, which have trouble greylisting because they regularly use
different IPs -- a partial list can be found at www.greylisting.org.
It also contains mail servers that run Symantec AV Gateway and other
clueless software that won't retry when presented with a 451.
table <nospamd> persist file "/etc/mail/nogreylist"
no rdr on $ext_if proto tcp from <nospamd> to port smtp
Steve
