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

* Your Email Address
* Spam protection	Enter the letters below: . .. .. .. ..__ \| \|\ /\| \|\| \|[__) \|/\\| \/ \|__\|\|__\|\| \
Comment	> Roundcube has a setting for that issue. Why do you do not have it? > https://bugs.horde.org/ticket/4733 is 12 years ago. It's not very > likely that Microsoft will change their mind. So why not use a way > that every Client understand? > > It'a also wrong what Michael wrote in https://bugs.horde.org/ticket/4733#c9 > > " FYI, Opera, Thunderbird, and KMail (at a minimum) send w/ correct 2231 > encoding." > > As you see in my example this isn't the case for (at least) > Thunderbird. It encodes the Content-Type -> name attribute in 2047 > while using 2231 for the Content-Disposition -> filename attribute. > > And this is exact the option that Roundcube provide (2047/2231 > encoding). This seems to be the most compatible way to encode > non-ascii chars in attachment file names.
Attachment
Watch this ticket