Weirdest email evuh

A couple of weeks back I posted to a verizon group laughing at Verizon's inability to route traffic from one Verizon DSL connection to another, whereas the rest of the world could see both systems happily. Today I got this most weird email response...

I'm guessing some virus gone mad, but there was no payload!

(some received lines removed)

From bballluva@verizon.net  Mon Jun 13 11:50:01 2005
Return-Path: <bballluva@verizon.net>
Received: from vms044pub.verizon.net (vms044pub.verizon.net [206.46.252.44])
        by linode.spuddy.org (Postfix) with ESMTP id 680841C7E9
        for <xxxx@spuddy.org>; Mon, 13 Jun 2005 11:49:53 -0400 (EDT)
Received: from oemcomputer ([141.157.222.185])
 by vms044.mailsrvcs.net (Sun Java System Messaging Server 6.2 HotFix 0.04
 (built Dec 24 2004)) with ESMTPA id <0II10053N5B4A1E7@vms044.mailsrvcs.net> for
 XXXX@spuddy.org; Mon, 13 Jun 2005 10:49:53 -0500 (CDT)
Date: Mon, 13 Jun 2005 11:48:58 -0400
From: "Charice Williamson" <bballluva@verizon.net>
Subject: Re: Verizon unable to route to verizon
To: "Stephen Harris" <xxxx@spuddy.org>
Message-id: <000401c5702f$70ad3320$2f01a8c0@myhome.westell.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7bit
X-Priority: 3
X-MSMail-priority: Normal
References: <039b7d.5v3.ln@spuddy.org>
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pugwash.mew.co.uk
X-Spam-Level: 
X-Spam-Status: No, hits=0.2 required=4.0 tests=RCVD_IN_NJABL,RCVD_IN_SORBS 
        autolearn=no version=2.63
Status: RO
Content-Length: 1467
Lines: 51


Part of DSL is to have a phone, a DSL fliter or a Wall Mount DSL fliter, a
Video game system or a Computer, an Ethernet connection or an USB
connection, a Power cord, an eletrecial outlet, a Phone line, a Phone jack
and A DSL modem or gate-way.

Hello!
----- Original Message -----
From: "Stephen Harris" <xxxx@spuddy.org>
Newsgroups: 0.verizon.adsl
Sent: Saturday, May 28, 2005 10:30 PM
Subject: Verizon unable to route to verizon


> I'm at my girlfriend's and am trying to reach my home machine.  A
> traceroute:
>
>
>   1    <1 ms    <1 ms    <1 ms  10.0.0.1
>   2     8 ms     8 ms     8 ms  10.5.65.1
>   3     8 ms    12 ms     8 ms  130.81.10.49
>   4  so-7-2-0-0.BB-RTR2.NWRK.verizon-gni.net [130.81.18.74]  reports:
Destination net unreachable.
>
> Trace complete.
>
>
> Not useful!
>
> However, if I log into a machine I have on teh west coast (an Linode)
> _that_ can see my home machine just fine, so my DSL works.
>
> How silly; Verizon can't talk to Verizon, but other people can!
>
> The route has been bouncing around most of today.  It's back now.  I
> wonder how long it will be before it drops again.
>
> --
>                                  Stephen Harris
>                            An Englishman in New York
 You might need to move from one place to the other for your DSL to work
properly.

 I'ts a good idea to complete a trace-route and ping your address
                  Sorry!

I love you very much!

Good-bye!

From: Vander Eubanks