Thread: [sqwebmail] sqwebmail problem with Chinese attachment filename
Brought to you by:
mrsam
From: John <aq...@ea...> - 2012-03-02 03:15:51
|
We upgraded sqwebmail from 5.1.2 to 5.5.3 recently, and got two problems with attachments with Chinese filenames. 1. regardless of utf-8 or CP936 encoding I choice, new messages with Chinese attachment filenames will display correctly, including the Chinese filename of the attachments. However when clicking "Display" or "Download" button, sqwebmail always prompts to download into message.dat, ie, these two buttons do not understand the correct filename nor understand the file extension of those attachments, even though sqwebmail displayed those filenames correctly in Chinese. 2. 5.1.2 was installed when sqwebmail supported gb2312 encoding, so we have many GBs of messages encoded in gb2312. Unfortunately new sqwebmail doesn't support gb2312 any more, so I have to use utf-8 or CP936 encoding. When opening old messages (encoded in gb2312), the email Subject and body are displayed correctly, however those attachments with Chinese filenames show some messed stuff. And they also share the same problem with Problem 1 above, ie, "Display" or "Download" button would prompt to download them as "message.dat". This is true for both utf-8 or CP936 encoding. The server is Centos, and I compile by hand, the relevant configuration flag I tried including "--enable-unicode=CP936 --enable-mimecharset=CP936" or "--enable-unicode=utf-8 --enable-mimecharset=utf-8", both got the same problem. I did change that CHARSET file accordingly and restart sqwebmail/apache when changing these encodings. utf-8 should allow characters in multiple languages. Would you advise how I should try to help solve these problems? Thank you! |
From: Sam V. <mr...@co...> - 2012-03-02 04:39:54
|
John writes: > We upgraded sqwebmail from 5.1.2 to 5.5.3 recently, and got two problems > with attachments with Chinese filenames. > > 1. regardless of utf-8 or CP936 encoding I choice, new messages with Chinese > attachment filenames will display correctly, including the Chinese filename > of the attachments. However when clicking "Display" or "Download" button, > sqwebmail always prompts to download into message.dat, ie, these two buttons > do not understand the correct filename nor understand the file extension of > those attachments, even though sqwebmail displayed those filenames correctly > in Chinese. There are many different factors, not at least of the sending mail's client compliance with RFC 2231, as well as the browser's capabilities. You'll need to look at the message's MIME headers. > 2. 5.1.2 was installed when sqwebmail supported gb2312 encoding, so we have > many GBs of messages encoded in gb2312. Unfortunately new sqwebmail doesn't > support gb2312 any more, so I have to use utf-8 or CP936 encoding. When The current version of sqwebmail uses the system iconv library for all character set conversions. > The server is Centos, and I compile by hand, the relevant configuration flag > I tried including "--enable-unicode=CP936 --enable-mimecharset=CP936" or "-- None of these options are present any more, sqwebmail uses uses all character sets supported by iconv. > enable-unicode=utf-8 --enable-mimecharset=utf-8", both got the same > problem. I did change that CHARSET file accordingly and restart > sqwebmail/apache when changing these encodings. The CHARSET file should specify utf-8. > utf-8 should allow characters in multiple languages. Would you advise how I > should try to help solve these problems? Thank you! The default contents of CHARSET should be sufficient. |
From: Sam V. <mr...@co...> - 2012-03-02 04:42:05
|
John writes: > We upgraded sqwebmail from 5.1.2 to 5.5.3 recently, and got two problems > with attachments with Chinese filenames. > > 1. regardless of utf-8 or CP936 encoding I choice, new messages with Chinese > attachment filenames will display correctly, including the Chinese filename > of the attachments. However when clicking "Display" or "Download" button, > sqwebmail always prompts to download into message.dat, ie, these two buttons > do not understand the correct filename nor understand the file extension of > those attachments, even though sqwebmail displayed those filenames correctly > in Chinese. There could be a number of factors that affect the browser's behavior, including whether the sending mail client complies with RFC 2231, for MIME header parameter encoding, as well as the browser implementation. You'll need to look at the message's MIME headers. > many GBs of messages encoded in gb2312. Unfortunately new sqwebmail doesn't > support gb2312 any more, sqwebmail now uses the system iconv library, which should certainly have support for gb2312. > The server is Centos, and I compile by hand, the relevant configuration flag > I tried including "--enable-unicode=CP936 --enable-mimecharset=CP936" or "-- None of these options have any effect any more. sqwebmail will use all character sets supported by your system iconv library. > enable-unicode=utf-8 --enable-mimecharset=utf-8", both got the same > problem. I did change that CHARSET file accordingly and restart > sqwebmail/apache when changing these encodings. > > utf-8 should allow characters in multiple languages. Would you advise how I > should try to help solve these problems? Thank you! The default CHARSET setting of UTF-8 should be sufficient. |