ID:               33349
 User updated by:  benjamin dot malynovytch at libertic dot fr
 Reported By:      benjamin dot malynovytch at libertic dot fr
 Status:           Open
 Bug Type:         IMAP related
 Operating System: *
 PHP Version:      5CVS-2005-06-20
 New Comment:

I gave a try on PHP 4.3.11, still not working.


Previous Comments:
------------------------------------------------------------------------

[2005-06-20 16:01:42] root at ka-rel dot cz

I'm experiencing the same behaviour with certain messages (mostly spam
but not always). A sample message is located at
http://ka-rel.cz/imap/bad001.tmp.

Whenever imap_fetchstructure function tries to analyze the message, cpu
gets to 100% and hangs (on NT 4.0 Server) or displays the "crash
message" (on WinXP), requesting to send it to Microsoft.

Till now, I've noticed that the bad messages have improperly set
boundary strings - maybe this confuses the function and results to
unability to parse individual parts of message. Also, such messages are
not decoded correctly if opened in a mail client.


PHP 4.3.3
IMAP c-Client Version 2001
WinXP: php_imap.dll, 593920 bytes, 24th August 2003
WinNT: php_imap.dll, 602112 bytes,  6th June   2005

------------------------------------------------------------------------

[2005-06-20 15:11:36] benjamin dot malynovytch at libertic dot fr

iliaa and sniper, you'll find the asked informations in your
mailboxes.

Is it possible that php5 doesn't work properly, when php4 does ?
It tried the application on an "old" box, using php4(4.3.4), and it
works fine (even on the message-of-death).
I haven't tried out on the production box though, cause I can't swap so
easily on php4 (other applications will dropp).

I also noticed, that a similar bug had been corrected in php 4.0.4
(imap_fetchstructure crashing) (Changelog). Is it possible that php5
has the same bug again ?

------------------------------------------------------------------------

[2005-06-20 11:54:59] [EMAIL PROTECTED]

We're interested in the 'message-of-death' only. Just export that
message and put it online or send via email to [EMAIL PROTECTED] and
[EMAIL PROTECTED]

Your initial example script is a bit odd though,
what EXACTLY (for real!) is $mbox_path set to? 


------------------------------------------------------------------------

[2005-06-20 11:32:27] benjamin dot malynovytch at libertic dot fr

Illia said:
>If the problem persists, please provide a URL to the complete text of
the message that causes the hang.

As I said just before, no output message are created. No error,
nothing, except the generated code that had been flushed (cleanly)
before the crash.
I can't even give you access to the page the generates this error: it's
placed on an intranet.

------------------------------------------------------------------------

[2005-06-20 10:24:02] [EMAIL PROTECTED]

Do not add any strace output here if not asked for.
Please provide the information Ilia asked before.


------------------------------------------------------------------------

The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
    http://bugs.php.net/33349

-- 
Edit this bug report at http://bugs.php.net/?id=33349&edit=1

Reply via email to