RE: Kill Verisign Routes :: A Dynamic BGP solution

["Eric Germann" <ekgermann () cctec com>]

Which is fine with me/my client base.  Since what they are doing is
essentially a MITM attack, the client base I serve and I would rather have
the mail sit in OUR spools for a couple of days, vs. bouncing immediately
with the potential of the mail addresses being harvested.  Also, from the
perspective of our "sensitive clients", they would like mistyped URL's with
parameters to be errored out on the browser side, vs being dumped to a
Verisign server with the parameters (potentially usernames/passwords, etc)
possibly ending up in their logs.

Also, whats to keep Verisign from changing the behavior of their mail spool?
Right now, its questionable how it rejects.  It would make a neat project to
make a server that accepted the whole message, and THEN bounced it after it
was all spooled/logged.  Verisign do something like that?  Nahhh, not our
beloved Verisign ....

Eric


> -----Original Message-----
> From: Stephen J. Wilcox [mailto:steve () telecomplete co uk]
> Sent: Thursday, September 18, 2003 6:51 PM
> To: Eric Germann
> Cc: nanog () nanog org
> Subject: Re: Kill Verisign Routes :: A Dynamic BGP solution
<snip>

> So totallymadeupdomain.com now resolves but is unreachable. That
> will prevent
> you from bouncing emails to non-existent domains immediately..
>
> Steve