From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16137 invoked by alias); 17 Aug 2012 10:16:55 -0000 Received: (qmail 16128 invoked by uid 22791); 17 Aug 2012 10:16:53 -0000 X-SWARE-Spam-Status: No, hits=-3.3 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx.meyering.net (HELO mx.meyering.net) (88.168.87.75) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 17 Aug 2012 10:16:40 +0000 Received: from rho.meyering.net (rho.meyering.net [127.0.0.1]) by rho.meyering.net (Acme Bit-Twister) with ESMTP id 9C841600BC; Fri, 17 Aug 2012 12:16:38 +0200 (CEST) From: Jim Meyering To: "H.J. Lu" Cc: overseers@gcc.gnu.org Subject: Re: Email to gcc-patches@gcc.gnu.org is treated as SPAM In-Reply-To: (H. J. Lu's message of "Thu, 16 Aug 2012 09:59:30 -0700") References: Date: Fri, 17 Aug 2012 10:16:00 -0000 Message-ID: <87a9xt7ri1.fsf@rho.meyering.net> MIME-Version: 1.0 Content-Type: text/plain Mailing-List: contact overseers-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: , Sender: overseers-owner@sourceware.org X-SW-Source: 2012-q3/txt/msg00075.txt.bz2 H.J. Lu wrote: > My email to gcc-patches@gcc.gnu.org is treated as SPAM. > What do I need to do to send patches to gcc-patches@gcc.gnu.org? > > Thanks. > > > H.J. > ---------- Forwarded message ---------- > From: Mail Delivery Subsystem > Date: Thu, Aug 16, 2012 at 9:55 AM > Subject: Delivery Status Notification (Failure) > To: hjl.tools@gmail.com > > > Delivery to the following recipient failed permanently: > > gcc-patches@gcc.gnu.org > > Technical details of permanent failure: > Google tried to deliver your message, but it was rejected by the > recipient domain. We recommend contacting the other email provider for > further information about the cause of this error. The error that the > other server returned was: 552 552 spam score exceeded threshold > (#5.6.1) (state 17). > > ----- Original message ----- > > DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; > d=gmail.com; s=20120113; > h=mime-version:in-reply-to:references:date:message-id:subject:from:to > :cc:content-type; > bh=2oWs5OyGOUvL9a/KuEEsBDMdJisZxYqbwSSc/w4L7mw=; > b=Rtfu4gXPRrQ5BbOvEWlpgYnH/U98O3aJsCsU3cTnu+JiKdDVhCmzapWSS82F780UEV > EiHVMaXLfzlejB2uuF+ZQ3/3Wl3IL4X+PUM14ld0/unbHsNYkTKwzsBpV64puC0ZnZ2t > jREm0Wj4EoFvFE0OmpD8CLd6JpQV+Z4kpcVBw5oT5qTOQaQ4JWtMlYql28QXn0Kx8c+6 > IqqTzOZ7WC7qQ9euxkoYK5dC7xpXXBLZx4tZcFtnkIVDmJz4YCR5aIW/Jp8aCzzwCXon > ybQTdWa6BZUOIvQd45hmo1DWfU5G8nJ7F8FzWmajkX+8nk6w3XttQaWzxXKg8ScgoTlc > 2RPQ== ... > From: "H.J. Lu" I don't know about this case (don't even know if I have access to those logs on sourceware.org), but... I have seen a few false-positive rejections of messages sent by gmail due to spam-detecting rules that deny a recipient whose HELO address cannot be looked up. In at least one case I documented, google was using an address for which lookup failed, so my system rejected it as spam. I guess it could have been due to DNS propagation delay.