Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

icloud mail attachments are corrupt if they contain spaces and downloaded via firefox

  • 1 reply
  • 9 have this problem
  • 4 views
  • Last reply by cor-el

more options

If you are accessing mail in icloud via firefox any attachment which contains spaces when saved will be corrupt. E.g "invoice for previous month.doc" when saved will come out as "invoice" with no file type and not the orginal size of the attachment. This problem is generic for all file types. Files that do not contain spaces or have _ in them download and save correctly.

I have tested this using the latest versions of firefox also default settings. On both windows 7 and OS X lion. The problem still exists. I have had friends with other accounts test this and all with the same result. I have spoken to apple care who isolated the problem and requested that the issue be taken to firefox directly. The problem has been ongoing for a year or so.

All other browsers have no issues with this problem.

If you have any idea on how to fix this your input would be greatly valued.

If you are accessing mail in '''icloud''' via '''firefox''' any attachment which ''contains spaces'' when saved will be corrupt. E.g "invoice for previous month.doc" when saved will come out as "invoice" with no file type and not the orginal size of the attachment. This problem is generic for all file types. Files that do not contain spaces or have _ in them download and save correctly. I have tested this using the latest versions of firefox also default settings. On both windows 7 and OS X lion. The problem still exists. I have had friends with other accounts test this and all with the same result. I have spoken to apple care who isolated the problem and requested that the issue be taken to firefox directly. The problem has been ongoing for a year or so. All other browsers have no issues with this problem. If you have any idea on how to fix this your input would be greatly valued.

All Replies (1)

more options

Sounds that the server doesn't comply to RFC 5987 and sends the wrong Content-Disposition:attachment; filename header.

See the 3.2.2. Examples section: