public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Matthias Klose <doko@debian.org>
To: overseers@sourceware.org
Subject: emails to gcc-testresults rejected as spam
Date: Mon, 13 Nov 2017 18:31:00 -0000	[thread overview]
Message-ID: <5a2b4150-6961-cd02-f233-b4b37691d478@debian.org> (raw)
In-Reply-To: <E1eEIwr-00012R-Ve@mailly.debian.org>

[-- Attachment #1: Type: text/plain, Size: 883 bytes --]

Hi,

just recently, I see a lot of reject messages when reporting test results to
gcc-testrsults.  Looking at the messages these are a few hundred lines long,
having a lot of failures in the quality tests. But it's not spam.

How can I safely send these messages?

Thanks, Matthias



-------- Forwarded Message --------
Subject: Mail delivery failed: returning message to sender
Date: Mon, 13 Nov 2017 17:55:05 +0000
From: Mail Delivery System <Mailer-Daemon@mailly.debian.org>
To: doko@coccia.debian.org

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  gcc-testresults@gcc.gnu.org
    host gcc.gnu.org [209.132.180.131]
    SMTP error from remote mail server after end of data:
    552 spam score exceeded threshold


[-- Attachment #2: Attached Message Part --]
[-- Type: message/delivery-status, Size: 207 bytes --]

[-- Attachment #3: Attached Message Part --]
[-- Type: text/rfc822-headers, Size: 1089 bytes --]

Return-path: <doko@coccia.debian.org>
Received: from coccia.debian.org ([2001:41c8:1000:21::21:11])
	from C=NA,ST=NA,L=Ankh Morpork,O=Debian SMTP,OU=Debian SMTP CA,CN=coccia.debian.org,EMAIL=hostmaster@coccia.debian.org (verified)
	by mailly.debian.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.89)
	(envelope-from <doko@coccia.debian.org>)
	id 1eEIwe-00011N-2u; Mon, 13 Nov 2017 17:54:52 +0000
Received: from doko by coccia.debian.org with local (Exim 4.89)
	(envelope-from <doko@coccia.debian.org>)
	id 1eEIwd-0006La-N4; Mon, 13 Nov 2017 17:54:51 +0000
To: gcc-testresults@gcc.gnu.org
Subject: Results for 6.4.0 20171112 (Debian 6.4.0-10) testsuite on powerpc64le-unknown-linux-gnu
Cc: debian-gcc@lists.debian.org
From: Matthias Klose <doko@debian.org>
Reply-To: Matthias Klose <doko@debian.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="ANSI_X3.4-1968"
Content-Transfer-Encoding: 8bit
Message-Id: <E1eEIwd-0006La-N4@coccia.debian.org>
Date: Mon, 13 Nov 2017 17:54:51 +0000
X-Exim-DSN-Information: Due to administrative limits only headers are returned



           reply	other threads:[~2017-11-13 18:31 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <E1eEIwr-00012R-Ve@mailly.debian.org>]

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=5a2b4150-6961-cd02-f233-b4b37691d478@debian.org \
    --to=doko@debian.org \
    --cc=overseers@sourceware.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).