python-ldap-dev — discussion among developers

Re: explicit vs implicit attributes names

[<mi...@st...>]

Jerome Alet wrote:
> 
> I'd want to retrieve complete LDAP entries from my server,
> including createTimestamp and modifyTimestamp (where available)

These are so-called operational attributes.

> But if I pass None as the attributes to retrieve, I only
> receive attributes which I've created myself, not "server"'s
> attributes like the two mentionned above.

This is not really a python-ldap issue.

> I have to explicitely pass all attributes names + "createTimestamp"
> and al, and I find this completely inconvenient.

Maybe ['*',"createTimestamp"] helps.

> Is there a simple solution to not have to explicitely name all
> attributes ?

OpenLDAP supports draft-zeilenga-ldap-opattrs which enable you to request 
all operational attributes with ['+']. All user and operational attributes 
can be retrieved from an OpenLDAP server with ['*','+']. This does not work 
for other LDAP servers which do not support draft-zeilenga-ldap-opattrs.

Furthermore expect all weird things to happen with various LDAP server 
products. E.g. Domino/LDAP does not process ['*'] properly. Not sure whether 
they fixed it during the last year...

Ciao, Michael.

Re: help on subschema

[<mi...@st...>]

paul k wrote:
> Hi all,
> how do I query the servers subschema entry  for supported objectclasses? 

See Demo/schema.py.

> Searching like:
> 
> conn.search_s('cn=subschema',ldap.SCOPE_SUBTREE, '(objectclass=*)')
 > returns ldap.NO_SUCH_OBJECT.

The sub schema sub entry is not always located in cn=subschema. You have to 
query the operational attribute subschemaSubentry for the DN holding the sub 
schema sub entry. That's what ldap.LDAPObject.search_subschemasubentry_s() 
is for.

Note that each part of the DIT can have its own separate sub schema sub 
entry! You have to query subschemaSubentry at each and every DN you're 
working with. Therefore you have to implement some kind of caching of sub 
schema instances to make it efficient.

I know the whole schema stuff is completely undocumented. But have a look at 
Demo/schema.py. That should make things more clear.

Ciao, Michael.

help on subschema

[paul k <pa...@su...>]

Hi all,
how do I query the servers subschema entry  for supported objectclasses? 
Searching like:

conn.search_s('cn=subschema',ldap.SCOPE_SUBTREE, '(objectclass=*)')

returns ldap.NO_SUCH_OBJECT. I cannot firute out how to get operational 
attributes.I looked at ldap.schema.subentry.SubSchema but could not 
figure out how to use it.

thanks
  Paul

Re: python-ldap segfault at binding time

[<mi...@st...>]

Hi Jerome,

you can reach the python-ldap developers on the list 
pyt...@li.... It's worth to subscribe to it. It's 
low-volume.

Jerome Alet wrote:
> 
> I'm the author of a python-written print quota and accounting 
> solution named PyKota, [..]  this software uses python-ldap (of course)
> 
> Two people reported segfaults to me at binding time under 
> RedHat 9 (with Python 2.2)
> 
> The attached program repeatedly crashes with a segfault 
> during the simple_bind_s() call on users' machines

Well, this is most likely caused by outdated versions of OpenSSL, OpenLDAP 
libs, SASL libs or maybe even outdated python-ldap itself or a library mix.

People experiencing seg faults should build/reinstall recent versions of 
their installed software in the following order:
- OpenSSL
- Cyrus-SASL
- OpenLDAP
- Python
- python-ldap

> Unfortunately I don't use RedHat, but Debian instead, and I must
> confess I didn't notice such a problem so far.

RedHat 9 is known to still ship with a very outdated version of OpenLDAP.

Ciao, Michael.

Re: Segmentation fault

[<mi...@st...>]

Marc Petitmermet wrote:
> 
> but when using 
> my development system with python-2.1.3, python-ldap-2.0.0pre19, 
> openldap-2.1.23, openssl-0.9.7c i get a segmentation fault:

It works for me with Python 2.3 and Python 2.1.3, python-ldap-2.0.0pre19, 
OpenLDAP libs 2.1.26 (self-compiled), openssl-0.9.7b-71 (RPM of SuSE Linux 9.0).

Guess it's a local installation error on your system. Please make sure to 
re-build and re-install all packages in this order:
- OpenSSL
- OpenLDAP
- Python
- python-ldap

Also make sure to have properly adjusted setup.cfg and invoked setup.py with 
the right Python executable.

Ciao, Michael.

Segmentation fault

[Marc P. <pet...@ma...>]

dear list members

i have the python code below (from initialize.py) to test ldap 
connection over ssh to an external ldap-server.

on my production system with python-2.1.3, python-ldap-2.0.0pre06, 
openldap-2.1.12, openssl-0.9.7c i get a correct output. but when using 
my development system with python-2.1.3, python-ldap-2.0.0pre19, 
openldap-2.1.23, openssl-0.9.7c i get a segmentation fault:

*** ldaps://x.x.xx:636 - SimpleLDAPObject.set_option ((17, 3),{})
*** ldaps://x.x.xx:636 - SimpleLDAPObject.set_option ((17, 3),{})
*** ldaps://x.x.xx:636 - SimpleLDAPObject.bind (('', '', 128),{})
ldap_bind
ldap_simple_bind
ldap_sasl_bind
ldap_send_initial_request
ldap_new_connection
ldap_int_open_connection
ldap_connect_to_host: x.x.xx
ldap_new_socket: 3
ldap_prepare_socket: 3
ldap_connect_to_host: Trying xxx.xxx.xx.xxx:636
ldap_connect_timeout: fd: 3 tm: -1 async: 0
ldap_ndelay_on: 3
ldap_is_sock_ready: 3
ldap_ndelay_off: 3
ldap_int_sasl_open: host=x.x.xx
TLS trace: SSL_connect:before/connect initialization
TLS trace: SSL_connect:SSLv2/v3 write client hello A
TLS trace: SSL_connect:SSLv3 read server hello A
TLS certificate verification: depth: 1, subject: xx 
emailAddress=xx@x.x.xx, issuer: xx emailAddress=xx@x.x.xx
TLS trace: SSL_connect:SSLv3 read server certificate A
TLS trace: SSL_connect:SSLv3 read server done A
TLS trace: SSL_connect:SSLv3 write client key exchange A
TLS trace: SSL_connect:SSLv3 write change cipher spec A
TLS trace: SSL_connect:SSLv3 write finished A
TLS trace: SSL_connect:SSLv3 flush data
TLS trace: SSL_connect:SSLv3 read finished A
Segmentation fault

can anybody tell me how to solve this? i don't think that this can be 
ignored. i guess that this is also the cause for my problems with the 
latest LDAPUserFolder which i wanted to use with zope.

thanks in advance for any hints.
regards,
marc



------------------------------------------------

test code:

import sys,ldap

# Set debugging level
ldap.set_option(ldap.OPT_DEBUG_LEVEL,255)
ldapmodule_trace_level = 1
ldapmodule_trace_file = sys.stderr

print
"""##################################################################
    # LDAPv3 connection over SSL
    ##################################################################
"""

# Create LDAPObject instance (one single line command below)
l = ldap.initialize(
       'ldaps://x.x.xx:636',
       trace_level=ldapmodule_trace_level,
       trace_file=ldapmodule_trace_file)
# Set LDAP protocol version used
l.protocol_version=ldap.VERSION3
# Try a bind to provoke failure if protocol version is not supported
l.bind_s('','',ldap.AUTH_SIMPLE)
# Close connection
l.unbind_s()

Re: subtree searches stopped working -- I am really stuck

[<mi...@st...>]

Joao S. O. Bueno wrote:
> 
> I am here developing my stuff when suddenly yesterday (ok, after an 
> unexpected -related or not - reboot) ,all my python ldap Subtree 
> searches return an empty result.

If it "suddenly" stopped working I guess this has nothing to do with
python-ldap. I'd rather expect the DB and/or the indexes of the LDAP server 
to be corrupted during the crash.

> I also could not find in the docs information about the options that are 
> available via get/set options.

Hmm, you could look into the man pages of the OpenLDAP libs.

Ciao, Michael.

Re: Noisy output with SASL-Authentication

[<mi...@st...>]

Johannes Beigel wrote:
> Maybe libsasl is compiled with debugging output turned on there? I also 
> noticed the option "-Q" to enable "SASL quiet mode" in the tool 
> ldapsearch. Without this flag, ldapsearch produces the same output as my 
> Python program.

Well, on my system I don't have such a noisy SASL debugging output. Even
when I compiled it myself. So maybe it's your local SASL installation. Maybe
you have time to dig into the OpenLDAP sources to find out what this -Q
switch really does. We can then decide whether it's feasible to expose that
in python-ldap.

Ciao, Michael.

subtree searches stopped working -- I am really stuck

[Joao S. O. B. <gw...@mp...>]

Hi all, hi Mike....

I am here developing my stuff when suddenly yesterday (ok, after an 
unexpected -related or not - reboot) ,all my python ldap Subtree 
searches return an empty result.

I am here unable to proceed with my work while I look for the possible 
causes for that.
I am using the 1.9.99pre-14 debian package. If this is a known issue (or 
a non issue that canbe prevented by option/cache control), I  like to know.

I also could not find in the docs information about the options that are 
available via get/set options.

Thanks

	JS
	-><-

Re: LDAP connection alive?

[Joao S. O. B. <gw...@mp...>]

Hi,

Thank you for the overview, Michael.

Sorry about the message subject.  Of course I should have posted it=20
with a proper subject, but I just released I had forgotten to change=20
the subject when it was already too late.


Tchau,

	JS
	-><-
On Monday 02 February 2004 05:20, Michael Str=F6der wrote:
> Joao S. O. Bueno wrote:
> > I apologize to posting this usage message to the devel list, but
> > it is my most handy resource right now:
>
> It's the only mailing list for python-ldap. So you're welcome to
> post here. But please use an appropriate subject line for your own
> topic. Thanks.
>
> > Which is the best way to check if a given connection is still
> > alive? Maybe try a search with SCOPE_BASE in a node, and check
> > for a time out? I'd need it not to be expensive to the ldap
> > server, neither to delay the thread.
>
> When I'm doing LDAP programming coaching this is a frequently asked
> question.
>
> My answer is always: Don't do it. It's a bad habit. Implement
> proper reconnecting instead.
>
> BTW: That's what ldap.ldapobject.ReconnectLDAPObject is for. But
> you have to understand what you're doing. And you have to
> understand the security implications of storing credentials in the
> ReconnectLDAPObject instance especially when pickling the instance
> on disk.
>
> Ciao, Michael.
>

LDAP connection alive?

[<mi...@st...>]

Joao S. O. Bueno wrote:
> 
> I apologize to posting this usage message to the devel list, but 
> it is my most handy resource right now:

It's the only mailing list for python-ldap. So you're welcome to post here. 
But please use an appropriate subject line for your own topic. Thanks.

> Which is the best way to check if a given connection is still alive?
> Maybe try a search with SCOPE_BASE in a node, and check for a time 
> out? I'd need it not to be expensive to the ldap server, neither to 
> delay the thread.

When I'm doing LDAP programming coaching this is a frequently asked question.

My answer is always: Don't do it. It's a bad habit. Implement proper 
reconnecting instead.

BTW: That's what ldap.ldapobject.ReconnectLDAPObject is for. But you have to 
understand what you're doing. And you have to understand the security 
implications of storing credentials in the ReconnectLDAPObject instance 
especially when pickling the instance on disk.

Ciao, Michael.

Re: Noisy output with SASL-Authentication

[Mauro C. <mci...@li...>]

Johannes Beigel wrote:

> Another question regarding SASL: Is there a python-ldap build for 
> windows with SASL-support? (Or: Are there any precompiled versions of 
> the Cyrus SASL library?) 

I should have one, if you're interested, but absolutely untested.

Mauro

Re: Noisy output with SASL-Authentication

[Johannes B. <jo...@br...>]

Hi.

[Sorry about the delay in my responses, but I'm only part-time working 
in my company and I don't read my email every day.]

Michael Ströder wrote:
> Try to set this globally not only in your LDAPObject instance:
> 
> ldap.set_option(ldap.OPT_DEBUG_LEVEL, 0)

Makes no difference (same output). I tried to set the option at 
different places (before and after initialize()/digest_md5()/
sasl_bind_s(), but that yields all the same result).

I use python-ldap, OpenLDAP and libsasl on a Debian (woody/sid) system. 
Maybe libsasl is compiled with debugging output turned on there? I also 
noticed the option "-Q" to enable "SASL quiet mode" in the tool 
ldapsearch. Without this flag, ldapsearch produces the same output as my 
Python program.

Another question regarding SASL: Is there a python-ldap build for 
windows with SASL-support? (Or: Are there any precompiled versions of 
the Cyrus SASL library?)

Ciao,
jojo.

Re: Noisy output with SASL-Authentication

[Joao S. O. B. <gw...@mp...>]

Hi there,

I apologize to posting this usage message to the devel list, but 
it is my most handy resource right now:

Which is the best way to check if a given connection is still alive? 
Maybe try a search with SCOPE_BASE in a node, and check for a time 
out? I'd need it not to be expensive to the ldap server, neither to 
delay the thread.

Regards,

	JS
	-><-

Re: Noisy output with SASL-Authentication

[<mi...@st...>]

Johannes Beigel wrote:

 >
 >   self.ldap = ldap.initialize(uri, trace_level=0)
 >   self.ldap.set_option(ldap.OPT_DEBUG_LEVEL, 0)


Try to set this globally not only in your LDAPObject instance:

ldap.set_option(ldap.OPT_DEBUG_LEVEL, 0)

Ciao, Michael.

Re: Noisy output with SASL-Authentication

[Johannes B. <jo...@br...>]

Hi.

Michael Ströder wrote:
> Johannes Beigel wrote:
>> I use python-ldap with SASL/Digest-MD5 authentication. With each 
>> sasl_bind_s() I get output like:
>>
>>   SASL/DIGEST-MD5 authentication started
>>   SASL username: admin@gandalf
>>   SASL SSF: 128
>>   SASL installing layers
> Post your code.

Sorry, I forgot. The relevant code snippet is this:

   self.ldap = ldap.initialize(uri)
   sasl = ldap.sasl.digest_md5(ADMIN_WITH_REALM, ADMIN_PW)
   self.ldap.sasl_bind_s(ADMIN_DN, sasl)

After reading your mail, I also tried the following lines instead of the 
simple call to ldap.initialize() without a change in the output of the 
program:

   self.ldap = ldap.initialize(uri, trace_level=0)
   self.ldap.set_option(ldap.OPT_DEBUG_LEVEL, 0)

But I guess, 0 is the default value for OPT_DEBUG_LEVEL and trace_level 
anyway. (For trace_level this is documented in python-ldap documentation.)

Ciao,
jojo.

Re: Noisy output with SASL-Authentication

[<mi...@st...>]

Johannes Beigel wrote:
> 
> I use python-ldap with SASL/Digest-MD5 authentication. With each 
> sasl_bind_s() I get output like:
> 
>   SASL/DIGEST-MD5 authentication started
>   SASL username: admin@gandalf
>   SASL SSF: 128
>   SASL installing layers

Post your code.

Watch out for:
ldap.initialize(... , trace_level=) and 
ldap.set_option(ldap.OPT_DEBUG_LEVEL, ... )

Ciao, Michael.

Noisy output with SASL-Authentication

[Johannes B. <jo...@br...>]

Hello.

I use python-ldap with SASL/Digest-MD5 authentication. With each 
sasl_bind_s() I get output like:

   SASL/DIGEST-MD5 authentication started
   SASL username: admin@gandalf
   SASL SSF: 128
   SASL installing layers

Is there a way to suppress this output (maybe with some option, I can 
set with set_option())?

Thanks in advance,
jojo.

ANN: python-ldap-2.0.0pre19

[<mi...@st...>]

Find a new pre-release of python-ldap:

   http://python-ldap.sourceforge.net/

python-ldap provides an object-oriented API to access LDAP directory
servers from Python programs. It mainly wraps the OpenLDAP 2.x libs for
that purpose. Additionally it contains modules for other LDAP-related
stuff (e.g. processing LDIF, LDAPURLs and LDAPv3 schema).

----------------------------------------------------------------
Released 2.0.0pre19 2004-01-22

Changes since 2.0.0pre18:

Modules/:
* LDAPObject.c:
   Most deprecated functions of OpenLDAP C API are not used anymore.
* functions.c:
   Removed unused default_ldap_port().
* constants.c:
   Removed unused or silly constants
   AUTH_KRBV4, AUTH_KRBV41, AUTH_KRBV42, URL_ERR_BADSCOPE, URL_ERR_MEM
* errors.c:
   Fixed building with OpenLDAP 2.2.x
   (errors caused by negative error constants in ldap.h)

ldap.ldapobject.LDAPObject:
* Removed unused wrapper methods uncache_entry(), uncache_request(),
   url_search(), url_search_st() and url_search_s()
* New wrapper methods for all the _ext() methods in _ldap.LDAPObject.

ldap.modlist:
* Some performance optimizations and simplifications
   in function modifyModlist()

Delivery Status Notification (Failure)

[Mail D. S. <MAI...@ma...>]

The following message to <che...@e-...> was undeliverable.
The reason for the problem:
5.1.0 - Unknown address error 550-'Command RCPT User <che...@e-...> not OK'

Delivery Status Notification (Failure)

[Mail D. S. <MAI...@ma...>]

The following message to <di...@ra...> was undeliverable.
The reason for the problem:
5.1.0 - Unknown address error 550-'Message content rejected'

Delivery Status Notification (Failure)

[Mail D. S. <MAI...@ma...>]

The following message to <di...@ap...> was undeliverable.
The reason for the problem:
5.1.0 - Unknown address error 553-'No mailbox here by that name, sorry (#5.7.1)'

Delivery Status Notification (Failure)

[Mail D. S. <MAI...@ma...>]

The following message to <di...@rs...> was undeliverable.
The reason for the problem:
5.1.0 - Unknown address error 550-'5.7.1 Message content rejected'

Delivery failure

[<MAI...@ya...>]

Message from yahoo.com.
Unable to deliver message to the following address(es).

<11...@ya...>:
This user doesn't have a yahoo.com account (11...@ya...) [0]

<11...@ya...>:
This user doesn't have a yahoo.com account (11...@ya...) [0]

--- Original message follows.

The original message is over 5K. Message truncated.

Return-Path: <pyt...@li...>
Received: from 212.123.84.82  (EHLO mailr-2.tiscali.it) (212.123.84.82)
  by mta113.mail.scd.yahoo.com with SMTP; Tue, 20 Jan 2004 11:18:57 -0800
Received: from ppp-82-84-96-162.cust-adsl.tiscali.it (82.84.96.162)
  by mailr-2.tiscali.it with SMTP; 20 Jan 2004 20:17:08 +0100
Message-ID: <002001c3dfec$c2edd06e$78a2fe58@ktgsqqjufmqqcb>
Reply-To: "=?windows-1251?B?ys7N0cDL0sjNw87CwN8gys7Mz8DNyN8=?=" <ko...@ke...>
From: "=?windows-1251?B?ys7N0cDL0sjNw87CwN8gys7Mz8DNyN8=?=" <pyt...@li...>
To: <101...@qu...>,
	 <101...@bi...>,
	 <101...@10...>,
	 <101...@co...>,
	 <101...@co...>,
	 <10...@go...>,
	 <10...@di...>,
	 <10...@e-...>,
	 <101...@ra...>,
	 <102.24@fidonet>,
	 <10...@im...>,
	 <102...@ub...>,
	 <102...@ub...>,
	 <102...@co...>,
	 <102...@co...>,
	 <10...@sm...>,
	 <1033816448@p126.f4.n5093.z2.ftn...>,
	 <103...@co...>,
	 <103...@co...>,
	 <10...@fr...>,
	 <1042.50@fidonet>,
	 <10...@ra...>,
	 <105...@re...>,
	 <105...@re...>,
	 <105...@ko...>,
	 <105...@bi...>,
	 <10...@di...>,
	 <106...@co...>,
	 <106...@co...>,
	 <106...@co...>,
	 <106...@sa...>,
	 <106...@pa...>,
	 <10...@ww...>,
	 <107664.1455
Subject: =?windows-1251?B?0vDl7ejt4zog8e/l9uj06OrgIO/w7uTg5iDv7iDy5evl9O7t8y4=?=
Date: Tue, 20 Jan 2004 22:09:56 +0300
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_007A_01C2A9A6.19F11222"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000

This is a multi-part message in MIME format.

------=_NextPart_000_007A_01C2A9A6.19F11222
Content-Type: text/plain;
	charset="windows-1251"
Content-Transfer-Encoding: quoted-printable


------=_NextPart_000_007A_01C2A9A6.19F11222
Content-Type: text/html;
	charset="windows-1251"
Content-Transfer-Encoding: quoted-printable

<HTML><HEAD><TITLE></TITLE>
</HEAD>
<BODY bgcolor=3D#FFFFFF leftmargin=3D5 topmargin=3D5 rightmargin=3D5=20=
bottommargin=3D5>
<FONT size=3D2 color=3D#000000 face=3D"Arial">
<DIV align=3Dcenter><FONT size=3D1 color=3D#FFFFFF><B></B></FONT></DIV>
<DIV align=3Dcenter><TABLE border=3D1 cellpadding=3D4 bordercolor=3D#00=
0000 cellspacing=3D-1>
<TR valign=3Dtop>
<TD width=3D266 valign=3Dtop><FONT size=3D2 color=3D#000000 face=3D"Ari=
al">
<DIV align=3Dcenter><FONT size=3D3>=CA=CE=CD=D1=C0=CB=D2=C8=CD=C3=CE=C2=
=C0=DF =CA=CE=CC=CF=C0=CD=C8=DF</FONT></DIV>
<DIV align=3Dcenter><FONT size=3D6 color=3D#000080><B>=ABA V V A L L=20=
O N=BB</B></FONT></DIV>
</FONT>
</TD>
<TD width=3D370 valign=3Dtop><FONT size=3D2 color=3D#000000 face=3D"Ari=
al">
<DIV><FONT size=3D3 color=3D#000080><B>&nbsp;</B></FONT></DIV>
<DIV align=3Dcenter><FONT size=3D3 color=3D#000080><B>=CE=D2=CA=D0=CE=C9=
=D2=C5 =C2=CE=C7=CC=CE=C6=CD=CE=D1=D2=C8 =C2=C0=D8=C5=C9 =CA=CE=CC=CF=C0=
=CD=C8=C8</B></FONT></DIV>
</FONT>
</TD>
</TR>
</TABLE>
</DIV>
<DIV align=3Dcenter>---------------------------------------------------=
-----------------------------------------------------------------------=
---------</DIV>
<DIV align=3Dcenter><FONT size=3D1 color=3D#FFFFFF><B> =D1=EA=EE=EB=FC=EA=
=EE =F1=EF=E5=F0=EC=E0=F2=E0=E7=EE=E8=E4=EE=E2 =F3 =E3=EE=EC=EE=F1=E5=EA=
=F1=F3=E0=EB=EE=E2? =CF=EE=EB=ED=FB=E9 =F0=EE=F2 =E8 =E2 =EF=EE=EF=E5=20=
=ED=E5=EC=ED=EE=E3=EE.</B></FONT></DIV>
<DIV align=3Dcenter><B>&nbsp;&nbsp;&nbsp;&nbsp;</B><FONT size=3D3><B>=CF=
=D0=C8=C3=CB=C0=D8=C0=C5=CC =C2=C0=D1 =CF=D0=C8=CD=DF=D2=DC =D3=D7=C0=D1=
=D2=C8=C5 =C2 =C1=C8=C7=CD=C5=D1-=D2=D0=C5=CD=C8=CD=C3=C5:</B></FONT></=
DIV>
<DIV align=3Dcenter><FONT size=3D5><B><U>=C3=EE=EB=EE=F1 =EA=EE=EC=EF=E0=
=ED=E8=E8: =F1=EF=E5=F6=E8=F4=E8=EA=E0 =EF=F0=EE=E4=E0=E6 =EF=EE =F2=E5=
=EB=E5=F4=EE=ED=F3</U></B></FONT></DIV>
<DIV align=3Dcenter><B>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;</B><FONT size=3D3><B>&nbsp;30-31 =FF=ED=E2=E0=F0=FF 2004 =E3=EE=
=E4=E0</B></FONT></DIV>
<DIV align=3Dcenter><FONT size=3D1 color=3D#FFFFFF><B></B></FONT></DIV>
<DIV align=3Dcenter><TABLE border=3D1 cellpadding=3D4 bordercolor=3D#00=
0000 cellspacing=3D-1>
<TR valign=3Dtop>
<TD width=3D162 valign=3Dtop><FONT size=3D2 color=3D#000000 face=3D"Ari=
al">
<DIV>=D6=C5=CB=DC =D2=D0=C5=CD=C8=CD=C3=C0</DIV>
</FONT>
</TD>
<TD width=3D474 valign=3Dtop><FONT size=3D2 color=3D#000000 face=3D"Ari=
al">
<DIV>=CF=F0=E0=EA=F2=E8=F7=E5=F1=EA=EE=E5 =EE=F1=E2=EE=E5=ED=E8=E5 =E8=20=
=EE=F2=F0=E0=E1=EE=F2=EA=E0 =F3=EC=E5=ED=E8=E9 =E8 =ED=E0=E2=FB=EA=EE=E2=
 =E4=EB=FF =FD=F4=F4=E5=EA=F
*** MESSAGE TRUNCATED ***



.

Delivery Status Notification (Failure)

[Mail D. S. <MAI...@ma...>]

The following message to <ie...@ma...> was undeliverable.
The reason for the problem:
5.1.0 - Unknown address error 550-'5.1.1 <ie...@ma...>... User unknown'