>> On Jan 21, 2016, at 11:35 AM, Michael Wise <[email protected]> >> wrote: >> >> Back In The Day, there was a BCP for shutting down a DNSBL that included >> running a daily check of the IP 127.0.0.1 (which should never hit), IIRC, as >> well as 127.0.0.2 (which should always return a hit); and if my memory >> serves, if either criteria was different (both listed or neither listed), >> the DNSBL should be flagged as not to be trusted. >> >> This is from memory, I remember a discussion … a decade or so ago? > > It's an obviously sensible thing to do, simple, cheap and doesn't require any > cooperation from the DNSBL operator more than all (but three) DNSBLs I know > of already do. > > IIRC it's explicitly called out as something you can do in Chris and Matt's > DNSBL RFC. > > I don't know of anyone who implemented it.
Heh..Steve, IIRC, are you the one who has a great story about listing the entire net on a DNSBL? ;~) I love that story. :~) Anne Anne P. Mitchell, Attorney at Law CEO/President, SuretyMail Email Reputation Certification Is Email You Send Being Junked? Get to the Inbox Using Your Own Mail System! http://www.SuretyMail.com/ http://www.SuretyMail.eu/ "Email marketing is the one place where it's better to ask permission than forgiveness." - Me Author: Section 6 of the CAN-SPAM Act of 2003 (the Federal anti-spam law) Member, California Bar Cyberspace Law Committee Member, Colorado Cybersecurity Consortium Ret. Professor of Law, Lincoln Law School of San Jose 303-731-2121 | [email protected] | @AnnePMitchell Facebook/AnnePMitchell | LinkedIn/in/annemitchell _______________________________________________ mailop mailing list [email protected] https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
