[Zope-Coders] Mail delivery failed: returning message to sender

[Mail Delivery System]

This message was created automatically by mail delivery software (Exim).

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  ctbomm652@rmt.flow.com.au
    SMTP error from remote mailer after RCPT TO:<ctbomm652@rmt.flow.com.au>:
    host ops2.flow.com.au [202.129.64.116]: 554 <ctbomm652@rmt.flow.com.au>:
    Recipient address rejected: Relay access denied

------ This is a copy of the message, including all the headers. ------

Return-path: <zope-coders@zope.org>
Received: from exim by mail.python.org with spamc (Exim 4.02)
	id 17AAMq-0003r7-00; Tue, 21 May 2002 10:12:00 -0400
Received: from [63.102.49.30] (helo=cvs.baymountain.com)
	by mail.python.org with esmtp (Exim 4.02)
	id 17AAMq-0003r0-00; Tue, 21 May 2002 10:12:00 -0400
From: "Collector: Zope Bugs, Features, and Patches ..." <zope-coders@zope.org>
To: Robert Thomson <ctbomm652@rmt.flow.com.au>, ajung <andreas@zope.com>, klm <klm@zope.com>, Brian <brian@zope.com>, chrism <chrism@zope.com>, Caseman <casey@zope.com>, _Rejected_ recipient <zope-collector-monitor@zope.org>
Subject: [ZC] 398/ 2 Reject "getPhysicalPath/Acquisition bug when referencing object from different context"
X-Recipients-debug: ['Anonymous User', 'ajung', 'klm', 'Brian', 'chrism', 'Caseman', ('_Rejected_ recipient', 'zope-collector-monitor@zope.org')]
Message-Id: <E17AAMq-0003r0-00@mail.python.org>
Date: Tue, 21 May 2002 10:12:00 -0400
X-Spam-Status: No, hits=-1.0 required=5.0 tests=BODY_PYTHON_ZOPE version=2.20
X-Spam-Level: 

Issue #398 Update (Reject) "getPhysicalPath/Acquisition bug when referencing object from different context"
 Status Rejected, Zope/bug medium
To followup, visit:
  http://collector.zope.org/Zope/398

==============================================================
= Reject - Entry #2 by ajung on May 21, 2002 10:11 am

 Status: Pending => Rejected

After reading this issue several times I still do not 
understand what you really mean. The example you gave
is not really useful to recognize the real problem.
Please provide a simple testcase that shows the problem.

-aj
________________________________________
= Request - Entry #1 by Anonymous User on May 20, 2002 3:27 am

When calling getPhysicalPath on a Zope object when in a different context (eg. further up the hierarchy), it returns incorrect values. This affects absolute_url() as-well.

I did try to upload a file with examples, but permission errors in the bug collector. Here's a paste of them, though.  Try http://rmt.dyndns.org/zopebug.txt also.
 More output:
 
 [/private/ipdb]$ call FindRange('202.129.64.4/30').getPhysicalPath()
 ('202.129.64.4_30', '202.129.64.0_18', '202.129.64.4_30')
 
 [/private/ipdb]$ call FindRange('202.129.64.0/18').getPhysicalPath()
 ('202.129.64.0_18', 'ipdb', '202.129.64.0_18')
 
 [/private/ipdb]$ call FindRange('202.129.64.0/18')
 202.129.64.0/18
 
 [/private/ipdb]$ call FindRange('202.129.64.4/30')
 202.129.64.4/30
 
 [/private/ipdb]$ call FindRange('202.129.64.4/30').aq_parent
 0.0.0.0/0
 # huh? This should return 202.129.64.0/18
 
 [/private/ipdb/202.129.64.0_18/202.129.64.4_30]$ call aq_parent
 202.129.64.0/18
 # like this!
 
 [/private/ipdb/202.129.64.0_18]$ call FindRange('202.129.64.4/30').aq_parent
 202.129.64.0/18
 # or this!
 
 [/private/ipdb]$ call FindRange('202.129.64.4/30').aq_parent.getPhysicalPath()
 ('', 'private', 'ipdb')
 
 [/private/ipdb]$ call FindRange('202.129.64.0/18').getPhysicalPath()
 ('202.129.64.0_18', 'ipdb', '202.129.64.0_18')

==============================================================