Indeed relay.verizon.net does ping but no tcp answer. However ping doesn't give us an accurate result if it's really the IP of relay.verison.net which answers. It seems to be but we cannot be sure.
And an icmp traceroute doesn't go further than 206.46.128.78 either, like tcp requests.
On Sat, 1 Jan 2005 16:39:27 +0000
Russell King <rmk+exim@???> wrote:
> On Sat, Jan 01, 2005 at 09:52:14PM +0530, Suresh Ramasubramanian wrote:
> > Nikademus wrote:
> > > Got the same problem as you in Belgium:
> > >
> > > traceroute 206.46.170.12
> > > 14 gigchannel9-0--12-0.core1.dfw-tx.vzlink.com (206.46.128.78) 117.483 ms 117.168 ms 116.729 ms
> > > 15 * * *
> >
> > http://www.aunty-spam.com/archives/2004/12/31/inside-source-says-verizon-bisb-blocking-inbound-email-from-non-us-sites/
> >
> > This is something I googled up. I don't know how true or not it is ..
>
> That article appears to contain no new information which the other URL in
> this thread already gave us.
>
> I've also tried tcptracerouting a selection of ports at relay.verizon.net
> as well - same thing. TCP and UDP seem to stop at the above router, but
> ICMP does work (it pings). So it appears that either there's deliberate
> blackholing off of all UDP and TCP connections.
>
> --
> Russell King
>
--
Nikademus
http://www.octools.com
.O.
..O
OOO
Please avoid sending me Word or PowerPoint attachments.
See
http://www.fsf.org/philosophy/no-word-attachments.html
