to consider: http://de3.php.net/manual/de/function.ldap-get-entries.php

Note: ldap_get_entries returns true even if no results are found, like this:

echo $entries=ldap_get_entries(...);
will print Array.
You have to check for number of row in the Array like this:
if($entries["count"]==0) return false;
Hope this helped someone...

I've worked out a solution now. I have

function ldap_email_from_username( $p_username ) {

$t_ldap_organization = config_get( 'ldap_organization' );

$t_ldap_root_dn = config_get( 'ldap_root_dn' );

$t_ldap_uid_field = config_get( 'ldap_uid_field', 'uid' );
$t_search_filter = "(&$t_ldap_organization($t_ldap_uid_field=$p_username))";
$t_search_attrs = array(
    $t_ldap_uid_field,
    'mail',
    'dn',
);

$t_ldap_mail ='';
$t_ds = ldap_connect_bind();

if( $t_ds ) {
    $t_sr = ldap_search( $t_ds, $t_ldap_root_dn, $t_search_filter, $t_search_attrs );

    if( $t_sr ) {
        $t_info = ldap_get_entries( $t_ds, $t_sr );
        if( ( $t_info ) && ( $t_info['count'] > 0) && ( array_key_exists( 'mail', $t_info[0] ) ) ) {
             $t_ldap_mail = $t_info[0]['mail'][0];
        }
    }
    ldap_free_result( $t_sr );
}
ldap_unbind( $t_ds );

return $t_ldap_mail;
}

The most important point is the sequence

array_key_exists( 'mail', $t_info[0] )

Regrettably the problem still exists (I admit I have the error switches set to halt in case of php-problems).
As far as I can see the code has not been changed with respect to my findings -- please consider my proposal in the previous note.

I.e., I mean the sequence

$t_info = ldap_get_entries( $t_ds, $t_sr );

if( ( $t_info ) && ( $t_info['count'] > 0) && ( array_key_exists( 'mail',

$t_info[0] ) ) ) {

$t_ldap_mail = $t_info[0]['mail'][0];

}

I've seen that the ldap.api code in my freshly installed mantis 1.2.5 has been greatly enhanced.
Yet I still see the problem.

In my setting, I query the users' email adresses via the LDAP api from our AD-server. I suppose that in case of a nonexisting data element the AD server returns someting like a void container, so that the error handlings rules in core/ldap.api, lines 259 and 265 are too weak:

258         # If no matches, return null.

259         if ( count( $t_info ) == 0 ) {

260                 log_event( LOG_LDAP, "No matches found." );

261                 return null;

262         }

263

264         # Make sure the requested field exists

265         if( array_key_exists( $p_field, $t_info[0] ) ) {

In debug mode I get for problematic the message that the second agument of the array_key_exists expression, i.e., $t_info[0], is NULL.
The following patch fixes the problem in my case:

265         if( ( array_key_exists( 0, $t_info ) ) && ( array_key_exists( $p_field, $t_info[0] ) ) ) {

Hi tk,

Did you have a look at 0012960 ? That issue was recently fixed (although after the release of 1.2.5) and seems quite similar to the problem you reported. If that's the case, you may want to download a nightly build of 1.2.x to test and confirm.

Hi dregard,

yes, this is exactly what I've seen. I directly applied the patch attached to 0012960 and confirmed that this patch also works.
So anyone with higher access rights may mark this issue as a duplicate of 0012960 and close it as fixed in 1.2.5+

Thank you!

Thanks for taking the time to look for duplicates and confirming that it works. Closing as requested.