Update on Querying IADB

Mailman List Mirror (Read Only)
1

For those interested in seeing how this has evolved, and what exactly this particular accreditation database provides, our query pages have been expanded, and include a link to the full suggested DNSL data response codes.

The codes we use at present include:

127.0.0.1 Listed in IADB
127.0.1.255 Vouched listing
127.2.255.1 Publishes SPF record
127.2.255.2 Publishes Microsoft "Caller I.D. for Email" record
127.2.255.101 Participates in Habeas program
127.2.255.102 Participates in Ironport's Bonded Sender program
127.3.100.0 Has absolutely no mailing controls in place
127.3.100.1 Scrapes addresses, pure opt-out only
127.3.100.2 Accepts unverified sign-ups such as through web page
127.3.100.3 Accepts unverified sign-ups, gives chance to opt out
127.3.100.4 Reserved
127.3.100.5 Has opt-in confirmation mechanism
127.3.100.6 Has and uses opt-in confirmation mechanism
127.3.100.7 Reserved
127.3.100.8 Reserved
127.3.100.9 Reserved
127.3.100.10 All mailing list mail is confirmed opt-in

The general information is at http://www.isipp.com/iadb.php
Query information specifically is at http://www.isipp.com/iadbquery.php

It is, of course, free to query IADB, as well as to be listed as an individual.

Anne

2

Hmm.. this is loads of fun if you're running a Listserv that has several
thousand lists defined, and not all of them have the same policies (for
instance, although the vast majority of our lists are 'confirmed opt-in', we
have several lists that are bulk-loaded with database extracts for "captive
audience" lists such as "all freshmen", "all grad students", and so on).

Also, the pricing seems a bit whacked - are you *really* expecting sites that
have less than 30 customers to pay $200/month? I know a *lot* of people
who have formed collectives of 10-15 people who chip in and get a 1U at
a colo....

It's totally unclear how you can encode an "individual" listing - that
whole "stuff to the left of the @ sign" thing is rather unhandy...

I'll skip the estimates of the cash flow generated if the database gets big
enough to be useful, but I suspect that Verisign might have competition....

3

Also, the pricing seems a bit whacked - are you *really* expecting sites that
have less than 30 customers to pay $200/month? I know a *lot* of people
who have formed collectives of 10-15 people who chip in and get a 1U at
a colo....

They are not email service providers; if you are talking about a site which only publishes non-commercial mailing lists, they would probably fall under the "newsletter publisher" rate, which is $10.00/month.

Anne

4

> 127.3.100.3 Accepts unverified sign-ups, gives chance to opt out

> 127.3.100.5 Has opt-in confirmation mechanism
> 127.3.100.6 Has and uses opt-in confirmation mechanism

> 127.3.100.10 All mailing list mail is confirmed opt-in

Hmm.. this is loads of fun if you're running a Listserv that has
several thousand lists defined, and not all of them have the same
policies (for instance, although the vast majority of our lists are
'confirmed opt-in', we have several lists that are bulk-loaded with
database extracts for "captive audience" lists such as "all freshmen",
"all grad students", and so on).

In a case like this we would list any IPs from which *only* come
confirmed lists separately, so that they would get the 127.3.100.10
listing. Otherwise we would look at the lowest common denominator
and use that data code response.

Also, the pricing seems a bit whacked - are you *really* expecting
sites that have less than 30 customers to pay $200/month? I know a
*lot* of people who have formed collectives of 10-15 people who chip
in and get a 1U at a colo....

I've already answered this on the fly, separately, but it bears
repeating. If you are talking about non-commercial mailing lists,
that would probably qualify for the newsletter publisher rate, which
is only $10/month.

It's also critical that people understand that you are now talking
about *being listed* in IADB, not about querying IADB, which is
always free (We've heard from at least one list member who thought
these rates being talked about were to *query* the list).

It's totally unclear how you can encode an "individual" listing - that
whole "stuff to the left of the @ sign" thing is rather unhandy...

Are you asking about "is there a data response code for "individual"?
There *could* be, but we determined that in the scheme of things
which most receiving systems care about, it doesn't matter. What
matters is the type of mail they send.

Anne