[EMAIL PROTECTED] [17/03/04 17:34 +]:
> >The codes we use at present include:
> >127.0.0.1Listed in IADB
>
> Hmmm... listed in my /etc/hosts as well.
> Am I IADB compliant?
Am i missing something or isn't this a standard dns block / white list
implementation?
> > 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..
>The codes we use at present include:
>127.0.0.1Listed in IADB
Hmmm... listed in my /etc/hosts as well.
Am I IADB compliant?
It's interesting to see how everyone tries to
reinvent LDAP on top of DNS and/or BGP instead of
just using the LDAP protocol itself. Som
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 abo
On Wed, 17 Mar 2004 01:48:45 PST, "Anne P. Mitchell, Esq." <[EMAIL PROTECTED]> said:
> 127.3.100.3Accepts unverified sign-ups, gives chance to opt out
> 127.3.100.5Has opt-in confirmation mechanism
> 127.3.100.6Has and uses opt-in confirmation mechanism
> 127
thanks. but I use 127.0.0.0/8 for other stuff. Hope you don't mind.
> 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 c
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.1Listed in
