Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Content-Type: text/plain; charset="iso-8859-1" From: Tim Prince Reply-To: tprince AT computer DOT org To: "Gregg C Levine" , Subject: Re: Viruses being transported with cygwin messages Date: Sun, 13 Oct 2002 19:56:37 -0700 References: <006601c272eb$5750f680$855a580c AT who> <20021013191503 DOT GA976 AT redhat DOT com> <005c01c27322$0e97b1e0$9573580c AT who> In-Reply-To: <005c01c27322$0e97b1e0$9573580c@who> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20021014025638.DEBE72CB4F@inet1.ywave.com> On Sunday 13 October 2002 18:36, Gregg C Levine wrote: > Hello from Gregg C Levine > Okay. I'll agree with you on that notion, Christopher. No real arguement > there. Now as to about those messages? Are those actual messages? I'm > inclined to think not. And I'll be permanently deleting them from my > message store. I also reported the initial example to those cloddies at > Earthlink, I'll be surprised if they know what to do. > Earthlink gave me immediate automatic acknowledgment that these were viruses originated by one of their customers. -- Tim Prince -- 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/