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

[email protected]
Newsgroups gmane.comp.horde.bugs
Message-ID <[email protected]>
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 | [email protected]
  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
------------------------------------------------------------------------------


[email protected] (2018-11-22 07:37) hat geschrieben:

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.



-- 
bugs mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.