#2714 SM doesn't correctly forward mails with differen encoding

closed-fixed
nobody
Compose (426)
7
2010-06-22
2010-04-30
Tamás Németh
No

Since hungarian language switched to UTF-8, I have problems with
forwarding mails composed using ISO-8859-2, especially when it
contains attachments with names containing (ISO-8859-2 encoded)
accentuated characters.

For example I try to forward a certain message (gzipped and attached to this
report) which contains some attachments, the messages loses its attachemts
during the forwarding process. I can see the attachments during editing
the message to be forwarded (see the also attached forwarding.jpg), but
they are missing from the messages sent. Neither the recipient sees them
nor me in the message saved into my Send folder.

I can reproduce the bug by:

Forwarding the attached ISO-8859-2 encoded message
(1241597121.Vca07I4ac355M208738.titanic:2,S) on an UTF-8 encoded
SquirrelMail 1.4.20 installation.

Discussion

  • Tamás Németh
    Tamás Németh
    2010-04-30

    Attachment name displayed incorrectly during composition (it was displayed correctly upon receipt, and all the attachments will disappear upon sending the message.)

     
    Attachments
  • Tamás Németh
    Tamás Németh
    2010-04-30

    • priority: 5 --> 7
     
  • Tamás Németh
    Tamás Németh
    2010-04-30

    • summary: SM doesn\'t correctly forward mails with differen encoding --> SM doesn't correctly forward mails with differen encoding
     
  • Tamás Németh
    Tamás Németh
    2010-04-30

    This bug is very annoying because of the many microsoft clients still using iso-8859-2. A reasonable workaround is to forward received mails attached to the forwarding mail, but users don't like it. Anyway, SquirrelMail should do an overall charset conversion on the message (including attachmnet filenames!) upon the initial composition of the forwarding mail. Thank you in advance.

     
  • I have a similar issue when replying an html mail with different encoding (squirrelmail UTF-8, mail sent in ISO8859-P1 charset).
    The client must sent a html mail format, it doesn't happen when the client sents a text only or text+html mail to squirrelmail.
    I found this in squirrelmail 1.4.16 and 1.4.20.

     
    • status: open --> pending-fixed
     
  • Please try the attached patch. The line numbers in it might be slightly off since it is based on 1.4.21SVN with some unpublished patches. If it doesn't apply automatically, just inspect the patch file yourself and make the change inside (simple).

     
  • Tamás Németh
    Tamás Németh
    2010-06-22

    OK, I tried it and it seems to work for us.

     
  • Tamás Németh
    Tamás Németh
    2010-06-22

    • status: pending-fixed --> open-fixed
     
    • status: open-fixed --> closed-fixed
     
  • Thanks for the feedback.

     
  • I've re-opened comments on this tracker, but I suspect that this has nothing to do with SquirrelMail (or we'd have heard of it by now). If printing doesn't work on ANY SquirrelMail page, then you could get the full HTML source of one such page and upload it so we can open that HTML in IE ourselves and see if we can print it. That'd be the fastest test, but I am pretty sure the answer will be "works for me." Perhaps your environment is doing things with the source code or....

     
  • Grrr, wrong tracker. Please ignore previous comment.