Posted on 11-12-2021 05:59 AM
We're having an odd issue where users can't send attachments in the Outlook client. I'll post the specs below and the things I've tried. Did anyone experience this?
• Affected Users are on Big Sur 11.6.1 + Outlook 2019 (16.54)
• Regular email with text sends fine. But when you attach any kind of file, Outlook is hosed and we get an "Operation on the server timed out" message. The Outlook Client stops talking to the Exchange server and users don't get any email; it appears to be trying to sync the attachment by uploading it to the Exchange server. By deleting the email with the attachment, emails roll back in.
• Deleting the profile and creating a new one does not help.
• Downgraded to older Outlook didn't help (I tried version 16.48).
• Workaround is to OWA in Chrome only. If we use OWA in Safari, similar issue with attachments.
• Windows PCs don't have this issue.
• We are not in an Exchange hybrid setup of Office 365 and Exchange 2010.
• Mailboxes are set up in Cache mode
• No anti-virus
• Zipping the files doesn't matter
Currently, working with Exchange admin and reading the links below. This appears to have been an issue a year or two ago, but I'm a little stuck.
Posted on 02-03-2022 08:31 AM
Posted on 02-03-2022 11:01 AM
@noahdowd We had a ticket with Microsoft Enterprise support. Collected logs. Then a whole lot of nothing. Several weeks later, the problem magically went away. During that time, we did find that Monterey behaved better with attachments.
Is your Exchange on-prem, hybrid? Are you seeing this across different macOSs?
Posted on 02-03-2022 01:45 PM
On-prem Exchange with O365. We're transitioning though so I was able to try it with a 2019 license too. No change.
It's just one user so far for us, running Monterey. Very weird! It looks exactly as you described.
Posted on 03-03-2022 12:56 PM
@noahdowd Seeing this for our first Monterey user. She is On-Prem Exchange, not migrated to O365 yet. What did you end up doing for your user on Monterey?
Posted on 03-07-2022 11:07 AM
It looks like switching the user account settings from Kerberos to Username/Password took care of that issue. I was even able to change it back to Kerberos and it still worked...