[Tickets #14807] Re: Broken File Names in Attachments when using ActiveSync

[noreply at bugs.horde.org]

BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE  
E-MAIL-ADRESSE WERDEN NICHT GELESEN.

Ticket-URL: https://bugs.horde.org/ticket/14807
------------------------------------------------------------------------------
  Ticket           | 14807
  Aktualisiert Von | rene.marth at hetzner.com
  Zusammenfassung  | Broken File Names in Attachments when using ActiveSync
  Warteschlange    | IMP
  Version          | 6.2.21
  Typ              | Bug
  Status           | Not A Bug
  Priorität        | 1. Low
  Milestone        |
  Patch            |
  Zuständige       | Michael Rubinsky
------------------------------------------------------------------------------


rene.marth at hetzner.com (2018-11-22 07:50) hat geschrieben:

What do you think about https://www.ietf.org/rfc/rfc2388 ?

3. Definition of multipart/form-data
[...]
"Field names originally in non-ASCII character sets may be encoded
    within the value of the "name" parameter using the standard method
    described in RFC 2047."

4.4 Other attributes
[...]
The original local file name may be supplied as well, either as a
    "filename" parameter either of the "content-disposition: form-data"
    header or, in the case of multiple files, in a "content-disposition:
    file" header of the subpart. The sending application MAY supply a
    file name; if the file name of the sender's operating system is not
    in US-ASCII, the file name might be approximated, or encoded using
    the method of RFC 2231.

Isn't that exactly the method Thunderbird is using? (and that works  
with the tested mail clients)