Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <40085BFA.ECDC330@dessent.net> Date: Fri, 16 Jan 2004 13:47:38 -0800 From: Brian Dessent Organization: My own little world... MIME-Version: 1.0 To: "'cygwin'" Subject: Re: deleting a file ending with a dot References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host.linuxsv3.net X-AntiAbuse: Original Domain - sources.redhat.com X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - dessent.net X-IsSubscribed: yes Reply-To: cygwin@cygwin.com Dave Korn wrote: > > David T-G wrote: > > > > > > [Does anyone know why this thread is showing up in my inbox > > instead of > > > being properly filtered? Has there been a list address change?] > > > > > Do you have your filters set to recognize both > > cygwin@cygwin.com and cygwin@sources.redhat.com? Both > > addresses get to this list. > > My filters failed today for just the same reason. I've decided that > checking for "cygwin-owner" in the From: field is probably most effective. I find it's always much more reliable to filter on one of the mailing list headers that the software adds. For this list I have a rule that checks that the "Mailing-List:" header contains "cygwin". Some lists use "List-ID:" or "X-Mailing-List:" so you have to look at the raw source. But doing it this way is very reliable, and doesn't depend on any of the TO or CC or FROM fields which can sometimes be weird (like if someone BCC'd the list or whatever.) Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/