Using older versions of Outlook for Mac for personal email and calendar
I have MacOS 13.3 and outlook 16.76.1
This issue have been happening for the past 2/3 weeks and it continues in this updated version of Outlook.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I have an issue whereby Outlook for Mac is losing attachments when sending emails (typically, but not exclusively, PDF files).
If a file(s) is/are dragged and dropped into an email it is shown as attached and appears to send as normal. There are no error messages or bouncebacks, and the first we know that the email has lost the attachment is when we are advised by the recipient. Then when checking the sent folder, the email is there but again without the attachments.
Doesn't do this every-time though... sometimes the email goes with the attachments as it normally should.
I'm using version 16.62 (22052500)
Has anybody else had this issue and is there a fix? Or is it a software glitch?
Using older versions of Outlook for Mac for personal email and calendar
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
I have MacOS 13.3 and outlook 16.76.1
This issue have been happening for the past 2/3 weeks and it continues in this updated version of Outlook.
Hi Nils, not for me, we ran the update today. and V16.76.1 for outlook was available from August 22, 2023.
Update list is here: Update history for Office for Mac - Office release notes | Microsoft Learn
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
Yes, thankfully the new version has fixed the problem for us. I will update if it happens again
There is a new version 16.76.1, which according to the version description has fixed this problem. Has anyone already had experience and can give feedback?