public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: Jason Molenda <jason-gcclist@molenda.com>
Cc: overseers@gcc.gnu.org
Subject: Re: Anti-Spam: honoring gnu.org's X-Spam-Status
Date: Thu, 20 Feb 2003 13:51:00 -0000	[thread overview]
Message-ID: <Pine.BSF.4.51.0302201443470.29729@naos.dbai.tuwien.ac.at> (raw)
In-Reply-To: <20030220011659.B78691@molenda.com>

On Thu, 20 Feb 2003, Jason Molenda wrote:
> Hm, looks like the folks at gnu.org have spamassassin jacked in to
> their MTA.

Yup.

>> Would it be hard to honor this header and refuse such messages?
> I can't remember a facility for doing that in normal ezmlm, but
> I'm sure we could cook something up.  But every note relayed through
> gcc@gnu.org is going to have that header.   Your e-mail had this
> header when it got through my own spamassassin filter:
>
>   X-Spam-Status: No, hits=0.3 required=7.0

Yeah, but mine has X-Spam-Status: No ;-), while I was suggesting to
filter based on X-Spam-Status: Yes.

> This part I don't really understand.  Your mail system generated
> a bounce because of an X-* header?  Or your mail system detects
> the spamassassin spam-level markers and bounces the note?

The former.  (Well, actually not the core mail system, but my procmail
recipes where I filter for X-Spam headers added by the gnu.org servers;
the spam ratio for my gerald@gnu.org address is way above 95%. :-( )

Gerald
-- 
Gerald "Jerry"   pfeifer@dbai.tuwien.ac.at   http://www.pfeifer.com/gerald/

  reply	other threads:[~2003-02-20 13:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-20  8:54 Gerald Pfeifer
2003-02-20  9:17 ` Jason Molenda
2003-02-20 13:51   ` Gerald Pfeifer [this message]
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.0302201443470.29729@naos.dbai.tuwien.ac.at \
    --to=pfeifer@dbai.tuwien.ac.at \
    --cc=jason-gcclist@molenda.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).