nws.charlie wrote:
I guess I'm one of the mail admin wannabe's... not by choice, but by
inheritance. It was turned over to me with almost zero training or
experience. :(
I found the initial posts clear, and had to wonder at some of the replies
myself! Just wanted to say thanks for posting the answer before I posted the
question. It shortened my head-bang session.
I guess the real problem comes from sites using appliances or commercial
solutions that use DNSBLs without the admins really realizing what this
means (some may even think the DNSBL is managed by the solution vendor).
The lesson for such vendors is that they must use some mechanism to
verify the "integrity" of their solutions (not everybody will update
their solution, so the check must be enabled since day 1). for instance,
a cron would qury the DNSBLs for 127.0.0.1 or the like, and if it is
listed, the DNSBL must be disabled.
This can be done on home grown setups as well.
