[MAILER-DAEMON@sources.redhat.com: failure notice]

[MAILER-DAEMON@sources.redhat.com: failure notice]

[Robert Schiele]

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

Hello.

Two comments about the mail attached:

1. Why does the system block the mail for the address 80.140.43.216 which is a
   dial-in, although I am sending the mail not directly but over a trustworthy
   non-open relay?

2. I have already send mail to
   global-allow-subscribe-rschiele=uni-mannheim.de@gcc.gnu.org multiple times
   (at least two times) a few months ago.  It seems that the blocking system
   is forgetting the registered addresses from time to time.  Is this
   intentional?

Robert

----- Forwarded message from MAILER-DAEMON@sources.redhat.com -----

Return-Path: MAILER-DAEMON@rumms.uni-mannheim.de
Received: from rumms.uni-mannheim.de [134.155.50.52]
	by localhost with IMAP (fetchmail-6.2.3)
	for robert@localhost (single-drop); Wed, 17 Dec 2003 07:05:34 +0100 (CET)
Received: from sources.redhat.com (sources.redhat.com [67.72.78.213])
	by rumms.uni-mannheim.de (8.12.10/8.12.10) with SMTP id hBH61xHx019129
	for <rschiele@uni-mannheim.de>; Wed, 17 Dec 2003 07:01:59 +0100 (MET)
Message-Id: <200312170601.hBH61xHx019129@rumms.uni-mannheim.de>
Received: (qmail 22809 invoked for bounce); 17 Dec 2003 06:01:51 -0000
Date: 17 Dec 2003 06:01:51 -0000
From: MAILER-DAEMON@sources.redhat.com
To: rschiele@uni-mannheim.de
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="1071640908sources.redhat.com1348851"
Subject: failure notice
X-Virus-Scanned: by amavisd-new
X-Spam-Status: No, hits=1.5 required=3.0
	tests=MAILER_DAEMON,MSG_ID_ADDED_BY_MTA_2,NO_REAL_NAME
	version=2.55
X-Spam-Level: *
X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp)
Status: RO
Content-Length: 2917
Lines: 71

Hi. This is the qmail-send program at sources.redhat.com.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

<gcc-patches@gcc.gnu.org>:
In an effort to cut down on our spam intake, we block email that is listed
by certain open-relay tracking services. Unfortunately you may have just
discovered the hard way that sometimes non-spam mail gets caught
accidentally.  In most cases you can clear this up by an upgrade to your
mail server or sometimes by getting an erroneous listing removed.
For more information about our use of these lists, see
  
    http://sources.redhat.com/lists.html#rbls
  
The IP number that I am denying mail from is 80.140.43.216
The list that you are on is DSBL.  See:
  
    http://dsbl.org/listing?80.140.43.216
  
for more information about this list and why you are on it.
 
 
If you are not a "spammer", we apologize for the inconvenience.
You can add yourself to the gcc.gnu.org "global allow list"
by sending email *from*the*blocked*email*address* to:
  
    global-allow-subscribe-rschiele=uni-mannheim.de@gcc.gnu.org
 
For certain types of blocks, this will enable you to send email without
being subjected to further spam blocking.  This will not allow you to
post to a list if you have been explicitly blocked, if you are posting
an off-topic message, if you are sending an attachment that looks like a
virus, etc.
 
Contact gcc-patches-owner@gcc.gnu.org if you have questions about this. (#5.7.2)

--- Enclosed are the original headers of the message.

Return-Path: rschiele@uni-mannheim.de
Received: (qmail 22786 invoked from network); 17 Dec 2003 06:01:43 -0000
Received: from unknown (HELO rumms.uni-mannheim.de) (134.155.50.52)
  by sources.redhat.com with SMTP; 17 Dec 2003 06:01:43 -0000
Received: from schiele.dyndns.org (p508C2BD8.dip.t-dialin.net [80.140.43.216])
	(authenticated bits=0)
	by rumms.uni-mannheim.de (8.12.10/8.12.10) with ESMTP id hBH61hHx019045
	for <gcc-patches@gcc.gnu.org>; Wed, 17 Dec 2003 07:01:43 +0100 (MET)
Received: by schiele.dyndns.org (Postfix, from userid 500)
	id 6B13E5CC77; Wed, 17 Dec 2003 07:01:41 +0100 (CET)
Date: Wed, 17 Dec 2003 07:01:41 +0100
To: gcc-patches@gcc.gnu.org
Subject: [PATCH] fix gcc_update to use libjava/libltdl/configure.ac
Message-ID: <20031217060140.GG15244@schiele.dyndns.org>
Mail-Followup-To: Robert Schiele <rschiele@uni-mannheim.de>,
	gcc-patches@gcc.gnu.org
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="l06SQqiZYCi8rTKz"
Content-Disposition: inline
User-Agent: Mutt/1.5.4i
From: Robert Schiele <rschiele@uni-mannheim.de>
X-Virus-Scanned: by amavisd-new

(Body suppressed)

--l06SQqiZYCi8rTKz--

----- End forwarded message -----

-- 
Robert Schiele			Tel.: +49-621-181-2517
Dipl.-Wirtsch.informatiker	mailto:rschiele@uni-mannheim.de

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [MAILER-DAEMON@sources.redhat.com: failure notice]

[Christopher Faylor]

[reply-to set]
On Wed, Dec 17, 2003 at 09:45:39AM +0100, Robert Schiele wrote:
>Two comments about the mail attached:
>
>1. Why does the system block the mail for the address 80.140.43.216 which is a
>   dial-in, although I am sending the mail not directly but over a trustworthy
>   non-open relay?

"The system" == DSBL.  You can ask them about this.

>2. I have already send mail to
>   global-allow-subscribe-rschiele=uni-mannheim.de multiple times
>   (at least two times) a few months ago.  It seems that the blocking system
>   is forgetting the registered addresses from time to time.  Is this
>   intentional?

Looking for "schiele" in the global allow list, it looks like you
subscribed to the global allow list once as:

schiele=pi3.informatik.uni-mannheim.de on Tue Apr  1 19:07:13 2003

and once as

rschiele=uni-mannheim.de today

Obviously, the mailing list software looks at those as two different addresses.

3. The correct email address for this type of query is mentioned in the bounce
message.

[MAILER-DAEMON@sources.redhat.com: failure notice]

[Daniel Jacobowitz]

Is the blacklisting acting up?  According to DSBL, that IP has never
been listed.

----- Forwarded message from MAILER-DAEMON@sources.redhat.com -----

Date: 20 Jan 2003 16:52:13 -0000
From: MAILER-DAEMON@sources.redhat.com
Subject: failure notice
To: drow@false.org

Hi. This is the qmail-send program at sources.redhat.com.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

<binutils@sources.redhat.com>:
In an effort to cut down on our spam intake, we block email that is listed
by certain open-relay tracking services. Unfortunately you may have just
discovered the hard way that sometimes non-spam mail gets caught
accidentally.  In most cases you can clear this up by an upgrade to your
mail server or sometimes by getting an erroneous listing removed.
For more information about our use of these lists, see
  
    http://sources.redhat.com/lists.html#rbls
  
The IP number that I am denying mail from is 65.125.64.184
The list that you are on is DSBL.  See:
  
    http://dsbl.org/listing.php?ip=65.125.64.184
  
for more information about this list and why you are on it.
 
 
If you are not actually a "spammer", you can add yourself to
the sources.redhat.com "global allow list" by sending email
*from*the*blocked*email*address* to:
  
    global-allow-subscribe-drow=false.org@sources.redhat.com
 
This will enable you to send email without being subjected to
further spam blocking.
  
If you are actually a spammer then you should think long and hard
about the people you are inconveniencing and come to the conclusion
that what you are doing is both highly annoying and immoral.
 
Contact binutils-owner@sources.redhat.com if you have questions about this. (#5.7.2)

--- Below this line is a copy of the message.

Return-Path: <drow@false.org>
Received: (qmail 17551 invoked from network); 20 Jan 2003 16:52:12 -0000
Received: from unknown (HELO crack.them.org) (65.125.64.184)
  by 172.16.49.205 with SMTP; 20 Jan 2003 16:52:12 -0000
Received: from nevyn.them.org ([66.93.61.169] ident=mail)
	by crack.them.org with asmtp (Exim 3.12 #1 (Debian))
	id 18ah2X-0001GW-00
	for <binutils@sources.redhat.com>; Mon, 20 Jan 2003 12:52:58 -0600
Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian))
	id 18af9q-0006yX-00
	for <binutils@sources.redhat.com>; Mon, 20 Jan 2003 11:52:22 -0500
Date: Mon, 20 Jan 2003 11:52:22 -0500
From: Daniel Jacobowitz <drow@mvista.com>
To: binutils@sources.redhat.com
Subject: Re: detect special mips64le dwarf2 line number length encoding
Message-ID: <20030120165222.GA26733@nevyn.them.org>
Mail-Followup-To: binutils@sources.redhat.com
References: <orfzrph0md.fsf@free.redhat.lsd.ic.unicamp.br> <20030119145937.GA15437@nevyn.them.org> <orlm1hf9zd.fsf@free.redhat.lsd.ic.unicamp.br> <20030120052604.GA21412@nevyn.them.org> <or4r83srp1.fsf@free.redhat.lsd.ic.unicamp.br>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <or4r83srp1.fsf@free.redhat.lsd.ic.unicamp.br>
User-Agent: Mutt/1.5.1i

On Mon, Jan 20, 2003 at 02:37:30PM -0200, Alexandre Oliva wrote:
> On Jan 20, 2003, Daniel Jacobowitz <drow@mvista.com> wrote:
> 
> > While I hate to dump more work on you, I would really rather we pursue
> > this than propogate the nonstandard IRIX approach to this.  I really
> > don't think it would be much of a difficulty.
> 
> Well, then, I can add this to my personal LINO to-do list, but I still
> think the patch must go in, at the very least for compatibility with
> mips64el binutils that have been out there for a while.  This change
> might look minor at first, but it actually fixes a linker crash, when
> it tries to find out the line number associated with a given address,
> to report a warning.  Object files created using the current tools are
> subject to this problem.  Then, whenever we switch to the standard
> format, everything will just keep on working, even in a
> backward-compatible way.

Nothing has ever used this non-standard format for little endian
before; AFAIK only SGI used it, and after they'd dropped much of their
little endian support.  This only affects the mips64el-linux target as
I understand it, since I thought that mips64el-elf would use the normal
notation.  So while I understand your point of view, "tools already out
there" is a bit of a bunk, since the mips64el-linux target is brand new
and has only been fully functional for a couple of weeks at best.  It
was contributed to GCC just days ago.

I'm not going to fight you on this, and I understand you've got too
much to do, and it's certainly good to prevent linker crashes even on
bad input; but I really think your argument is bogus and that we should
stop generating this form of debug info ASAP.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


----- End forwarded message -----

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

Re: [MAILER-DAEMON@sources.redhat.com: failure notice]

[Christopher Faylor]

On Tue, Nov 19, 2002 at 01:38:52PM -0800, Roland McGrath wrote:
>Ok, thanks.  I also meant the forward to imply a re-send of that message,
>since it was going to overseers, so please respond to that too (separately,
>CC'ing those other folks).  Btw, this will be a test of the CC: parsing. :-)

I'm not going to be doing anything with the glibc stuff.  I don't know who
set up the forwarding there but, with luck, someone else will reply about
that.

cgf

Re: [MAILER-DAEMON@sources.redhat.com: failure notice]

[Jason Molenda]

On Tue, Nov 19, 2002 at 12:38:53PM -0800, Roland McGrath wrote:


> > > I'm trying to access the libc mailing list archives for bug-glibc from
> > > <URL:http://sources.redhat.com/glibc/>, but the two last months seem
> > > to be missing.  The pages do not specify who to contact about the
> > > archives, so I decided to try to email you.
> > 
> > I have no idea how this is handled.  Roland, can you help?
> > 
> > > Is there something wrong with the archive, or is the mailing list
> > > dead?
> > 
> > The archive seems to have problems,
> 
> bug-glibc is a gnu.org mailing list, not a sources.redhat.com one.
> mail.gnu.org has some archives, though they are full of spam.  I hadn't
> noticed before now that sources.redhat.com had archives of it too.


To address the original concern, yes, you've correctly deduced all
the details.  I re-subscribed most of the gnu.org lists under
sources.redhat.com addresses when we noticed this last month, but
I missed bug-glibc.  I'll subscribe it tonight.  I'll probably be
too lazy to get mbox archives of the intervening months of traffic
and archive those, but hey, you never know. :-) :-)


Jason

Re: [MAILER-DAEMON@sources.redhat.com: failure notice]

[Roland McGrath]

Ok, thanks.  I also meant the forward to imply a re-send of that message,
since it was going to overseers, so please respond to that too (separately,
CC'ing those other folks).  Btw, this will be a test of the CC: parsing. :-)

Re: [MAILER-DAEMON@sources.redhat.com: failure notice]

[Christopher Faylor]

On Tue, Nov 19, 2002 at 12:38:53PM -0800, Roland McGrath wrote:
Content-Description: message body text
>Hey there.  AFAICT this spam detector is buggy because it doesn't notice
>more than one CC: header.  Maybe that's not RFC822 (I dunno off hand), but
>folks sure do it.

Yep, they do.  This is now fixed.  I hope.

Thanks,
cgf

[MAILER-DAEMON@sources.redhat.com: failure notice]

[Roland McGrath]

[-- Attachment #1: message body text --]
[-- Type: text/plain, Size: 167 bytes --]

Hey there.  AFAICT this spam detector is buggy because it doesn't notice
more than one CC: header.  Maybe that's not RFC822 (I dunno off hand), but
folks sure do it.


[-- Attachment #2: forwarded message --]
[-- Type: message/rfc822, Size: 4718 bytes --]

From: MAILER-DAEMON@sources.redhat.com
To: roland@redhat.com
Subject: failure notice
Date: 19 Nov 2002 20:29:20 -0000
Message-ID: <200211192005.gAJK5XP12511@mx1.redhat.com>

Hi. This is the qmail-send program at sources.redhat.com.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

<overseers@sources.redhat.com>:
Mail rejected: List address must be in To: or Cc: headers.
 
If you are not actually a "spammer", you can add yourself to
the sources.redhat.com "global allow list" by sending email to:
  
    global-allow-subscribe-roland=redhat.com@sources.redhat.com
 
This will enable you to send email without being subjected to
further spam blocking.
  
If you are actually a spammer then you should think long and hard
about the people you are inconveniencing and come to the conclusion
that what you are doing is both highly annoying and immoral.
 
Contact overseers-owner@sources.redhat.com if you have questions about this. (#5.7.2)

--- Below this line is a copy of the message.

Return-Path: <roland@redhat.com>
Received: (qmail 26764 invoked from network); 19 Nov 2002 20:29:19 -0000
Received: from unknown (HELO gateway.sf.frob.com) (64.163.212.31)
  by sources.redhat.com with SMTP; 19 Nov 2002 20:29:19 -0000
Received: from magilla.sf.frob.com (magilla.sf.frob.com [198.49.250.228])
	by gateway.sf.frob.com (Postfix) with ESMTP
	id 4567636DB; Tue, 19 Nov 2002 12:29:18 -0800 (PST)
Received: (from roland@localhost)
	by magilla.sf.frob.com (8.11.6/8.11.6) id gAJKTHC11780;
	Tue, 19 Nov 2002 12:29:17 -0800
Date: Tue, 19 Nov 2002 12:29:17 -0800
Message-Id: <200211192029.gAJKTHC11780@magilla.sf.frob.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
From: Roland McGrath <roland@redhat.com>
To: Andreas Jaeger <aj@suse.de>
Cc: Petter Reinholdtsen <pere@hungry.com>
Cc: overseers@sources.redhat.com
Subject: Re: libc mailing list archives broken?
In-Reply-To: Andreas Jaeger's message of  Tuesday, 19 November 2002 17:43:57 +0100 <u8smxx33xu.fsf@gromit.moeb>
X-Antipastobozoticataclysm: Bariumenemanilow

> Petter Reinholdtsen <pere@hungry.com> writes:
> 
> > Hello
> >
> > I'm trying to access the libc mailing list archives for bug-glibc from
> > <URL:http://sources.redhat.com/glibc/>, but the two last months seem
> > to be missing.  The pages do not specify who to contact about the
> > archives, so I decided to try to email you.
> 
> I have no idea how this is handled.  Roland, can you help?
> 
> > Is there something wrong with the archive, or is the mailing list
> > dead?
> 
> The archive seems to have problems,

bug-glibc is a gnu.org mailing list, not a sources.redhat.com one.
mail.gnu.org has some archives, though they are full of spam.  I hadn't
noticed before now that sources.redhat.com had archives of it too.

overseers@sources.redhat.com is the address to reach people who maintain
that system.  I've CC'd them in case they can tell us something useful
about those archives.  

From what I can see, the archiver used to be on the gnu.org list under a
sourceware.cygnus.com address (I get this by reading the amusing tidbit
http://sources.redhat.com/ml/bug-glibc/2002-09/msg00000.html, wdii).
sourceware.cygnus.com was renamed to sources.redhat.com a long time ago.  A
couple of months ago Red Hat decided for some reason to remove that CNAME,
so the list redistribution presumably started bouncing and got dropped by
the gnu.org mailman engine.

If the archiver on sources.redhat.com for bug-glibc gets set up again,
I don't know if it's feasible to pump the missing time period's gnu.org
archives through it to get the missing months of (reduced spam) archive.

There are also periodic claims by the gnu.org sysadmins that they are
installing sane spam filtering, so you might poke them to make the gnu.org
bug-glibc archives usable again by getting rid of the spam majority.



Roland

[MAILER-DAEMON@sources.redhat.com: failure notice]

[Zack Weinberg]

Please fix GNATS again.

zw

----- Forwarded message from MAILER-DAEMON@sources.redhat.com -----

Date: 25 Jul 2002 16:06:01 -0000
From: MAILER-DAEMON@sources.redhat.com
To: zack@codesourcery.com
Subject: failure notice

Hi. This is the qmail-send program at sources.redhat.com.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

<gnats-admin@gcc.gnu.org>:
Sorry, no mailbox here by that name. (#5.1.1)

--- Below this line is a copy of the message.

Return-Path: <zack@codesourcery.com>
Received: (qmail 2924 invoked by uid 71); 25 Jul 2002 16:06:01 -0000
Resent-Date: 25 Jul 2002 16:06:01 -0000
Resent-Message-ID: <20020725160601.2923.qmail@sources.redhat.com>
Resent-From: gcc-gnats@gcc.gnu.org (GNATS Filer)
Resent-To: gnats-admin@gcc.gnu.org
Resent-Reply-To: gcc-gnats@gcc.gnu.org, Zack Weinberg <zack@codesourcery.com>
Received: (qmail 463 invoked from network); 25 Jul 2002 16:01:12 -0000
Received: from unknown (HELO egil.codesourcery.com) (66.92.14.122)
  by sources.redhat.com with SMTP; 25 Jul 2002 16:01:12 -0000
Received: from zack by egil.codesourcery.com with local (Exim 3.35 #1 (Debian))
	id 17Xl32-0003v8-00; Thu, 25 Jul 2002 09:01:04 -0700
Message-Id: <20020725160103.GA15016@codesourcery.com>
Date: Thu, 25 Jul 2002 09:01:04 -0700
From: Zack Weinberg <zack@codesourcery.com>
To: pinskia@physics.uc.edu
Cc: gcc-gnats@gcc.gnu.org
In-Reply-To: <20020725142745.13413.qmail@sources.redhat.com>
References: <20020725142745.13413.qmail@sources.redhat.com>
Subject: pending/7405: Re: bootstrap: Illegal .size expression


>Number:         7405
>Category:       pending
>Synopsis:       Re: bootstrap: Illegal .size expression
>Confidential:   yes
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Jul 25 09:06:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     
>Release:        
>Organization:
>Environment:
>Description:
 On Thu, Jul 25, 2002 at 02:27:45PM -0000, pinskia@physics.uc.edu wrote:
 > libgcc2.s: Assembler messages:
 > libgcc2.s:294: Error: Illegal .size expression
 ...
 > -       .size   ___muldi3, _.-___muldi3
 > +       .size   ___muldi3 , . - ___muldi3
 
 Gnnn.  I was not expecting underscore-prefixing to happen.
 
 Could you please apply the appended patch to your tree and retest?
 It is a hack, but will at least let me know if the problem is what I
 believe it is.
 
 zw
 
 Index: defaults.h
 ===================================================================
 RCS file: /cvs/gcc/gcc/gcc/defaults.h,v
 retrieving revision 1.84
 diff -u -p -r1.84 defaults.h
 --- defaults.h	25 Jul 2002 05:14:17 -0000	1.84
 +++ defaults.h	25 Jul 2002 16:00:33 -0000
 @@ -205,9 +205,7 @@ do { fputs (integer_asm_op (POINTER_SIZE
      {							\
        fputs (SIZE_ASM_OP, STREAM);			\
        assemble_name (STREAM, BEG);			\
 -      fputs (", ", STREAM);				\
 -      assemble_name (STREAM, END);			\
 -      putc ('-', STREAM);				\
 +      fputs (", .-", STREAM);				\
        assemble_name (STREAM, BEG);			\
        putc ('\n', STREAM);				\
      }							\
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:

----- End forwarded message -----

[MAILER-DAEMON@sources.redhat.com: failure notice]

[Craig Rodrigues]

Hi,

I am getting these error messages when responding
to things in GNATS.

-- 
Craig Rodrigues        
http://www.gis.net/~craigr    
rodrigc@mediaone.net          

----- Forwarded message from MAILER-DAEMON@sources.redhat.com -----

Date: 3 Jan 2002 16:06:14 -0000
From: MAILER-DAEMON@sources.redhat.com
To: rodrigc@mediaone.net
Subject: failure notice

Hi. This is the qmail-send program at sources.redhat.com.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

<gcc-prs@gcc.gnu.org>:
Sender: rodrigc@mediaone.net
This mailing list is not for general discussions.  Please resend your
mail note to a more appropriate list.


--- Below this line is a copy of the message.

Return-Path: <rodrigc@mediaone.net>
Received: (qmail 12901 invoked from network); 3 Jan 2002 16:06:09 -0000
Received: from unknown (HELO dibbler.ne.mediaone.net) (24.218.57.139)
  by sources.redhat.com with SMTP; 3 Jan 2002 16:06:09 -0000
Received: (from rodrigc@localhost)
	by dibbler.ne.mediaone.net (8.11.0/8.11.0) id g03G6Ub10428;
	Thu, 3 Jan 2002 11:06:30 -0500
Date: Thu, 3 Jan 2002 11:06:29 -0500
From: Craig Rodrigues <rodrigc@mediaone.net>
To: James.Marselle@GFIGenfare.spx.com
Cc: rodrigc@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
   nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Subject: Re: bootstrap/5248: I can't get bootstrap to work.
Message-ID: <20020103110629.A10416@mediaone.net>
References: <OFA5034126.4CF66373-ON86256B36.0056EB77@spx.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <OFA5034126.4CF66373-ON86256B36.0056EB77@spx.com>; from James.Marselle@GFIGenfare.spx.com on Thu, Jan 03, 2002 at 10:01:38AM -0600

On Thu, Jan 03, 2002 at 10:01:38AM -0600, James.Marselle@GFIGenfare.spx.com wrote:
> By the way, I was getting a lot of the following warnings during the build:
> 
> cc1: warning: -g is only supported when using GAS on this processor.
> cc1: warning: -g option disabled.
> 
> Would this indicate that I was using the wrong "as" or is this some other
> problem?

Yes that is the problem.
-- 
Craig Rodrigues        
http://www.gis.net/~craigr    
rodrigc@mediaone.net          

----- End forwarded message -----

Re: [MAILER-DAEMON@sources.redhat.com: failure notice]

[Christopher Faylor]

On Tue, Nov 07, 2000 at 05:24:10PM -0800, Jason Molenda wrote:
>I wouldn't worry much about spammers who are RBL'ed getting clever
>enough to subscribe to a list before spamming.  That seems pretty
>unlikely for now.

I agree.  So this could be the best of all possible worlds, then, isn't
it?  We could get the benefit of spam blocking without impacting our
mailing list users.

This probably means that we can get rid of the whitelist, too.  People
could put themselves on the whitelist just by subscribing.

cgf

Re: [MAILER-DAEMON@sources.redhat.com: failure notice]

[Christopher Faylor]

I agree that Ian was amazing diplomatic in his response.  It's
nice to know who I can send all of the angry email to in the future.

:-)

On Tue, Nov 07, 2000 at 03:21:51PM -0800, Jason Molenda wrote:
>Another option is to use a free e-mail service like, oh I don't
>know, Yahoo Mail.  Set up a Yahoo Mail account and you can send
>your outgoing mail through them, and you can even retrieve any
>Yahoo Mail via POP3.  I'm sure Hotmail and other free mail services
>on the net provide similar services.

This is what I usually suggest.

What about his idea of allowing anyone who was a subscriber to the
mailing list in question through?  That would be easy to implement.

Do we want to do this?

cgf

Re: [MAILER-DAEMON@sources.redhat.com: failure notice]

[Jason Molenda]

On Tue, Nov 07, 2000 at 07:46:25PM -0500, Christopher Faylor wrote:

> What about his idea of allowing anyone who was a subscriber to the
> mailing list in question through?  That would be easy to implement.

It should work - the userid in the DIR/editor file should be alias,
so you could run ezmlm-list if a message was going to be RBL'ed.
I'd only do the ezmlm-list check if the RBL matched true - it's a
pretty expensive operation for every message to go through.

There is also an 'allow' list of users (akin to the digest users)
for each mailing list.  It's only used for lists like libc-hacker
and cygwin-developer which restrict posts to list members.  It
allows you to have multiple accepted addresses, but only receive
e-mail at one.

For instance, I might subscribe as 'jason-libc-spam@molenda.com'
but I sometimes post as jsm@cygnus.com and jsm@redhat.com, so I'd
subscribe jsm@cygnus.com and jsm@redhat.com to the allow list.

With lists that restrict posts to subscribed people, these allow
list additions have to be approved by the moderator (along with
subscriptions).

I suspect the same allow lists (ezmlm-list DIR/allow) exist even
for lists that don't restrict posts in this manner, so someone who
was RBL'ed and was coming in from multiple locations could list
them all here.

I wouldn't worry much about spammers who are RBL'ed getting clever
enough to subscribe to a list before spamming.  That seems pretty
unlikely for now.

Jason

Re: [MAILER-DAEMON@sources.redhat.com: failure notice]

[Jason Molenda]

On Tue, Nov 07, 2000 at 10:38:44PM -0500, Christopher Faylor wrote:

> 
> This probably means that we can get rid of the whitelist, too.  People
> could put themselves on the whitelist just by subscribing.
> 


I'd keep it around.  If you had a list participant who read the list
on the web, but wanted to post, they'd get grumpy if we didn't have a
whitelist capability.

I'd expect the whitelist functionality to become largely unused if
the list subscriber check were added, though.


J

Re: [MAILER-DAEMON@sources.redhat.com: failure notice]

[Jason Molenda]

On Tue, Nov 07, 2000 at 10:38:44PM -0500, Christopher Faylor wrote:

> 
> This probably means that we can get rid of the whitelist, too.  People
> could put themselves on the whitelist just by subscribing.
> 


I'd keep it around.  If you had a list participant who read the list
on the web, but wanted to post, they'd get grumpy if we didn't have a
whitelist capability.

I'd expect the whitelist functionality to become largely unused if
the list subscriber check were added, though.


J

Re: [MAILER-DAEMON@sources.redhat.com: failure notice]

[Christopher Faylor]

On Tue, Nov 07, 2000 at 05:24:10PM -0800, Jason Molenda wrote:
>I wouldn't worry much about spammers who are RBL'ed getting clever
>enough to subscribe to a list before spamming.  That seems pretty
>unlikely for now.

I agree.  So this could be the best of all possible worlds, then, isn't
it?  We could get the benefit of spam blocking without impacting our
mailing list users.

This probably means that we can get rid of the whitelist, too.  People
could put themselves on the whitelist just by subscribing.

cgf

Re: [MAILER-DAEMON@sources.redhat.com: failure notice]

[Jason Molenda]

On Tue, Nov 07, 2000 at 07:46:25PM -0500, Christopher Faylor wrote:

> What about his idea of allowing anyone who was a subscriber to the
> mailing list in question through?  That would be easy to implement.

It should work - the userid in the DIR/editor file should be alias,
so you could run ezmlm-list if a message was going to be RBL'ed.
I'd only do the ezmlm-list check if the RBL matched true - it's a
pretty expensive operation for every message to go through.

There is also an 'allow' list of users (akin to the digest users)
for each mailing list.  It's only used for lists like libc-hacker
and cygwin-developer which restrict posts to list members.  It
allows you to have multiple accepted addresses, but only receive
e-mail at one.

For instance, I might subscribe as 'jason-libc-spam@molenda.com'
but I sometimes post as jsm@cygnus.com and jsm@redhat.com, so I'd
subscribe jsm@cygnus.com and jsm@redhat.com to the allow list.

With lists that restrict posts to subscribed people, these allow
list additions have to be approved by the moderator (along with
subscriptions).

I suspect the same allow lists (ezmlm-list DIR/allow) exist even
for lists that don't restrict posts in this manner, so someone who
was RBL'ed and was coming in from multiple locations could list
them all here.

I wouldn't worry much about spammers who are RBL'ed getting clever
enough to subscribe to a list before spamming.  That seems pretty
unlikely for now.

Jason

Re: [MAILER-DAEMON@sources.redhat.com: failure notice]

[Christopher Faylor]

I agree that Ian was amazing diplomatic in his response.  It's
nice to know who I can send all of the angry email to in the future.

:-)

On Tue, Nov 07, 2000 at 03:21:51PM -0800, Jason Molenda wrote:
>Another option is to use a free e-mail service like, oh I don't
>know, Yahoo Mail.  Set up a Yahoo Mail account and you can send
>your outgoing mail through them, and you can even retrieve any
>Yahoo Mail via POP3.  I'm sure Hotmail and other free mail services
>on the net provide similar services.

This is what I usually suggest.

What about his idea of allowing anyone who was a subscriber to the
mailing list in question through?  That would be easy to implement.

Do we want to do this?

cgf