This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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 updated to the latest version of Outlook today and I'm able to once again send signed emails with the attachments being included for the recipient.
Seeing this issue as well. M1, Intel-based mac
Mail attachments are displayed even under the sent folder but don’t arrive at the recipient's mailbox
We use S/MIME. Turning it off seems to help for a while. but eventually comes back.
Microsoft Outlook for mac 16.66.(22100201) and older version
I experience exactly the same behavior.
Outlook 365 For Business on Mac OS (Macbook Pro / M1 / S-MIME certificate configured).
Attachments are silently ignored.
Yes indeed , it is a "known issue". We cannot see the history of the bug, which would be great to actually see when it was filled. The only thing we know for sure is that they started investigating 2 weeks ago.
The most problematic part on the story is that people noticed this and reported on the beta versions as it seems and they still went on and released it with that bug included.
I am here to echo the frustration and confusion. The software that I pay hundreds of dollars a year for is broken in a fundamental way. Microsoft, please escalate this issue!