[Tickets #10788] Re: IMP crashes Apache when retrieving Exchange folders
bugs at horde.org
bugs at horde.org
Tue Nov 22 22:07:02 UTC 2011
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
Ticket URL: http://bugs.horde.org/ticket/10788
------------------------------------------------------------------------------
Ticket | 10788
Updated By | Michael Slusarz <slusarz at horde.org>
Summary | IMP crashes Apache when retrieving Exchange folders
Queue | IMP
Version | 5.0.14
Type | Bug
State | Duplicate
Priority | 1. Low
Milestone |
Patch |
Owners |
------------------------------------------------------------------------------
Michael Slusarz <slusarz at horde.org> (2011-11-22 15:07) wrote:
>>> Timestamp: Tue, 22 Nov 2011 07:21:11 +0100
> S: * OK Microsoft Exchange Server 2003 IMAP4rev1 server version
> 6.5.7638.1 (mailserver.bar) ready.
> C: [LOGIN Command - username: mcc1]
> S: 1 OK LOGIN completed.
> C: 2 LSUB "" *
> S: * LSUB () "/" "Sent Items"
> S: * LSUB () "/" Trash
> S: * LSUB () "/" Sent
> S: * LSUB () "/" Drafts
> S: 2 OK LSUB completed.
> C: 3 LSUB "" "Public Folders/*"
> S: 3 OK LSUB completed.
> C: 4 LIST "" *
> S: * LIST (\HasNoChildren) "/" Aufgaben
> ....
> S: 4 OK LIST completed.
> C: 5 LIST "" "Public Folders/*"
> ...
> S: * LIST (\HasNoChildren) "/" {30}
> S: [LITERAL DATA - 30 bytes]
> S:
> S: * LIST (\HasNoChildren) "/" "Public Folders/Whatever"
> ...
> S: 5 OK LIST completed.
> C: 6 LIST "" INBOX
> S: * LIST (\Marked \HasNoChildren) "/" INBOX
> S: 6 OK LIST completed.
> C: 7 LOGOUT
> S: * BYE Microsoft Exchange Server 2003 IMAP4rev1 server version
> 6.5.7638.1 signing off.
> S: 7 OK LOGOUT completed.
>
> Apparently the Exchange server gives the whole list of folders to
> IMP but it then fails to display. There stays a "Loading..."
> statement forever and a httpd process freaks out on server.
There is nothing wrong with this exchange (other than the fact that
Exchange doesn't list the INBOX as "subscribed", but we already work
around that).
You will need to debug further and find where your sever is having
issues. Try looking at javascript log on the browser or setting
Horde's logging to debug and then looking for errors.
More information about the bugs
mailing list