List Info

Thread: ezmlm warning




ezmlm warning
user name
2007-11-06 21:43:17
Hi! This is the ezmlm program. I'm managing the
perl5-portersperl.org mailing list.

I'm working for my owner, who can be reached
at perl5-porters-ownerperl.org.


Messages to you from the perl5-porters mailing list seem to
have been bouncing. I've attached a copy of the first
bounce
message I received.

If this message bounces too, I will send you a probe. If the
probe bounces,
I will remove your address from the perl5-porters mailing
list,
without further notice.


I've kept a list of which messages from the perl5-porters
mailing list have 
bounced from your address.

Copies of these messages may be in the archive.
To retrieve a set of messages 123-145 (a maximum of 100 per
request),
send an empty message to:
   <perl5-porters-get.123_145perl.org>

To receive a subject and author list for the last 100 or so
messages,
send an empty message to:
   <perl5-porters-indexperl.org>

Here are the message numbers:

   129990
   129991
   129992
   129993
   129994
   129995
   129996
   129997
   129998
   129999
   130000
   130001
   130002
   130003
   130004
   130005
   130006
   130007
   130008
   130009
   130010
   130011
   130012
   130013
   130014
   130015
   130016
   130017
   130018
   130019
   130020
   130021
   130022
   130023
   130024
   130025
   130026
   130027
   130028
   130029
   130030
   130031
   130032
   130033
   130034
   130035
   130036
   130037
   130038
   130039
   130040
   130041
   130042
   130043
   130044
   130045
   130046
   130047
   130048
   130049
   130050
   130051
   130052
   130053
   130054
   130055
   130056
   130058
   130057
   130059
   130060
   130061
   130062
   130063
   130064
   130065
   130066
   130067
   130068
   130069
   130070
   130071
   130072
   130073
   130074
   130075
   130076
   130077
   130078
   130079
   130080
   130081
   130082
   130083
   130084
   130085
   130086
   130087
   130088
   130089
   130090
   130092
   130091
   130093
   130094
   130095
   130096
   130097
   130098
   130099
   130100
   130102
   130101
   130103
   130104
   130105
   130106
   130107
   130108
   130109
   130111
   130110
   130112
   130113
   130114
   130115
   130116
   130117
   130118
   130119
   130120
   130121
   130122
   130123
   130124
   130125
   130126
   130128
   130129
   130130
   130127
   130131
   130132
   130133
   130134
   130135
   130136
   130137
   130138
   130139
   130140
   130141
   130142
   130143
   130144
   130145
   130146
   130147
   130148
   130149
   130150
   130151
   130152
   130154
   130155
   130156
   130157
   130158
   130159
   130160
   130161
   130163
   130164
   130166
   130168
   130169
   130170
   130171
   130172
   130173
   130174
   130175
   130176
   130177
   130178
   130179
   130181
   130182
   130183
   130184
   130185
   130186
   130187
   130188
   130189
   130190
   130191
   130192
   130193
   130194
   130195
   130196
   130197
   130198
   130199
   130200
   130202
   130201

--- Enclosed is a copy of the bounce message I received.

Return-Path: <>
Received: (qmail 7016 invoked from network); 26 Oct 2007
06:32:56 -0000
Received: from x1a.develooper.com (HELO x1.develooper.com)
(216.52.237.111)
  by lists.develooper.com with SMTP; 26 Oct 2007 06:32:56
-0000
Received: (qmail 22910 invoked by uid 225); 26 Oct 2007
06:32:56 -0000
Delivered-To: perl5-porters-return-129990-bond=yahoo.comperl.org
Received: (qmail 22900 invoked by alias); 26 Oct 2007
06:32:55 -0000
X-Spam-Status: No, hits=4.9 required=8.0
	tests=BAYES_00,RAZOR2_CF_RANGE_51_100,RAZOR2_CF_RANGE_E4_51
_100,RAZOR2_CHECK,SPF_HELO_PASS
X-Spam-Check-By: la.mx.develooper.com
Received: from starfire.yahoo.com (HELO starfire.yahoo.com)
(66.98.192.98)
    by la.mx.develooper.com (qpsmtpd/0.28) with ESMTP; Thu,
25 Oct 2007 23:32:52 -0700
Received: by starfire.yahoo.com (Postfix)
	id 625CA401DEA; Fri, 26 Oct 2007 01:26:54 -0500 (CDT)
Date: Fri, 26 Oct 2007 01:26:54 -0500 (CDT)
From: MAILER-DAEMONyahoo.com (Mail Delivery System)
Subject: Undelivered Mail Returned to Sender
To: perl5-porters-return-129990-bond=yahoo.comperl.org
Auto-Submitted: auto-replied
MIME-Version: 1.0
Content-Type: multipart/report;
report-type=delivery-status;
	boundary="2B1AC4002DD.1193380014/starfire.yahoo.com&qu
ot;
Content-Transfer-Encoding: 8bit
Message-Id: <20071026062654.625CA401DEAstarfire.yahoo.com>

This is a MIME-encapsulated message.

--2B1AC4002DD.1193380014/starfire.yahoo.com
Content-Description: Notification
Content-Type: text/plain; charset=us-ascii

This is the mail system at host starfire.yahoo.com.

I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached
below.

For further assistance, please send mail to postmaster.

If you do so, please include this problem report. You can
delete your own text from the attached returned message.

                   The mail system

<bondyahoo.com>: cannot update mailbox /var/mail/bond
for user bond. error
    writing message: File too large

--2B1AC4002DD.1193380014/starfire.yahoo.com
Content-Description: Delivery report
Content-Type: message/delivery-status

Reporting-MTA: dns; starfire.yahoo.com
X-Postfix-Queue-ID: 2B1AC4002DD
X-Postfix-Sender: rfc822;
perl5-porters-return-129990-bond=yahoo.comperl.org
Arrival-Date: Fri, 26 Oct 2007 01:26:54 -0500 (CDT)

Final-Recipient: rfc822; bondyahoo.com
Original-Recipient: rfc822;bondyahoo.com
Action: failed
Status: 5.2.2
Diagnostic-Code: x-unix; input/output error

--2B1AC4002DD.1193380014/starfire.yahoo.com
Content-Description: Undelivered Message
Content-Type: message/rfc822
Content-Transfer-Encoding: 8bit

X-Virus-Scanned: amavisd-new at yahoo.com
Received: from starfire.yahoo.com ([127.0.0.1])
	by localhost (starfire.yahoo.com [127.0.0.1]) (amavisd-new,
port 10024)
	with ESMTP id 8tEM4v+WL1Ti for <bondyahoo.com>;
	Fri, 26 Oct 2007 01:26:47 -0500 (CDT)
Received: from lists.develooper.com (x6.develooper.com
[63.251.223.186])
	by starfire.yahoo.com (Postfix) with SMTP id 3700B4026A7
	for <bondyahoo.com>; Fri, 26 Oct 2007 01:26:45
-0500 (CDT)
Received: (qmail 4779 invoked by uid 514); 26 Oct 2007
06:26:44 -0000
Mailing-List: contact perl5-porters-helpperl.org;
run by ezmlm
Precedence: bulk
list-help: <mailto:perl5-porters-helpperl.org>
list-unsubscribe: <mailto:perl5-porters-unsubscribeperl.org>
list-post: <mailto:perl5-portersperl.org>
X-List-Archive: <http://nntp.perl.org/group/perl.perl5.porters/129990>

List-Id: <perl5-porters.perl.org>
Delivered-To: mailing list perl5-portersperl.org
Received: (qmail 4763 invoked from network); 26 Oct 2007
06:26:43 -0000
Delivered-To: perl5-portersperl.org
X-Spam-Check-By: la.mx.develooper.com
Message-ID: <47218891.2080209NevCal.com>
Date: Thu, 25 Oct 2007 23:26:25 -0700
From: Glenn Linderman <perlNevCal.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
rv:1.8.0.9) Gecko/20061211 SeaMonkey/1.0.7 Mnenhy/0.7.4.0
MIME-Version: 1.0
To: Brandon Black <blblackgmail.com>
CC: Linda W <perl-diddlertlinx.org>, 
 Perl 5 Porters <perl5-portersperl.org>
Subject: Re: Broken Perl OO-parent-method call
References: <47211F7D.5020903tlinx.org>	
<84621a60710251739g7de5c3e7h9b0e610e4c4e7ca6mail.gmail.com>	 <20071026021328.GZ29047bort.ca> <472168FF.5020104tlinx.org>	
<84621a60710252212s252f5fb8xba356fe6ffaf8ef3mail.gmail.com>
<84621a60710252215p69edc4f3x26e66138f26c5883mail.gmail.com>
In-Reply-To:
<84621a60710252215p69edc4f3x26e66138f26c5883mail.gmail.com>
X-No-Archive: yes
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please
include it with any abuse report
X-AntiAbuse: Primary Hostname - gary.yourhostdns.com
X-AntiAbuse: Original Domain - perl.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - NevCal.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 

On approximately 10/25/2007 10:15 PM, came the following
characters from 
the keyboard of Brandon Black:
> On 10/26/07, Brandon Black <blblackgmail.com> wrote:
>> Most likely the cleanest way to fix this without
breaking anything
>> else is to make the method lookup code ignore these
stub entries and
>> look past them in the inheritance lookup, if
they're easy to identify.
>>
> 
> Except I wasn't thinking about AUTOLOAD.  I bet the
above would break
> AUTOLOAD.  I never use it, so I never really think of
it.  Hmmm.


I wondered about that after reading your first message, and
almost 
responded, and then I convinced myself it would have to be a
different 
stub, so should be detectably different.

-- 
Glenn -- http://nevcal.com/
===========================
A protocol is complete when there is nothing left to
remove.
-- Stuart Cheshire, Apple Computer, regarding Zero
Configuration Networking

--2B1AC4002DD.1193380014/starfire.yahoo.com--

[1]

about | contact  Other archives ( Real Estate discussion Medical topics )