decoded filename in BODYSTRUCTURE

Use this forum if you want to discuss a problem or ask a question related to a hMailServer beta release.
Post Reply
alec
New user
New user
Posts: 5
Joined: 2009-06-16 10:24

decoded filename in BODYSTRUCTURE

Post by alec » 2009-06-16 10:35

I'm the Roundcube Webmail developer. One of our users requested issue which is related to hMailServer's BODYSTRUCTURE reply. For message part headers:

Code: Select all

Content-Type: application/x-zip-compressed; name="=?iso-8859-1?B?beT2LnppcA==?="
server returns:

Code: Select all

("APPLICATION" "X-ZIP-COMPRESSED" ("NAME" "mäö.zip")
The name is decoded and converted to Unicode. The problem is because Roundcube converts returned name again from iso-8859-1 (it's message charset) to unicode and filename is displayed wrong. More info here: http://trac.roundcube.net/ticket/1485920.
My question: is this described in any RFC that decoded parameter value must/should/can be converted to Unicode?

User avatar
martin
Developer
Developer
Posts: 6834
Joined: 2003-11-21 01:09
Location: Sweden
Contact:

Re: decoded filename in BODYSTRUCTURE

Post by martin » 2009-06-16 19:07

No, this is very much a real bug, and a fairly serious one.

It's the same bug which caused a similar problem reported in your forum:
http://trac.roundcube.net/ticket/1484969#comment:17

It was fixed in hMailServer 5.2, build 348. This build is currently alpha. A beta build will be up on the download page soon.

(I added your example above/below to the hMailServer automated test suite so that it's confirmed to continue work properly before every new build.)

Post Reply