Search Again:

Re: Working around Verisign power-grab?

From: Joe D''Andrea
Date: Tuesday, September 16, 2003
Time: 4:56:54 pm

At 6:32 PM -0500 9/16/03, Mia's Virtual Post Office wrote:
>...that is cause we are not using DNS. We just added a static route
>for 64.94.110.11 to a server on our network.. Much simpler, no
>collateral damage and very efficient. So to see this work you would
>need be on our network.

OK... so your users don't get Verisign's ad^h^hsearch page. Instead
of null routing it, why not route it to your own ad^h^hsearch page.

But there will be collateral damage for mistyped e-mail, no? If I'm
on your network and accidentally send an e-mail to
"me@nonexistantdomain.com" then that message will sit in your queue
attempting to be delivered until it expires. Under a correctly
configured system, I would get that message back as a bounce
immediately. That serves the purpose of letting me know that my
message didn't get through and it doesn't clog up your MTA.

The other collateral damage, which may or may not apply to you is
that SMTP servers that rely on Verify Return Path (SIMS, Communigate)
are not rendered useless as all return paths are valid. (at least for
.com and .net).

~joe

--
_______________________________________________________________
Joseph D'Andrea ~ http://www.west21.com/ ~ JoeDan@West21.com
WEST21.com Internet services for the 21st Century
webhosting ~ co-location ~ wireless access ~ WebCat programming



Messages In This Thread:



Return to Digital Point Solutions' Home Page