An attachment with a name which contains dotted characters sent by Thunderbird has an unreadable name part and/or .dat extension when you open it in Outlook 2017/2019
Categories
(Thunderbird :: Untriaged, defect)
Tracking
(Not tracked)
People
(Reporter: ottkarner, Unassigned)
Details
Attachments
(3 files)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.75 Safari/537.36 Edg/86.0.622.38
Steps to reproduce:
The two different preconditions (independent tests) to reproduce the issue:
Machine (laptop)/platform 1:
- Microsoft Windows 10 Professional Version 1909 (OS Build 18363.900)
- Windows regional settings:
- Country or region: Estonia
- Regional format: Estonian (Estonia)
- Thunderbird 78.3.2 (32-bit) - fresh install!
- Microsoft Office Home and Business 2016 Version 2009 (Build 13231.20262 Click-to-Run)
- E-mail communication used in both Thunderbird/Outlook: POP3/SMTP over SSL/TSL ports 995/465
- E-mail addresses: two different addresses with the same domain name/service provider
Machine (desktop)/platform 2:
- Microsoft Windows 10 Professional Version 2004 (OS Build 19041.508) - with all updates!
- Windows regional settings:
- Country or region: Estonia
- Regional format: Estonian (Estonia)
- Thunderbird 78.3.2 (32-bit) - fresh install!
- Microsoft Office Home 365 Version (Build 13231.20390 Click-to-Run) - with all updates!
- E-mail communication used in both Thunderbird/Outlook: POP3/SMTP over SSL/TSL ports 995/465
- E-mail addresses: three different addresses - two with one domain name/service provider (as platform 1) and one with another domain name/service provider
Steps to reproduce the issue:
- Open and use Thunderbird to write a letter:
- Create a file with a name that contains dotted characters (I have tested only with ä and Ü!) which length is longer than 11 symbols (with/without spaces) and size is not empty
- Open Thunderbird, attach the created file into a letter and send it to some e-mail address which is accessible by Outlook
- Open and use Outlook to read a letter:
- Open the letter in Outlook 2017/2019 which was sent by Thunderbird
Actual results:
When the letter sent by Thunderbird is opened in Outlook 2017/2019:
-
Recognize that the attachment filename's second part contains unusual characters with a pattern %XX%XX%XX... where XX are numbers
-
Recognize that the attachment filename's readable part is no longer than certain amount of symbols from the start on the filename (I've got results with 16-18 correct symbols in the beginning of the filename)
-
Recognize that the attachment file's extension is sometimes correct and sometimes it has .dat extension - the pattern is not clear (I've got correct/incorrect results with .docx / .pptx files, but only incorrect .dat extensions with .asice / .cdoc files which are signed / encrypted containers created and used by Estonian ID-card software)
Some other related results which may be helpful:
- The attachments sent by Thunderbird are:
- have correct filenames and file extensions if received and looked via browser in webmail client
- have correct filenames and file extensions if received and looked in Outlook 2010 (POP3/SMTP / MSO Home and Business 2010 Version 14.0.7258.5000 (32-bit) / Microsoft Windows 10 Professional Version 1909)
-
The attachments sent from gmail.com / outlook.com via browser have correct filenames and file extensions if received and looked in Outlook 2017/2019 (platform 1 / 2)
-
My college informed that the issue remains if older Thunderbird version was tried (I haven't tested it myself)
Expected results:
When the letter send by Thunderbird is opened by Outlook 2017:
- The correct attachment filenames without unusual characters are expected
- The correct attachment file extensions are expected
Comment 2•5 years ago
|
||
My college informed that the issue remains if older Thunderbird version was tried (I haven't tested it myself)
So something changed in Outlook?
Hi Magnus,
It seems so. But now it looks like that only the Click-to-Run versions are affected.
I added a new attachment that includes a small attempt to narrow down potential sources of the defect.
However, I can still produce Outlook's faulty behavior only with Thunderbird.
Best wishes,
Ott
Comment on attachment 9183756 [details]
Thunderbird-Outlook PART II, AN INVESTIGATION.pdf
Sorry for mistake: the today (in the end of the document) should be Oct 26!
Comment 5•5 years ago
|
||
Thanks for the detailed investigation. Let's continue in the duplicate though.
Description
•