ID:               33500
 Comment by:       php at eikel dot org
 Reported By:      ed2019 at columbia dot edu
 Status:           Open
 Bug Type:         Feature/Change Request
 Operating System: RHEL4
 PHP Version:      4.3.10
 New Comment:

Hello,

this problem still exists in PHP 5.2.6. As stated by Mark Crispin [1]
this problem is probably a bug in the PHP IMAP implementation. Any
suggestions how to fix this problem?

Regards,
Benjamin

[1]
http://mailman2.u.washington.edu/pipermail/imap-uw/2005-June/000101.html


Previous Comments:
------------------------------------------------------------------------

[2008-06-20 15:04:41] josh_barth at hotmail dot com

If you happen to run across this error while attempting to connect to
an Exchange server.......  In my case Exchange 2007 from Ubuntu

Install Kerberos client i.e heimdal-client

Switch to the apache user....for Ubuntu that is "www-data":

su www-data

kinit [EMAIL PROTECTED] 'Mind the case [EMAIL PROTECTED]

klist 'Will show current ticket granting ticket and other tokens

Note: krbtgt will expire and this procedure will need to be repeated I
am currently researching a method to ensure an active krbtgt at all
times

Try testing with this script as the apache user, replacing ipaddress,
username, domainname and password.

<?php
$mbox =
imap_open("{ipaddress:993/imap/ssl/novalidate-cert/notls/debug}INBOX",
"domainname/username", "password") or
die(imap_last_error()."<br>Connection Failure!");

echo "<h1>Mailboxes</h1>\n";
$folders = imap_listmailbox($mbox, "{ipaddress:993}", "*");

if ($folders == false) {
    echo "Call failed<br />\n";
} else {
    foreach ($folders as $val) {
        echo $val . "<br />\n";
    }
}

echo "<h1>Headers in INBOX</h1>\n";
$headers = imap_headers($mbox);

if ($headers == false) {
    echo "Call failed<br />\n";
} else {
    foreach ($headers as $val) {
        echo $val . "<br />\n";
    }
}

imap_close($mbox);
?>

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

[2008-05-26 10:36:17] ruben at dedigate dot com

This issue is also in PHP5 ... there's no way to open an imap/pop
connection to an exchange2007 server that announces GSSAPI :-(

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

[2007-10-11 09:18:25] tma at gatehouse dot dk

FYI, the same problem appears when trying to use plain-text POP3
authentication against a Microsoft Exchange 2007 server.

IMHO, this is indeed a deficiency in PHP, and the solution is simple:
Expose the uw-imap mail_parameters() function in the PHP API.

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

[2005-06-29 15:04:31] ed2019 at columbia dot edu

I have also filed this bug with RedHat, see bug # 161826:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=161826 , as well
as to Mark Crispin ( author of the c-client imap library ), that
discussion is archived here:
http://mailman1.u.washington.edu/pipermail/imap-uw/2005-June/000091.html

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

[2005-06-28 19:06:58] ed2019 at columbia dot edu

I am the system administrator.  I appreciate your trying to screen out
non-bugs, but this is not a non-bug, but I am quite sure that this is a
real bug.

An IMAP server supports multiple methods of remote client
authentication.  Among them, GSSAPI and plain.  When a client connects,
the server advertises these auth methods and other options it supports,
for example, GSSAPI, PLAIN, etc.

The client then selects which AUTH method to use.  php's imap extension
is choosing to use the GSSAPI method, but I would like it to make a
different choice.  Or, after GSSAPI fails, I would like it to try the
PLAIN auth method.

There is, however, no way (to my knowledge, or in the documentation) to
get it to make that choice.  The underlying c-client library that php
uses to talk to imap servers supports making the choice, and the imap
servers themselves support it, but PHP does not.  I think that puts it
into the category of a 'bug' that belongs in PHP's bug system.

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

The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
    http://bugs.php.net/33500

-- 
Edit this bug report at http://bugs.php.net/?id=33500&edit=1

Reply via email to