Menu

#2613 Wrong headers decoding if splitted into multiple lines

open
nobody
5
2009-01-12
2009-01-12
No

Problem in all versions (>=1.4.11 including 1.4.17) as well as in 1.5.2 SVN.

If a long attachment name was splited into multiple lines, eg (from raw message headers):
------=_20090111224249_58870
Content-Type: application/msword; name="
=?iso-8859-2?Q?Poj=EAcie_zagospodarowania_turystycznego_i_rekreacyjnego.d?=
oc"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="
=?iso-8859-2?Q?Poj=EAcie_zagospodarowania_turystycznego_i_rekreacyjnego.d?=
oc"

it will be decoded (and displayed) incorrectly in 1.4.17 as:
"2;Pojęcie zagospodarowania turystycznego i rekreacyjnego.d oc" (2; at beginning and additional space between ".d" and "oc" extension").

BTW, this email was sent by Squirrelmail 1.4.11 :(

Could you fix this?

Regards,
Jacek

Discussion

  • Paul Lesniewski

    Paul Lesniewski - 2009-04-03

    Thanks very much for your report. I have just committed a potential fix for this to 1.5.2SVN. If you could test it, that would help toward the eventual back-porting of that fix into our stable branch (1.4.x).

    If you just can't wait for that fix to be taken back into 1.4.x, you can use the fixed copy of class/deliver/Deliver.class.php that I have attached here. It is branched from 1.4.18SVN.

    No matter which you try, PLEASE PLEASE PLEASE PROVIDE FEEDBACK.

     
  • Paul Lesniewski

    Paul Lesniewski - 2009-04-03

    Backport of foldLine fix from DEVEL to STABLE

     
  • Jacek Kalinski

    Jacek Kalinski - 2009-04-03

    Thanks for your answer.
    Mail send from SM with this patch (SVN 13513) is correctly recognized by both versions (1.4.x, 1.5.x including SVN 13513).
    Mail send from previous versions of SM 1.5.x (before this patch) are still recognized incorrectly (with space in name), but I think it is acceptable.

    So it is working for me.

     
  • Paul Lesniewski

    Paul Lesniewski - 2009-04-03

    Thanks very much for the feedback. Can you clarify how you tested 1.4.x? Did you use it as is or did you use the file attached to this tracker?

    Messages sent from SM before this fix are not supported, because they are broken.

     

Log in to post a comment.