[Phpgroupware-tracker] [Bug #2159] pop3 error 'ERR Command line too long'

[nobody]

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

Changes by: Angelo Tony Puglisi <address@hidden>
Date: 2003-Jan-09 16:36 (America/New_York)

------------------ Additional Follow-up Comments ----------------------------
I'm gonna guess right now that is has to do with the RedHat php wanting to use 
TLS on port 110, so when it does not happen, as with the pop3 socket class, it 
sends some extra stuff to the client reporting as much.

If I'm guessing right, it's no big deal. Hopefully it only needs a tweak to 
tell it is OK for that extra line to come from the server. I actually did this 
in the IMAP sockets class during some random work on it recently.




=================== BUG #2159: FULL BUG SNAPSHOT ===================


Submitted by: datenpunk               Project: phpGroupWare                 
Submitted on: 2003-Jan-08 16:22
Category:  email                      Bug Group:  0.9.14.001 release        
Severity:  5 - Major                  Priority:  Normal                     
Resolution:  None                     Assigned to:  angles                  
Status:  Open                         Component Version:  None              
Platform Version:  Linux - RedHat     Reproducibility:  None                

Summary:  pop3 error 'ERR Command line too long'

Original Submission:  Trying to log in to pop3 the error 'ERR Command line too 
long' occurs.
Doing a $str = trim($str); in msg2socket() (class.network.inc.php) solves the 
problem somehow.
It seems as if there is blank or something like that which breakes the pop3 
proto.

I say somehow because there is a:
STAT::+OK Mailbox open, 6 messages 
but there are no emails visible.

So the trim seems to prevent the session from breaking completely but doesn't 
solve the whole problem.

The fct is called from email/inc/class.mail_dcom_pop3_sock.inc.php

I also did an update from cvs - the same problem.
FYI: I don't have IMAP support compiled into php.

Greetings

Daniel [datenPUNK] Khan

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

-------------------------------------------------------
Date: 2003-Jan-09 16:36             By: angles
I'm gonna guess right now that is has to do with the RedHat php wanting to use 
TLS on port 110, so when it does not happen, as with the pop3 socket class, it 
sends some extra stuff to the client reporting as much.

If I'm guessing right, it's no big deal. Hopefully it only needs a tweak to 
tell it is OK for that extra line to come from the server. I actually did this 
in the IMAP sockets class during some random work on it recently.


-------------------------------------------------------
Date: 2003-Jan-09 15:55             By: datenpunk
It's the default daemon.
Change:
/* $Id: class.network.inc.php,v 1.8.2.4 2002/09/01 13:37:17 skeeter Exp $ */

-------------------------------------------------------
Date: 2003-Jan-09 14:08             By: angles
Anyone know of the API file class.network.inc.php has been changed recently? 
Also, what POP3 server are you using, the stock RedHat one, U-Wash ?



CC List
*******

CC Address                          | Comment
------------------------------------+-----------------------------
address@hidden           | fyi



No files currently attached


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