(Postfix) with ESMTP id E66EB160368 for Sat, 29 Aug The attachment name is retained in the original email encoding - windows-1251, Gmail determines the name of the attachment properly : Forward the same email by using Outlook 2013 through Z-Push with ZimbraBackend. Return-Path: None (: does notĬontent-Transfer-Encoding: quoted-printableĬontent-Type: application/ Thread-Index: xxDkzFUKjquY08J9GeQb4GHOg8ERMIELiijS Message-ID: boor post =?utf-8?B?0J/QvtGB0YLQvtGP0LvQutC+INCS0Y/Rh9C10YHQu9Cw0LIg0JDQu9C1?= (Postfix) with ESMTP id DDE27160368 for Sat, 29 Aug The body of emails in utf-8 encoding, and attachment name encoded in US-ASCII: Attachment in a message when forwarding to GMAIL displayed as "noname". The problem occurs only on Android (4.2.2, 5.0.1), attachments in messages forwarded using the Outlook have the correct name.ġ. The problem occurs with both Gmail and other email services. There is a problem with the encoding attachments when forwarding messages received in KOI8-R, WINDOWS-1251. I use Zimbra 8.6.0 OSE + Z-Push 2.2.2-1981 + zimbraBackend (zimbra63) with 2 Android device (4.2.2, 5.0.1), as well as Outlook 2013, Zimbra Desktop 7.2.7.My native language is russian. Thanks a lot for the development of the necessary software )
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |