php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #21914 imap_open() fails with iMail POP3 server
Submitted: 2003-01-27 22:20 UTC Modified: 2003-06-11 16:38 UTC
Votes:1
Avg. Score:5.0 ± 0.0
Reproduced:1 of 1 (100.0%)
Same Version:0 (0.0%)
Same OS:1 (100.0%)
From: jaime at iguana-farm dot com Assigned:
Status: Not a bug Package: IMAP related
PHP Version: 4.2.3 OS: RedHat 7.2
Private report: No CVE-ID: None
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If you forgot your password, you can retrieve your password here.
Password:
Status:
Package:
Bug Type:
Summary:
From: jaime at iguana-farm dot com
New email:
PHP Version: OS:

 

 [2003-01-27 22:20 UTC] jaime at iguana-farm dot com
I am to open a connection to an ipSwitch iMail ver 6.06 POP3 server using imap_open(). I have tried this under RedHat 7.2 and FreeBSD with PHP versions 4.2.3, 4.1.2 with the same results. Under FreeBSD ver 4.0.6 it works.

[jaime@lizard test]$ php -q test.php 
<br />
<b>Warning</b>:  Couldn't open stream {mail.seismicom2.com:110/pop3}INBOX
 in <b>.../test/test.php</b> on line <b>3</b><br />
Array
(
    [0] => Retrying CRAM-MD5 authentication after 
    [1] => Retrying CRAM-MD5 authentication after Invalid userid/password
    [2] => Retrying CRAM-MD5 authentication after illegal command
    [3] => Retrying CRAM-MD5 authentication after authentication exchange failed
    [4] => Can not authenticate to POP3 server: authentication exchange failed
)

[jaime@lizard test]$ cat test.php 
<?php

$mbox = imap_open("{mail.imailserver.com:110/pop3}INBOX", "user", "passwd");
print_r(imap_errors());
?>

Is this a c-client problem?

Thanks,
Jaime

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2003-01-27 23:03 UTC] sniper@php.net
Yes, this is most likely a c-client problem.
But do try this call:

imap_open("{mail.imailserver.com:110/pop3/notls}INBOX", ..

(notice the 'notls' there..)

And what versions of c-client did you use to build
4.0.6 and 4.2.3? And what were the configure lines used?
It also depends a lot on how the c-client was build
and with what options..

 [2003-02-07 23:53 UTC] sniper@php.net
No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Open". Thank you.


 [2003-06-11 16:03 UTC] davidkoopman at yahoo dot com
I have the same problem...
$type = "pop";
$aServer = "mail.mycaboodle.com";
$spec = "{".$aServer.":".$aPort."/$type/notls"."}"."INBOX";
$mbox = @imap_open($spec, $aAccount['user_name'], $aAccount['password']);
print_r(imap_errors());
 results in:
rray
(
    [0] => Retrying CRAM-MD5 authentication after 
    [1] => Retrying CRAM-MD5 authentication after Invalid userid/password
    [2] => Retrying CRAM-MD5 authentication after illegal command
    [3] => Retrying CRAM-MD5 authentication after authentication exchange failed
    [4] => Can not authenticate to POP3 server: authentication exchange failed
)

I am using imap-2002c1 for c-client under RH7.2.  I am struggling with this because I can log in via command line.  The mail server I am trying to connect to: mail.mycaboodle.com is running Imail 8.00, which is the only mail server I have seen in my hunting for a solution that this error occurs on.
 [2003-06-11 16:14 UTC] jaime at iguana-farm dot com
The CRAM-MD5 problem is a compatiblity problem beween c-client (all versions)  and IMail. c-client folks claim that IMail is "non-compliant" while ipSwitch has no interest in correctting the problem.

My workaround was to patch up the c-client pop3.c to check if is connection to an iMail server and set auths=0 in the function pop3_auth().

Jaime
 [2003-06-11 16:38 UTC] derick@php.net
Not a bug in PHP then -> bogus
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Fri Dec 27 14:01:29 2024 UTC