[Tickets #14241] Re: Attachment filename containing german umlauts and Outlook 2013/2016

[noreply at bugs.horde.org]

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

Ticket URL: https://bugs.horde.org/ticket/14241
------------------------------------------------------------------------------
  Ticket             | 14241
  Updated By         | Sebastian.Bopper at uni-hohenheim.de
  Summary            | Attachment filename containing german umlauts and
                     | Outlook 2013/2016
  Queue              | Synchronization
  Version            | FRAMEWORK_5_2
  Type               | Bug
  State              | Duplicate
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Sebastian.Bopper at uni-hohenheim.de (2016-06-02 11:54) wrote:

> Hello,
>
> I have a little problem with Outlook and Horde via ActiveSync:
>
> if you send an email (via IMP or Outlook)  with an attachment  
> containing german umlauts (i.e. "hörprobe.doc") to an INTERNAL Horde  
> user, the attachment is displayed correctly in IMP, but if you open  
> the email with Outlook 2013 via ActiveSync, the attachment's name is  
> displayed as "Unbenannte Anlage 0147.doc" (I guess it's "Unnamed  
> attachment" in english, the number is incrementing with each new  
> email). However, if you send the same attachment to an external  
> email address the attachment is displayed correctly.
>
> Best regards, Christian
>

Hi Christian,

just want to report, that I can confirm this bug/problem. I did also a  
post about it last year here:
https://forums.slipstick.com/threads/93929-untitled-attachment-if-file-name-contains-eg-special-character/ ... but up to now it is not  
fixed.

The current configuration is: Outlook/16.0 (16.0.4378.1000; MSI; x86).  
The mail server is HORDE (Imp H5 (6.2.14) by using EAS Version: 14.0.  
and Outlook's EAS. Bug is still present.

For me still the challenge is to determine whether it is an client  
(outlook) or server (HORDE) issue.

Kind regards from Germany, Sebastian