>with the number of IP addresses authorized by the SPF2 record, and
>even for domains which only authorize a very few IP addresses, we'll
>have no practical way (except manual processing of requests) to
>correct outdated blacklist listings.
A lookup to IADB, which is an accreditation database rather than a
blacklist or a whitelist, can (and will for listed IP addresses) give
you enough information to determine whether the blacklist listing
should be decreased in weight or even overridden. That information
includes, among other things, the opt-in level of the mailing list mail
which comes from that IP address, and whether that IP address is listed
in Bonded Sender or Habeas. If an IADB-listed IP address returns a
code indicating that all mailing list mail coming from that IP address
is, for example, confirmed-opt-in, that's useful information in the
face of the IP address also appearing on a blacklist.
SPF publishers who are also listed in IADB include the
"accredit=%{ir}.iadb.isipp.com" in their SPF records; I assume it would
be the similar for SPF2. The information returned from an IADB query
includes whether an SPF record is published for that IP, so there is a
closed loop there - if you check SPF first, you'll know that the IP is
listed in IADB and you can get more info there - if you check IADB
first, you'll know that there is an SPF record for that IP address.
Some receivers prefer to do their lookups to IADB2 rather than IADB -
IADB2 provides an aggregated weighted score rather than, but based on,
the individual bits of information.
(http://www.isipp.com/iadb.php)
Anne
Anne P. Mitchell, Esq.
President/CEO
Institute for Spam and Internet Public Policy
Professor of Law, Lincoln Law School of SJ
Committee Member, Asilomar Microcomputer Workshop