We have an Exchange 2010 environment and an instance of OWA running.
I have a user who is unable to open an attachment from an old E-mail; neither of us is able to open the file, because it's supposed to be a document (either .doc or .pdf) but the name of the file is just appearing as "@".
It does not appear to have any associated format, other than "File". When I attempt to open the document, none of the listed applications seem to work.
Has anyone else come across this issue previously?
I understand. No, the user was not able to open the file.
The file was originally accessible, however, the format appears to have changed in his Inbox, which is very strange. I suppose he has no alternative but to request the attachment to be sent again, but I would really like to get to the bottom of this matter (if at all possible), because it is not the first time it has happened.
No, the user was not able to open the file.
The file was originally accessible, however, the format appears to have changed in his Inbox, which is very strange
So, the user was able to open the file at some point? These two sentences seem to contradict each other. I find my users' definition of "accessible" to be pretty loose. He may have seen it was there and never opened it; only to find this week that a file called "@" with no extension isn't really accessible.
I would recommend to the user to save attachments to another location for future use (we get too reliant on email as a storage space). If he needs it on other devices you probably know all the options (One Drive, Google Drive, Dropbox, Box, etc.). Is this an issue with space allocation for the account? Was the email archived? You may have a rule in Exchange that made the attachment inaccessible.
This has happened before? Have you seen an attachment opened then not able to be opened a few months later? How's your Exchange storage space?
The user insists that they were able to view the attachment upon first receipt; I cannot validate.
If the message were presently in archive, I would be able to see that it is in an archived state; however, I would not be able to tell if he moved it into archive and then removed it.
The Exchange storage space wanes from time to time. Although, I believe he is the only user who seems to get this issue.