[Zope3-dev] Mail delivery failed: returning message to sender

[Mail Delivery System]

This message was created automatically by mail delivery software.

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:

  sidnei at awkly.org
    SMTP error from remote mailer after end of data:
    host mail.redesul.com.br [200.248.43.8]: 554 qq permanent problem (#5.3.0)

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

Return-path: <zope3-dev at zope.org>
Received: from cache1.zope.org ([12.155.117.38])
	by mail.python.org with esmtp (Exim 4.22)
	id 1B4kj9-00059C-7F; Sat, 20 Mar 2004 12:57:43 -0500
From: zope3-dev at zope.org (gintautasm)
Reply-To: zope3-dev at zope.org
To: ;
Subject: [Instance and Type based subscriptions] 
Message-ID: <20040320125743EST at dev.zope.org>
X-BeenThere: zope3-dev at zope.org
X-Zwiki-Version: 0.21.1
Precedence: bulk
List-Id:  <zope3-dev at zope.org>
List-Post: <mailto:zope3-dev at zope.org>
List-Subscribe: <http://dev.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/InstanceAndTypeBasedSubscriptions/subscribeform>
List-Unsubscribe: <http://dev.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/InstanceAndTypeBasedSubscriptions/subscribeform>
List-Archive: <http://dev.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/InstanceAndTypeBasedSubscriptions>
List-Help: <http://dev.zope.org/Wikis/DevSite/Projects/ComponentArchitecture>
Date: Sat, 20 Mar 2004 12:57:43 -0500
X-Spam-Status: OK (default 0.000)

??changed:
-    policies. These are currently provides via methods on the objects
    policies. These are currently provided via methods on the objects

??changed: - as subscribers that were called when objects of a
particular type - are added or removed. Why? If there are multiople
actions we want as subscribers that are called when objects of a
particular type are added or removed. Why? If there are multiple
actions we want

??changed: - Similarly, we have a dependency framework, for,
essentially, - defining integrity constraints mong objects. We prevent
objects Similarly, we have a dependency framework essentially for
defining integrity constraints among objects. We prevent objects

??changed: - even for it's class. even for its class.

??changed: - and call it's notify method. and call its notify method.

--
forwarded from http://dev.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/InstanceAndTypeBasedSubscriptions