Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Sun, 22 Jul 2001 22:52:12 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: spam Message-ID: <20010722225212.E9168@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20010722224710 DOT A4471 AT ping DOT be> <3B5B4C13 DOT 1080303 AT ece DOT gatech DOT edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <3B5B4C13.1080303@ece.gatech.edu>; from cwilson@ece.gatech.edu on Sun, Jul 22, 2001 at 05:56:35PM -0400 On Sun, Jul 22, 2001 at 05:56:35PM -0400, Charles Wilson wrote: >In the past, cygwin used ORBS. But now we can't. We do use the ORBS replacements that have cropped up but they don't seem to be as effective as ORBS. >Thus the increase in spam. However, I haven't noticed multiple spams >from the same address (unless the multiples come VERY close together) >-- so I assume that someone -- probably cgf -- is manually blocking >each spammer. Perhaps not. Yep. I block every spam I see. In fact, if I see spam in binutils, I block it there and in many other mailing lists, including cygwin. So, the cgf spam coverage should be pretty good. However, when I am on vacation or away from the computer (a regrettably rare event) you may see some spam flitting by. I would suggest that the best response to spam is to send email to the *proper* place, i.e. the originating site. Sending a "why doesn't someone do something about this" response is just, as Chuck says, adding to the annoyance. The only thing that I hate more than spam itself is the responses to spam. It's like yelling at someone in the library because they were talking too loudly. cgf -- 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/