#68 rc2a: a certain spam times out while opening

closed-works-for-me
None
5
2003-03-11
2003-02-19
K Yoder
No

I got this spam bounced around to my administrator
mailbox. If I try to open it with 1.4 release
candidate, the page loads for a while, then I get the
message "Fatal error: Maximum execution time of 60
seconds exceeded in
/usr/local/share/squirrelmail-1.4.0-rc2a/class/mime/Message.class.php
on line 484". I tried moving it to a different mailbox
and reading it from there, but same result. The same
message loads normally with no delay using 1.2.9. I
will attach the spam; it's a maildir message in courier.

Discussion

  • Logged In: YES
    user_id=285765

    Marc, I think this has something to do with mime parsing.
    Can this be fixed in 1.4 or will it be forwarded to 1.5?

     
    • assigned_to: nobody --> stekkel
     
  • Logged In: YES
    user_id=476981

    I downloaded the message and I can't reproduce it. What I
    need is the bodystructure of the message. With the info
    plugin you can requist the bodystructure by doing:
    UID FETCH #uid BODYSTRUCTURE
    with #uid the id in the message (see the url-link)
    Probably your imap server produces a wring bodystructure or
    we have a bug in our brodystructure parser.

     
  • K Yoder
    K Yoder
    2003-02-21

    Logged In: YES
    user_id=293425

    As you requested, here's output of "info":

    Request:
    A003 UID FETCH 185 BODYSTRUCTURE
    Response:
    Error in IMAP command received by server.

    I also tried with #185, same result. Also tried with some
    message ID's that weren't having this problem, same result.
    Maybe I'm not writing it correctly?

     
  • Logged In: YES
    user_id=476981

    you have to select the checkbox before the select inbox as
    well as the checkbox where you enter the bodystructure
    command.
    You can also try the latest cvs

     
    • status: open --> open-works-for-me
     
  • Logged In: YES
    user_id=476981

    Thnx for the bodystructure. I feeded it the bodystructure
    parser and I had no problems with it.
    I was using the latest CVS for the test.

     
    • status: open-works-for-me --> closed-works-for-me