[Tickets #9212] encoding of attached filenames with foreign caracters is not correct

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/9212
------------------------------------------------------------------------------
  Ticket             | 9212
  Created By         | luc.germain at usherbrooke.ca
  Summary            | encoding of attached filenames with foreign caracters
                     | is not correct
  Queue              | IMP
  Version            | 4.3.7
  Type               | Bug
  State              | Unconfirmed
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


luc.germain at usherbrooke.ca (2010-09-01 14:36) wrote:

When a file having foreign caracters is attached to a message and sent  
with IMP, the encoding does not follow exactly RFC 2231 section 4.  
Here is the header sent by IMP:

--=_3pfswe3aoqg4
Content-Type: text/plain;
  charset=UTF-8;
  name*="utf-8''Fichier%20attach%C3%A9.txt"
Content-Disposition: attachment;
  filename*="utf-8''Fichier%20attach%C3%A9.txt"
Content-Transfer-Encoding: quoted-printable

Ce fichier contient des mots avec des caract=C3=A8res accentu=C3=A9s.
--=_3pfswe3aoqg4--


The name*= and filename*= should NOT be surrounded by double quotes.  
The lines should be instead:

  name*=utf-8''Fichier%20attach%C3%A9.txt
and
  filename*=utf-8''Fichier%20attach%C3%A9.txt

Some clients (rightfully) ignore these lines when the double quotes  
are there, but they decode the name correctly when the double quotes  
are removed.