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

Mail Delivery System Mailer-Daemon@python.org
Tue, 02 Apr 2002 08:26:03 -0500


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:

  iivi@yahoo.com
    SMTP error from remote mailer after end of data:
    host mx2.mail.yahoo.com [64.157.4.88]: 554 delivery error:
    dd This user doesn't have a yahoo.com account (iivi@yahoo.com) - mta444.mail.yahoo.com

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

Return-path: <zope-coders@zope.org>
Received: from [63.102.49.30] (helo=cvs.baymountain.com)
	by mail.python.org with esmtp (Exim 3.35 #2)
	id 16sOI4-0000Ka-00; Tue, 02 Apr 2002 08:25:36 -0500
From: "Collector: Zope Bugs, Features, and Patches ..." <zope-coders@zope.org>
To: II-V-I <iivi@yahoo.com>, ajung <andreas@zope.com>, klm <klm@zope.com>, Brian <brian@zope.com>, chrism <chrism@zope.com>, paul <paul@zope.com>, _Rejected_ recipient <zope-collector-monitor@zope.org>
Subject: [ZC] 328/ 2 Reject "Structured Text fails on accented letters"
X-Recipients-debug: ['Anonymous User', 'ajung', 'klm', 'Brian', 'chrism', 'paul', ('_Rejected_ recipient', 'zope-collector-monitor@zope.org')]
Message-Id: <E16sOI4-0000Ka-00@mail.python.org>
Date: Tue, 02 Apr 2002 08:25:36 -0500

Issue #328 Update (Reject) "Structured Text fails on accented letters"
 Status Rejected, Zope/bug medium
To followup, visit:
  http://collector.zope.org/Zope/328

==============================================================
= Reject - Entry #2 by ajung on Apr 2, 2002 8:25 am

 Status: Pending => Rejected

See http://www.zope.org/Members/ajung/howto/Locale%20Support%20for%20Structured%20Text/

-aj
________________________________________
= Request - Entry #1 by Anonymous User on Apr 2, 2002 7:57 am

structured text fails on accented letters
for example:

**è** doens't work while
**&egrave;** does

probably some parsing problem ...
==============================================================