#734 mime decoding message/rfc822 attachments

closed-fixed
9
2002-10-15
2002-06-18
No

I found a pretty nasty bug in the mime decoding of the
bodystructure.

If you forward a message with a subject containing a ")"
without a "(". for example: " test ) "
then the mime-decoding goes wrong because of the
mime_match_parenthesis function.
I will try to workout a sollution but it won't be easy :-(

The returned envelope structure in case of
message/rfc822 attachements causes the wrong
decoding.

Discussion

  • Marc Groot Koerkamp

    Logged In: YES
    user_id=476981

    correction:
    If the subject is:
    test " )
    then things goes wrong

     
  • Marc Groot Koerkamp

    Logged In: YES
    user_id=476981

    The problem was the missing check for literals in
    mime_match_parentheses (mime.php).

    The fix is in SM 1.3 DEVEL

     
  • Marc Groot Koerkamp

    • assigned_to: nobody --> stekkel
    • status: open --> open-fixed
     
  • Marc Groot Koerkamp

    Logged In: YES
    user_id=476981

    The problem was the missing check for literals in
    mime_match_parentheses (mime.php).

    The fix is in SM 1.3 DEVEL

     
  • Marc Groot Koerkamp

    Logged In: YES
    user_id=476981

    The problem was the missing check for literals in
    mime_match_parentheses (mime.php).

    The fix is in SM 1.3 DEVEL

     
  • Marc Groot Koerkamp

    • labels: 102904 --> Message Headers
    • milestone: --> IMAP Server Specific
     
  • Thijs Kinkhorst

    Thijs Kinkhorst - 2002-10-15
    • status: open-fixed --> closed-fixed
     
  • Thijs Kinkhorst

    Thijs Kinkhorst - 2002-10-15

    Logged In: YES
    user_id=285765

    Hello,

    Your report was filed against an old version of SquirrelMail. We
    have new releases out which have fixed many issues. Can you
    please test the most recent version - or even better the CVS
    version - and report if this issue still exists? Thanks!

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks