After kb2956128 update, email with pdf attachment stuck in exchange server
After the update was installed, emails received that had a .pdf attachment would not download from exchange server 2003 to the .pst file we have designated for the email to download to. Also, if an attempt is made to open the email at the exchange server level, the email won't open. If no attachment then the email downloads to the .pst. The later Microsoft updates do the same thing but the email will disappear from the exchange server after a period of time. Anyone else experience this? Is it a combination of Microsoft updates with Office 2010 and Exchange server 2003 and adobe reader? Or is it a McAfee issue? Any thoughts?
July 16th, 2015 11:40am

Also, if an attempt is made to open the email at the exchange server level, the email won't open.

By "at the exchange server level", do you mean the emails can't be opened from OWA?

Please close Outlook and then try sending a test email (which has a .pdf attachment) to yourself. After that, try receiving and opening the email directly from within OWA to see the result. If the email still can't be opened, it means it's an Exchange server side issue. In this case, I'd recommend you post a new question in the Exchange forum for further assistance:

https://social.technet.microsoft.com/Forums/office/en-US/home?category=exchangeserver

If the problem can't be reproduced when receiving directly using OWA, please try contacting the McAfee support and disable the integration with Outlook, and then test the issue again.

If still no luck, we can try temporarily uninstalling kb2956128 update to verify if it's the root cause.

Please let me know the result.

Regards,

Steve Fan
TechNet Community Support

Free Windows Admin Tool Kit Click here and download it now
July 16th, 2015 10:19pm

I should give some more information. We verified that this started when kb2956128 was installed back in February. We uninstalled the update and all worked normal. We have been waiting for a fix. I was just posting this to see if maybe Microsoft has created a fix for this particular issue and/or if anyone else had seen this problem.
July 20th, 2015 12:14pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics