From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: overseers@gcc.gnu.org, Aldy Hernandez <aldyh@redhat.com>
Subject: Re: Bounced messages to gcc-patches.
Date: Thu, 21 May 2015 02:00:00 -0000 [thread overview]
Message-ID: <20150521020042.GA4123@ednor.casa.cgf.cx> (raw)
In-Reply-To: <555D10BA.3070208@redhat.com>
On Wed, May 20, 2015 at 06:54:50PM -0400, Aldy Hernandez wrote:
>Hi folks.
>
>I sent a patch to gcc-patches today with the subject of "Re: [patch
>10/10] debug-early merge: compiler proper". The first time it was
>silently dropped, but at least one of the recipients received it just fine.
>
>It had a 97k patch, which I thought could be the problem (size??). I
>tried again with a gziped patch and this time I received:
>
> ----- The following addresses had permanent fatal errors -----
><gcc-patches@gcc.gnu.org>
> (reason: 552 spam score exceeded threshold)
>
> ----- Transcript of session follows -----
>... while talking to gcc.gnu.org.:
> >>> DATA
><<< 552 spam score exceeded threshold
>554 5.0.0 Service unavailable
>
>The headers files in the message that was sent back from gcc.gnu.org did
>not have any indication as to why the spam socre was exceeded.
>
>Are my messages in limbo somewhere? Can they be released?
>
>Can I do anything to post my patch, or is this a subtle hint that should
>I consider vacation and/or retirement?
You really didn't give enough context to figure out what was responsible
for the bounce. I don't see anything unusual bounced as spam with a
redhat.com message-id.
I've added you to the whitelist but, in the future, if you have issues
please think about how you'd like to receive a bug report about a
compiler problem. I need details like time, date, message-contents
what email addres it was sent from and, if possible what the message-id
was.
prev parent reply other threads:[~2015-05-21 2:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 22:55 Aldy Hernandez
2015-05-21 2:00 ` Christopher Faylor [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=20150521020042.GA4123@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@sourceware.org \
--cc=aldyh@redhat.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).