public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Matthew Galgoci <mgalgoci@redhat.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: law@redhat.com, <overseers@sources.redhat.com>
Subject: Re: [Fwd: failure notice]
Date: Tue, 18 Nov 2003 15:53:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0311181047120.4445-100000@lacrosse.corp.redhat.com> (raw)
In-Reply-To: <3FBA2F76.9040908@redhat.com>

On Tue, 18 Nov 2003, Andrew Cagney wrote:
> > In message <3FB8E7D2.6030203@redhat.com>, Andrew Cagney writes:
> >  >This is a multi-part message in MIME format.
> >  >--------------000300030405000306090207
> >  >Content-Type: text/plain; charset=us-ascii; format=flowed
> >  >Content-Transfer-Encoding: 7bit
> >  >
> >  >What triggers this?
> > Could be a content issue.  Hard to guess what it might be without any of
> > the content -- subject lines & message body in particular.  Our spam filters
> > are pretty aggressive (thank god :-)
> 
> I get that all the time.  This:
> 
> "Sorry, I've been told to reject your posts."
> 
> I believe is new?

I can see how ac131313 might be seen as a forged random spam by someone just glancing
at headers and quick on the trigger. Or perhaps some spammer has been forging a from of
ac131313@redhat.com. *shrug* I dunno.

It's spam like that this is causing us to look impliment whitelisting of valid @redhat.com 
email addresses at Red Hat.

Anyhow, I'm not sure how the spam filters on sources works, but someone ought to check if andrew's
address somehow got added to a blacklist and possibly whitelist his address.

-- 
Matthew Galgoci
System Administrator
Red Hat, Inc
919.754.3700 x44155

  reply	other threads:[~2003-11-18 15:53 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-17 15:23 Andrew Cagney
2003-11-18  7:48 ` law
2003-11-18 14:40   ` Andrew Cagney
2003-11-18 15:53     ` Matthew Galgoci [this message]
2003-11-18 16:18       ` Ian Lance Taylor
2003-11-18 16:28         ` Christopher Faylor
2003-11-18 16:16     ` Christopher Faylor
2003-11-18 16:23       ` Andrew Cagney
2003-11-18 16:33         ` Christopher Faylor
2003-11-18 16:16 ` Ian Lance Taylor
  -- strict thread matches above, loose matches on Subject: below --
2007-02-19 21:12 Mark Mitchell
2007-02-19 21:21 ` Christopher Faylor
2007-02-19 22:03   ` Mark Mitchell
2004-08-18 17:20 Corinna Vinschen
2004-08-18 17:44 ` Ian Lance Taylor
2004-08-18 17:54   ` Corinna Vinschen
2004-08-18 18:52     ` Ian Lance Taylor
2004-08-18 22:13       ` Ian Lance Taylor
2004-08-18 22:21       ` Corinna Vinschen
     [not found] <1066412429.25550.133.camel@doubledemon.codesourcery.com>
2003-10-17 17:58 ` root
2003-06-04  4:30 Joern Rennecke
2003-02-01  2:32 Robert Love
2003-02-01  2:53 ` Christopher Faylor
2002-08-16 20:19 Ulrich Drepper
2002-08-16 20:25 ` Christopher Faylor
2002-03-05 12:18 Joel Sherrill
2002-03-07 20:57 ` Andrew Cagney
2001-04-23 11:46 Jonathan Larmour
2001-04-23 11:50 ` Jonathan Larmour
2000-12-30  6:08 Stan Shebs
2000-07-07  8:56 ` Stan Shebs
2000-12-30  6:08 ` Jim Kingdon
2000-07-07  9:43   ` Jim Kingdon
2000-12-30  6:08   ` Chris Faylor
2000-07-07 15:30     ` Chris Faylor
2000-12-30  6:08     ` Jim Kingdon
2000-07-07 18:46       ` Jim Kingdon
2000-12-30  6:08       ` Chris Faylor
2000-07-07 19:05         ` Chris Faylor
2000-12-30  6:08 Jonathan Larmour
2000-08-30 11:12 ` Jonathan Larmour
2000-12-30  6:08 ` Jason Molenda
2000-08-30 11:32   ` Jason Molenda
2000-12-30  6:08   ` Jason Molenda
2000-08-30 12:03     ` Jason Molenda
2000-12-30  6:08     ` Chris Faylor
2000-08-30 12:37       ` Chris Faylor
2000-12-30  6:08       ` Jason Molenda
2000-08-30 13:15         ` Jason Molenda
2000-12-30  6:08         ` Chris Faylor
2000-08-30 13:45           ` Chris Faylor
2000-12-30  6:08         ` Jonathan Larmour
2000-08-30 13:51           ` Jonathan Larmour
2000-12-30  6:08           ` Chris Faylor
2000-08-30 14:01             ` Chris Faylor
2000-12-30  6:08             ` Jonathan Larmour
2000-08-30 14:13               ` Jonathan Larmour

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.LNX.4.44.0311181047120.4445-100000@lacrosse.corp.redhat.com \
    --to=mgalgoci@redhat.com \
    --cc=ac131313@redhat.com \
    --cc=law@redhat.com \
    --cc=overseers@sources.redhat.com \
    /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).