From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: overseers@gcc.gnu.org
Subject: Anti-Spam: honoring gnu.org's X-Spam-Status
Date: Thu, 20 Feb 2003 08:54:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.51.0302200950080.6817@naos.dbai.tuwien.ac.at> (raw)
The following message (injected to gcc@gcc.gnu.org via gcc@gnu.org)
carried a X-Spam-Status: Yes added by the gnu.org mail system.
Would it be hard to honor this header and refuse such messages?
(I noticed it, because my own mail system then generated a bounce
based on that header, which in turn caused ezml to warn...)
Gerald
---- message ----
Return-Path: <gcc-return-67756-pfeifer=dbai.tuwien.ac.at@gcc.gnu.org>
Received: from sources.redhat.com (sources.redhat.com [66.187.233.205])
by vexpert.dbai.tuwien.ac.at (8.12.6/8.12.6) with SMTP id h18BwQFB025935
for <pfeifer@dbai.tuwien.ac.at>; Sat, 8 Feb 2003 12:58:26 +0100 (CET)
Received: (qmail 1213 invoked by alias); 8 Feb 2003 11:58:05 -0000
Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:gcc-unsubscribe-pfeifer=dbai.tuwien.ac.at@gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc/>
List-Post: <mailto:gcc@gcc.gnu.org>
List-Help: <http://gcc.gnu.org/ml/>
Sender: gcc-owner@gcc.gnu.org
Delivered-To: mailing list gcc@gcc.gnu.org
Received: (qmail 1186 invoked from network); 8 Feb 2003 11:57:59 -0000
Received: from unknown (HELO fencepost.gnu.org) (199.232.76.164)
by 172.16.49.205 with SMTP; 8 Feb 2003 11:57:59 -0000
Received: from monty-python.gnu.org ([199.232.76.173])
by fencepost.gnu.org with esmtp (Exim 4.10)
id 18hTcK-0003Ri-00
for gcc@gnu.org; Sat, 08 Feb 2003 06:57:56 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
id 18hTZM-0005pJ-00
for gcc@gnu.org; Sat, 08 Feb 2003 06:54:53 -0500
Received: from gnudist.gnu.org ([199.232.41.7])
by monty-python.gnu.org with esmtp (Exim 4.10.13)
id 18hTXc-0005Wc-00
for gcc@gnu.org; Sat, 08 Feb 2003 06:53:04 -0500
Received: from 66-178-47-198.reverse.newskies.net ([66.178.47.198] helo=helimore617.com)
by gnudist.gnu.org with smtp (Exim 4.10.13)
id 18hTXY-0005Ak-00
for gcc@gnu.org; Sat, 08 Feb 2003 06:53:01 -0500
From: "Mr. Charles Ugboko," <ccdas@yahoo.com>
Reply-To: mrcharles_ugboko@mailsurf.com
To: gcc@gnu.org
Date: Sat, 8 Feb 2003 12:52:46 +0100
Subject: acknowledge
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-Id: <E18hTXY-0005Ak-00@gnudist.gnu.org>
X-Spam-Status: Yes, hits=11.4 required=5.0
tests=DEAR_SOMEBODY,DEAR_SOMETHING,FORGED_YAHOO_RCVD,
LINES_OF_YELLING,MIME_LONG_LINE_QP,NIGERIAN_TRANSACTION_2,
RATWARE_OE_MALFORMED,SPAM_PHRASE_05_08,SUPERLONG_LINE,
US_DOLLARS,US_DOLLARS_3
version=2.41
X-Spam-Flag: YES
X-Spam-Level: ***********
X-Spam-Checker-Version: SpamAssassin 2.41 (1.115.2.8-2002-09-05-exp)
X-Spam-Report: 11.40 hits, 5 required;
* 4.4 -- X-Mailer contains malformed Outlook Express version
* -1.0 -- BODY: Contains 'Dear Somebody'
* 2.6 -- BODY: Nigerian scam key phrase (million dollars)
* 2.1 -- BODY: Nigerian scam key phrase ($NN,NNN,NNN.NN)
* 1.0 -- BODY: Contains 'Dear (something)'
* 0.1 -- BODY: illegal Nigerian transactions (2)
* 0.7 -- BODY: Spam phrases score is 05 to 08 (medium)
[score: 6]
* 0.3 -- BODY: A WHOLE LINE OF YELLING DETECTED
* -2.2 -- BODY: Contains a line >=199 characters long
* 2.0 -- RAW: Quoted-printable line longer than 76 characters
* 1.4 -- 'From' yahoo.com does not match 'Received' headers
next reply other threads:[~2003-02-20 8:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-20 8:54 Gerald Pfeifer [this message]
2003-02-20 9:17 ` Jason Molenda
2003-02-20 13:51 ` Gerald Pfeifer
2003-02-20 18:18 ` Jason Molenda
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=Pine.BSF.4.51.0302200950080.6817@naos.dbai.tuwien.ac.at \
--to=pfeifer@dbai.tuwien.ac.at \
--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).