From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 494 invoked by alias); 29 Oct 2003 18:15:15 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 487 invoked from network); 29 Oct 2003 18:15:15 -0000 Received: from unknown (HELO redhat.com) (66.187.230.200) by sources.redhat.com with SMTP; 29 Oct 2003 18:15:15 -0000 Received: by redhat.com (Postfix, from userid 201) id CC4C932A8A7; Wed, 29 Oct 2003 13:15:14 -0500 (EST) Date: Wed, 29 Oct 2003 18:15:00 -0000 From: Christopher Faylor To: amylaar@cs.tu-berlin.de, joern.rennecke@superh.com Cc: gdb@sources.redhat.com, gcc@gcc.gnu.org, overseers@sourceware.org Subject: Re: mail to gcc-testresults and gdb-patches disappearing Message-ID: <20031029181514.GD10292@redhat.com> Reply-To: overseers@sourceware.org Mail-Followup-To: amylaar@cs.tu-berlin.de, joern.rennecke@superh.com, gdb@sources.redhat.com, gcc@gcc.gnu.org, overseers@sourceware.org References: <200310291604.h9TG4CB21519@heute.cs.tu-berlin.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200310291604.h9TG4CB21519@heute.cs.tu-berlin.de> User-Agent: Mutt/1.4.1i X-SW-Source: 2003-10/txt/msg00326.txt.bz2 [reply-to set to overseers] On Wed, Oct 29, 2003 at 05:04:12PM +0100, Joern Rennecke wrote: >Mail that I have sent from my superh.com account to gcc-testresults and >gdb-patches in the last weeks has never appeared in the mailing list >archives. If you look at the below email: http://sources.redhat.com/ml/gdb-patches/2003-10/msg00651.html you'll see that it contains the entire header of your message. To me that indicates that there is probably a misconfiguration on your end. Other email has been blocked due to bad headers: X-OriginalArrivalTime Email with this type of header invariably comes from an email loop so it is not allowed. Since it is indicative of a loop, no indication of dropped email is given since it would just potentially contribute to the loop. So, it looks like you have something to fix on your end.