Tim Prince wrote: > Earthlink gave me immediate automatic acknowledgment that these were viruses > originated by one of their customers.
Sorry for the extra noise, but in case anyone's trying to track down the sources, I also got a message claiming to be from Christopher Faylor (though with the wrong address). It also went through Earthlink, as the headers show: =================================== Return-Path: <[EMAIL PROTECTED]> Received: from [internal addresses] Received: from falcon.mail.pas.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by [internal address] with ESMTP id g9DHPru13432 for <[EMAIL PROTECTED]>; Sun, 13 Oct 2002 13:25:53 -0400 (EDT) Received: from pool0355.cvx40-bradley.dialup.earthlink.net ([216.244.43.100] helo=HUNG) by falcon.mail.pas.earthlink.net with smtp (Exim 3.33 #1) id 180mXM-0004o6-00; Sun, 13 Oct 2002 10:28:21 -0700 From: Christopher Faylor <[EMAIL PROTECTED]> Subject: Re: bash 2.05a command completion spec bug MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----------4MNKIZZFJFEJXQK" Message-Id: <[EMAIL PROTECTED]> Bcc: Date: Sun, 13 Oct 2002 10:28:21 -0700 Content-Length: 69055 =================================== Here was the entire message (my company server apparently nabbed the actual virus on the way in, but I'm updating my antivirus just in case...): =================================== On Tue, Feb 12, 2002 at 09:29:28AM -0500, Jason Tishler wrote: >Command completion specs causes bash 2.05a specifically *and* Cygwin >in general to behave "poorly." By "poo =================================== -Jerry Williams -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/