MacOS stock Mail app | Some attachments cannot be downloaded when their filename contains Greek characters

So, I've been facing this bug for a long time, at least during the last 3 major versions of MacOS. I've configured the stock Mail app for use with my gmail and regularly, when I receive emails from work which contain attachments and their filenames are written in Greek, most of the times Mail says it's unable the download them. Unfortunately, this does not happen consistently and it's mainly random, but happens quite a lot.


  • The web version of gmail displays the attachments correctly.
  • The iOS and iPadOS versions of the stock Mail app does not have this issue. They display and download all the attachments from the same emails correctly.
  • I've reported this to Apple numerous times, but it hasn't been fixed in years.
  • Rebuilding my mailbox (through Mail app function), removing and re-adding my mailboxes does not solve the issue.
  • This seems to be an encoding issue but there are no options to play with in Mail app or Gmail settings (I'm using IMAP by the way).


Since this bug seems to be very specific, allow me explain the exact situation when it shows up. I've set up Gmail to fetch email from my work email account residing in sch.gr (that's my work email provider) through POP3. Both the web mail version of sch.gr and gmail shows attachment filenames correctly. No encoding issues whatsoever. Only the macOS Mail app shows the filenames as question marks and this does not even happen to every attachment, but most of them. As a result I cannot download or [pre]view them, which is rather annoying. So, since the Gmail web version shows the attachment filenames correctly, I would assume the problem to reside with the sch.gr email provider not doing something properly (maybe a server side misconfiguration). On the other hand Gmail manages to see through the issue for its web version of their service, but Mail app doesn't when it receives the emails. Rather peculiar, correct?


Here's a workaround for the issue: Tap on each attachment, wait until the app says "Unable to download attachment", switch to a different email, wait for a few seconds (this is crucial) and then switch back to your original message and voila. The attachment filenames and the attachments themselves appear as they should. The issue is demonstrated in the following screencast: https://ibb.co/KWtNtQ1


Has anyone faced and/or addressed this issue?

MacBook Pro 15″, macOS 12.3

Posted on Apr 1, 2022 4:21 AM

Reply

Similar questions

8 replies

Apr 7, 2022 1:49 AM in response to etresoft

Upon further research, I'm referencing a sample email from a mailing list. I changed my email address to receiver@gmail.com.


Indeed the raw source data indicates that different encodings reside in the same email. There are a few instances where utf-8 is used, but iso-8859-7 (an old Greek encoding) is far more used in different parts of the email as well as in the attachment filenames.


Senders usually use Outlook on Windows, Horde or Roundcube web email clients.


Raw source data: https://filen.io/d/35c43ec6-fed3-4e9a-85ff-ff38bf2f86f2#!l5VkSl13W21Ik3mfLgmIh9XMukXppnVF

Apr 1, 2022 5:58 AM in response to SakisAg

SakisAg wrote:

So, since the Gmail web version shows the attachment filenames correctly, I would assume the problem to reside with the sch.gr email provider not doing something properly (maybe a server side misconfiguration). On the other hand Gmail manages to see through the issue for its web version of their service, but Mail app doesn't when it receives the emails. Rather peculiar, correct?

Actually not very peculiar. I’ve seen similar things before. The most likely cause is an encoding problem. Apple is usually more strict about these things. And because Apple users are more insular, and less business-focused, problems like this aren’t encountered as often and aren’t supported. Other companies with different markets, namely Google and Microsoft, are going to be accepting of these encoding problems. And since they are more accepting, there is less incentive on the originator of the corrupt data to fix the problem.


This problem exists, to one degree or another, throughout the internet and the computing industry. Different companies have different standards about when to stand their ground and refuse to accept invalid data. E-mail messages are particularly problematic. Apple, because of its market, it’s relatively small market size, it’s relatively large market power, and it’s own quirks, is more likely to reject corrupted data like this than other companies. So when you encounter an edge case like, with email attachments written in Greek, it’s not surprising that you would be able to see it fail.


If you could anonymize the e-mail and post it, I could tell you exactly what is wrong with it. But in all honesty, it’s a waste of time. If it is an Apple bug, Apple isn’t going to fix it. If it isn’t an Apple bug, Apple isn’t going to fix it. You would also have to track down who actually encoded the e-mail incorrectly. Maybe it was the sender’s e-mail client. But it could have also been any e-mail server between the sender and you. It isn’t unusual to disassemble e-mails to check them for viruses, phishing, etc., reassemble them, and send them on. There is no guarantee they will be reassembled correctly.

Apr 1, 2022 7:47 AM in response to SakisAg

SakisAg wrote:

In conclusion, this is what leads me to deem it as an Apple bug.

Perhaps Apple implemented more lenient checking on iOS? Regardless, I never discounted the possibility that it could be an Apple bug. I simply said that Apple isn't going to fix it, at least not directly. Apple may very well replace the current version of Mac Mail for the iOS version at a future date. Maybe that will fix this bug. Maybe that will introduce new bugs. But without seeing the original message, I will continue to assume that the message was simply encoded incorrectly.


Perhaps Apple Mail extracts and caches the attachments, correcting the encoding in the process. That might explain why you see it correctly when you switch to a different message. MIME e-mail is simply exceptionally difficult to compose. A significant portion of all e-mails that we all use on a daily basis is the result of some company deciding to abandon existing standards and make up a new one. It caught on and now we have HTML e-mail.

Apr 7, 2022 8:40 AM in response to SakisAg

This sample looks fine in Apple Mail. Do you experience the problem with it? I'm just opening the file as an "eml" file. I didn't try to send it to myself like a real message.


I looked at the content and it appears correct. There is no problem in using different encodings, including iso-8859-7, as long as the content is correct.


This part can be a little tricky. This is getting pretty deep into the details of MIME encoding by using a "B-encoding" in a content-disposition field. It appears to be correct and Apple Mail appears happy with it. But just because one does something correctly doesn't mean they won't be punished for it. Various spam filters and e-mail gateways could corrupt this data.

Apr 7, 2022 11:14 AM in response to etresoft

Yes. This was one of the emails that the attachment filenames appeared incorrectly. Bear in mind that switching away from the message and returning to it after a while resolves this issue.


Sending the message to yourself wouldn't reproduce this issue. You would need to use the specific mail server my company uses, which probably causes this issue. The issue I'm describing is something specific to the messages transferred by this email server. Either the email client the senders use causes this (this is not so probable as they use a variety of email clients including the webmail apps I referenced in my previous message), or the mail server itself.


This is the method I follow to reproduce the issue: I select and open an email from the "suspected for issue" list (this includes emails arriving from sch.gr mail server). See that the attachment[s] filename[s] are shown [sometimes partially] as questionmarks, click on the attachments manually, get the "Unable to download attachments" message, switch away from the message, return to it after a few seconds and voila! The issue is not there any longer. I'm sampling this message for the raw source before and after the issue is resolved and the raw source data is not altered, as expected.

Apr 1, 2022 6:22 AM in response to etresoft

What you say is logical and I comprehend it. I'm part of the IT industry myself since the 90s. Encoding problems have been here since I remember and until every last one system is configured to use a single global unicode system, we'll probably keep facing them.


I would like to stress two points:

  1. The issue I'm reporting happens only on the MacOS version of Mail app and not on iOS or iPadOS.
  2. Please notice the last paragraph of my original message. The issue is resolved just by switching messages. And this workaround has a permanent effect in macOS Mail app database. You won't get it again for that specific message. This is what I find peculiar about it.


In conclusion, this is what leads me to deem it as an Apple bug.


Thank you for your time! 🙂

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

MacOS stock Mail app | Some attachments cannot be downloaded when their filename contains Greek characters

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.