[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
Mick Vaites wrote: > Unfortunately if someone has run a dictionary attack on a domain the number > of unwanted responses to locations that don't exist is a pain for everyone - > so you cannot win either way. No if you do it James's way - we all win. Which is why the best practice docs all recommend it. The dictionary attacks aren't an issue in that case. Where the spammer uses random addresses, and uses your domain, via a third party box, you'd only see bounces for genuine addresses at your domain. Marginally less resource intensive that feeding it to /dev/null ;) If you have /dev/null in your email configuration anywhere, I regard it as a failure. Although I do have one domain I forward to /dev/null, it is only for the purposes of logging how much spam would have been delivered. Since there are no email addresses that work in that domain (except postmaster@ of course!) and it is unlikely to be a mistype of an existing domain name, I don't regard that domain as "email". -- The Mailing List for the Devon & Cornwall LUG http://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/linux_adm/list-faq.html