From: Jim Meyering <jim@meyering.net>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: overseers@gcc.gnu.org
Subject: Re: Email to gcc-patches@gcc.gnu.org is treated as SPAM
Date: Fri, 17 Aug 2012 10:16:00 -0000 [thread overview]
Message-ID: <87a9xt7ri1.fsf@rho.meyering.net> (raw)
In-Reply-To: <CAMe9rOok-E7UzTsLk8p_fcaUi=fwN8b4RS415CFpZfb86_WPVQ@mail.gmail.com> (H. J. Lu's message of "Thu, 16 Aug 2012 09:59:30 -0700")
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 <mailer-daemon@googlemail.com>
> 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" <hjl.tools@gmail.com>
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.
prev parent reply other threads:[~2012-08-17 10:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 16:59 H.J. Lu
2012-08-16 17:27 ` Christopher Faylor
2012-08-17 10:16 ` Jim Meyering [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a9xt7ri1.fsf@rho.meyering.net \
--to=jim@meyering.net \
--cc=hjl.tools@gmail.com \
--cc=overseers@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).