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

[Dr. Christian Böttger]

This mail is an automated notification from the bugs tracker
 of the project: phpGroupWare.

/**************************************************************************/
[bugs #2159] Latest Modifications:

Changes by: 
                Dr. Christian Böttger <address@hidden>
'Date: 
                Wed 04/21/04 at 08:50 (Europe/Berlin)

            What     | Removed                   | Added
---------------------------------------------------------------------------
         Assigned to | angles                    | None


------------------ Additional Follow-up Comments ----------------------------
no email application maintainer available






/**************************************************************************/
[bugs #2159] Full Item Snapshot:

URL: <http://savannah.gnu.org/bugs/?func=detailitem&item_id=2159>
Project: phpGroupWare
Submitted by: Daniel Khan
On: Wed 01/08/03 at 21:22

Category:  email
Item Group:  0.9.14.001 release
Severity:  5 - Average
Priority:  5 - Normal
Resolution:  None
Assigned to:  None
Status:  Open
Component Version:  None
Platform Version:  GNU/Linux - RedHat/Fedora
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: Wed 04/21/04 at 08:50         By: cboettger
no email application maintainer available

-------------------------------------------------------
Date: Fri 06/27/03 at 02:27         By: cw
Is this still a problem?

-------------------------------------------------------
Date: Thu 01/09/03 at 21: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: Thu 01/09/03 at 20: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: Thu 01/09/03 at 19: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
------------------------------------+-----------------------------
anglemail --AT-- free-source --DOT-- com | fyi









For detailed info, follow this link:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=2159>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/