RE: National Do Not Call Registry has opened

*sigh* So why did Richard Callahan even bother soliciting advice the first
place? They are demonstrating they have no concern in operating a decent
mail system, even after many kind folks here provided them all the info they
needed.

I've had two confirmations dropped so far today. Bad in-addr and 'click
here' seem to have tipped the scales.

To save you all some keystrokes...
Donotcall.gov has no MX records. No reverse DNS on any of their outbound
mail boxes. And they obviously are not processing bounces/complaints/etc.
since nothing on that netblock has port 25 open.

  -Mike

*sigh* So why did Richard Callahan even bother soliciting advice the first
place? They are demonstrating they have no concern in operating a decent
mail system, even after many kind folks here provided them all
the info they
needed.

I've had two confirmations dropped so far today. Bad in-addr and 'click
here' seem to have tipped the scales.

To save you all some keystrokes...
Donotcall.gov has no MX records. No reverse DNS on any of their outbound
mail boxes. And they obviously are not processing bounces/complaints/etc.
since nothing on that netblock has port 25 open.

Appears to be the case flying by... Not a very promising init of the
initiative,
also imho, let's hope our friends (techno-politically) mature their
baby/proposal
over time then.. or let's attempt alternative efforts.. :wink:

mh

Businesses that ask for email addresses know that a significant percentage
of people can't type their own email address correctly. Each of those
results in a bounce, or an undeliverable message sitting in an mqueue
somewhere. It would not surprise me if they also reduced their
Timeout.queuereturn to a few hours as well.

Dealing with the bounces would be a nightmare, they've already got their
handsful with the webservers and the outbound mail boxes.

Sameer

Yo Sameer!

To save you all some keystrokes...
Donotcall.gov has no MX records. No reverse DNS on any of their outbound
mail boxes. And they obviously are not processing bounces/complaints/etc.
since nothing on that netblock has port 25 open.

And you can bet that this "project" cost at least six figures, maybe
seven. As a taxpayer, I was quite disappointed to see IIS and Microsoft
SMTPSVC gluing this pile together. When I went in and registered last
night, I was surprised to see that it was so simple. There seemed to be
no protection against a bot coming in and mailbombing someone to death.
What a sad state this business is in.

Charles

I
was thinking more along the line of a bot submitting every possible
10 digit phone number. Do the nation a favor.

cheers,
nick

Businesses that ask for email addresses know that a significant percentage
of people can't type their own email address correctly. Each of those
results in a bounce, or an undeliverable message sitting in an mqueue
somewhere. It would not surprise me if they also reduced their
Timeout.queuereturn to a few hours as well.

Dealing with the bounces would be a nightmare, they've already got their
handsful with the webservers and the outbound mail boxes.

:wink:

mh

Which is, of course, what might happen with email addresses, if someone made the very bad decision to implement a plausible opt-out scheme for junk emails.

>I was thinking more along the line of a bot submitting every possible
>10 digit phone number. Do the nation a favor.

Which is, of course, what might happen with email addresses, if someone
made the very bad decision to implement a plausible opt-out scheme for
junk emails.

We had this discussion in Sweden a couple years back, in the operator
forum, and we more or less joked that wildcards with exception was
the only acceptable opt-out, where a domain holder might submit a
domain name and state "only those email accounts matched by "*.namn.se"
who opt out of my wildcard opt-out may be sent spam". At the time
I was working at the swedish TLD registry and immediately offered
"*.se" as wildcard, since that was "my domain". :wink:

We still have no such register. Or any register.