phpgroupware-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Phpgroupware-tracker] [Bug #1992] Warning: Couldn't open stream {local


From: nobody
Subject: [Phpgroupware-tracker] [Bug #1992] Warning: Couldn't open stream {localhost:143}INBOX in /.../phpg.../email/inc/class.mail_dcom_imap.inc.php on line 214
Date: Thu, 10 Apr 2003 03:16:06 -0400

=================== BUG #1992: LATEST MODIFICATIONS ==================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=1992&group_id=509

Changes by: Rüdiger Götz <address@hidden>
Date: Thu 04/10/2003 at 07:16 (GMT)

------------------ Additional Follow-up Comments ----------------------------
I had the same problems on a Suse Linux 8.1 system and I could solve it by 
attaching "/novalidate-cert" at the address of the IMAP-Server like 
"123.123.123.123/novalidate-cert".





=================== BUG #1992: FULL BUG SNAPSHOT ===================


Submitted by: pkt                     Project: phpGroupWare                 
Submitted on: Mon 12/16/2002 at 03:37
Category:  email                      Bug Group:  0.9.14.001 release        
Severity:  5 - Major                  Priority:  Normal                     
Resolution:  None                     Assigned to:  None                    
Status:  Open                         Component Version:  CVS               
Platform Version:  Linux - SuSE       Reproducibility:  Every Time          

Summary:  Warning: Couldn't open stream {localhost:143}INBOX in 
/.../phpg.../email/inc/class.mail_dcom_imap.inc.php on line 214

Original Submission:  This bug occurs every time you set prefs and then enter 
the email app, or initially login to phpgw and then enter the email app. 
However, subsequent refreshings of the screen does not show this error. This 
seems to be just when you try to initialize the email app on first entry. It's 
almost as if the app tries to first-pass access email without having the 
user/password combo and then a subsequent iteration of the code grabs the 
user/pwd pair and then calls the email successfully. 

Follow-up Comments
*******************

-------------------------------------------------------
Date: Thu 04/10/2003 at 07:16       By: rgoetz
I had the same problems on a Suse Linux 8.1 system and I could solve it by 
attaching "/novalidate-cert" at the address of the IMAP-Server like 
"123.123.123.123/novalidate-cert".



-------------------------------------------------------
Date: Sun 12/22/2002 at 17:03       By: pkt
I have "fixed" this at least temporarily. I went to that file and on that line 
(214), I replaced the variable with the entry "143/notls" or something to that 
effect. My server is down now or I'd put the exact entry. 

-------------------------------------------------------
Date: Sun 12/22/2002 at 11:51       By: None
I experienced the same problems,  (0.9.14.001) but I am able to extra pop 
accounts

-------------------------------------------------------
Date: Wed 12/18/2002 at 19:54       By: None
I have the exact same issue with 0.9.14.001 tar or CVS. Also, tried the 
unstable. Issue persists. Email works fine be the server assignment localhost, 
127.0.0.1, host.domain.com, or 192.x.x.x. Occurs with the same frequency as 
above poster.

Note: May be unrelated, but not able to use extra pop accounts. Resorted to 
fetchmail as a temporary solution.

Red Hat 8, i386
Apache 2.x
PHP4 w/globals enabled.
Reproduced on two servers and many installations.

Richard Harmonson, RHCE


CC list is empty


No files currently attached


For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=1992&group_id=509




reply via email to

[Prev in Thread] Current Thread [Next in Thread]