outlook
2175 TopicsNew Outlook for Mac – Persistent IMAP Sync, Search & Attachment Failures (MS Support Unresolved)
I am reporting a persistent, reproducible issue with New Outlook for Mac that remains unresolved despite extensive troubleshooting, including two Microsoft Support cases. I am seeking a technical investigation and a permanent solution, not another repetition of basic troubleshooting steps. 1. System configuration Application: Microsoft Outlook for Mac (New Outlook) Current version: 16.114.4 (tel:26110224); previously 16.114.3 Operating system: macOS Tahoe 26.7.2 (up to date) Email provider: https://mailbox.org/ Account type: IMAP (not Microsoft Exchange / Microsoft 365) VPN: Not in use 2. Problems experienced The following issues occur repeatedly: Email search fails: Search results remain stuck on grey loading placeholders indefinitely. Attachments cannot be downloaded: Both old and newly received attachments fail, displaying either “Downloading attachments from server…” indefinitely or the message: “Attachments need to be downloaded again from the server. Please try again later.” Extremely slow mailbox loading and synchronization, affecting normal email use. Delays when sending emails, also documented during Microsoft Support troubleshooting. The problems are intermittent but recurring, making Outlook unreliable for everyday use. Important: The https://mailbox.org/ webmail interface works correctly, including searching emails and downloading attachments. Microsoft Support also reviewed comparisons with Apple Mail and Legacy Outlook and concluded that the issue appears specific to New Outlook for Mac. 3. Troubleshooting already performed The following measures have already been attempted, without a lasting resolution: Created two new Outlook profiles. Removed and re-added the affected IMAP account. Performed Outlook account remapping. Reset the Outlook account and rebuilt local synchronization data. Re-synchronized the mailbox and allowed sufficient time for completion. Completely uninstalled and reinstalled Outlook, followed by fresh account configuration. Verified internet connectivity and basic account functionality. Compared New Outlook with Legacy Outlook, webmail and Apple Mail, as documented in Microsoft Support’s case notes. Verified Outlook and macOS versions and checked for updates. Retested after account resets, reinstallation and reconfiguration. Result: The account reset temporarily restored email search, but attachments continued to fail. Shortly afterward, search stopped working again. Both problems persist even with newly received messages. A separate macOS user profile was additionally suggested by Microsoft Support, but I have no confirmed result from that test. 4. Microsoft Support involvement I have contacted Microsoft Support repeatedly under different case numbers During the latest interaction on November 6, 2026, Microsoft Support: Reviewed the previous case history and confirmed that extensive troubleshooting had already been performed. Acknowledged that the problem appears isolated to New Outlook for Mac. Confirmed that available troubleshooting at their support level had been exhausted. Could not offer a permanent resolution or a specific software fix. Recommended posting the issue in the Microsoft Tech Community and submitting feedback through the Microsoft Feedback Portal. Similar IMAP-related problems have also been discussed publicly since at least April 2026, without an identified resolution applicable to my case. 5. Request to Microsoft Outlook engineering / product specialists Given the extensive unsuccessful troubleshooting, I would appreciate specific answers to the following: Is this a known bug affecting IMAP accounts in New Outlook for Mac? Is there an identified issue with IMAP synchronization, attachment retrieval or the search backend? Are there diagnostic logs, error codes or targeted tests that would help engineering identify the root cause? Is there a confirmed fix, reliable workaround or planned software update addressing these symptoms? Can this issue be escalated to the Outlook for Mac engineering team, rather than restarting standard first-level troubleshooting? This issue has already consumed considerable time across multiple troubleshooting attempts and Microsoft Support interactions, while essential Outlook functionality remains unavailable. I would greatly appreciate a technically substantiated response, a concrete escalation path and, ideally, a permanent resolution. Thank you.7Views0likes0CommentsSharePoint /:f:/r/ links fail from Outlook: %2F becomes %252F
We are seeing a reproducible issue with SharePoint Online folder sharing links (/:f:/r/) sent via Outlook. A freshly generated folder link works when opened directly in Edge. When opening the link from Outlook, it can also work the first time, but subsequent attempts fail with: "Unknown render failure. This item isn't available." The failing URL shows what appears to be double URL encoding in the SharePoint id parameter: Working: id=%2Fsites%2F... Failing: id=%252Fsites%252F... We tested: - Edge and Edge InPrivate - Fresh authentication - Normal paste into Outlook - Hyperlink via Ctrl+K - Microsoft Defender Safe Links configuration A normal SharePoint site URL sent via Outlook works correctly. We also found a reliable workaround. Instead of the SharePoint sharing URL: https://<tenant>.sharepoint.com/:f:/r/sites/.../Forms/AllItems.aspx?id=...&share=... we use the direct library URL: https://<tenant>.sharepoint.com/sites/.../Forms/AllItems.aspx?id=...&p=true The direct AllItems.aspx URL works both directly and when sent through Outlook. Has anyone seen this behavior recently? In particular, why would a folder sharing link work on the first click but subsequently result in %2F becoming %252F? We have already opened a Microsoft support case. Note: This post was written with the assistance of Microsoft Copilot based on my own troubleshooting results and tests.29Views0likes0CommentsMS Account Blocked due to OAuth Emails
Hi! I am writing in this community forum in the event my account gets blocked again due to false positive flagging and to ensure it never happens again. Lately I've been noticing that my MS account has been constantly getting flagged for suspicious activity. Based on the patterns, it seems to be flagged when my TrueNAS server sends OAuth email alert to my own email. Specifcally, my email was blocked after 5 emails were sent in a single day, or it could be from 3 emails being sent in a single minute. This issue only started occuring recently and has never happened before during my time using TrueNAS OAuth emails, so I am not sure what may have changed to cause this. For the time being, I have disabled Outlook OAuth email alerts from TrueNAS for the time being until this bug or whatever the root cause for this has been determined. More importantly I want to discuss potential flaws during the account recovery process that may require the attention of Microsoft employee. During the attempt to recover my account and prove that I am not a bot, I had to click and hold a button. This button is not visible if MSEdge's tracking prevention is set to strict. I refreshed the page multiple times before figuring out I had to add https://account.live.com:443 as an exception. Due to the page refreshing multiple times, the account recovery itself ended up getting blocked. Possibily due to the servers mistakening this as a brute force attempt. This made the recovery process more difficult. Whenever my account is flagged, I get an email from email address removed for privacy reasons to unlock my verify my account. However, many sources indicate that this email is fraudulent and is a form of an AiTM phishing attack (sources: https://learn.microsoft.com/en-us/answers/questions/4583915/i-received-a-email-form-the-email-member-services, https://learn.microsoft.com/en-us/answers/questions/4670819/is-member-services-@-outlook-safe ) This is of course quite ironic since instead of this suspicious email address being flagged for phishing, my own legitimate account gets flagged which triggers some sort of bot reply from the suspicious email that would actually compromise my account. The email also correctly identifies my name, which I have censored. Also, if you copy the link on "verify your account", you will see https://go.microsoft.com/fwlink/?linkid=xxxxxxx. With a phishing mail like this, users who are also affected by false positive flagging for suspicious activity for using OAuth emails are at high risk for falling victim to this scam. So going back to the purpose of this post. Is there any possible way to continue using TrueNAS Outlook OAuth notifications without getting my account falsely flagged as suspicious?59Views0likes1CommentHow do you make a Shared Mailbox the default Send From account? (New Outlook)
I'm using Outlook for Windows version 1.2025.109.100 (on behalf of another user). I'm reading some suggestions online that say you need to add the account to Outlook first before making it the default Send From. I'm also looking at the Help section in Outlook that directs you to change this in the Compose and Reply settings. However, it's not possible to sign into a mailbox that isn't a user. I thought you used to be able to 'sign into' a shared mailbox using your own account but that is not the case now (perhaps it never was?). What it seems like is that we instead need to convert "Accounting" to a User account, give it a license, then sign into it in Outlook. That's not a Shared Mailbox - that's a user mailbox. I don't want to create a point of weakness for a potential cyber-attack (which we've had several). I can't really set up MFA for this account that no one can maintain. And I really don't want to have to spend money on a license to do something just because one piece of software is incompatible. Having to repeatedly instruct people and then repeatedly remind them to change their FROM account is just bonkers. On Outlook for Mac, as long as you're in the Shared Mailbox, the default FROM is that mailbox. (but, don't get me started on how much better the Mac version of Outlook is than the Windows version - see: All Accounts)2.2KViews0likes4CommentsClassic Outlook "EMAIL FORWARDING IS ON" bar: how to keep forwarding and remove the bar
Since around August 2026, classic Outlook (Microsoft 365) has shown a brown bar across the message list: "EMAIL FORWARDING IS ON — You are forwarding your email to …" with a Manage Rules button. There's no setting or registry key to dismiss it. The usual advice is to turn the forwarding off, which doesn't help if the forwarding is deliberate. This behavior disappeared for a while but has recently returned. I have several Inbox rules that forward mail from specific senders to a family member. They have to run server-side, because some must work while my PC is off, and I need to keep my own copy. Here's what I tried: - Change the rules to "on this computer only": bar stays - Change the rules from Forward to Redirect: bar stays - Disable the forwarding rules: bar goes, but so does the forwarding - Replace the Inbox rules with an Exchange mail flow (transport) rule: !!! bar goes, forwarding still works !!! The bar appears for any Inbox rule that forwards or redirects mail. A mail flow rule runs in Exchange Online before the message reaches my mailbox, and the bar trigger apparently doesn't look at it. Requirement: you need Exchange admin rights on your Microsoft 365 tenant. That's typically the case for small-business or custom-domain subscriptions where you're the admin. Home and Outlook.com accounts don't have mail flow rules. Steps (Exchange Online PowerShell) 1. Connect: Connect-ExchangeOnline -UserPrincipalName <your-address> 2. List your forwarding rules and their conditions: Get-InboxRule | ? {$_.ForwardTo -or $_.RedirectTo -or $_.ForwardAsAttachmentTo} | fl Name,Enabled,From,FromAddressContainsWords,SubjectContainsWords,RedirectTo,ForwardTo 3. Create one mail flow rule that covers them. Here the conditions are by sender, using regex patterns, and all patterns in the list are OR'd: New-TransportRule -Name 'Copy to Family' ` -SentTo '<your-address>' -FromAddressMatchesPatterns '@sender1\.com$','^alerts@sender2\.com$' ` -BlindCopyTo '<recipient-address>' -SentTo limits the rule to mail addressed to you. -BlindCopyTo delivers a copy that shows the original sender, like a redirect, and you keep the original. The Exchange admin center also has a GUI for this, under Mail flow → Rules. 4. Check the rule order: Get-TransportRule | ft Name,Priority,State,StopRuleProcessing If an existing rule above yours has StopRuleProcessing = True, yours will never run. A common example is a "bypass spam filtering" rule with no conditions. New rules are added at the bottom, so move yours up: Set-TransportRule 'Copy to Family' -Priority 0 5. Wait up to 30 minutes. A new or changed mail flow rule doesn't take effect right away. Then test by adding a temporary sender pattern, such as a personal address you can send from, and check the trace: Get-MessageTraceV2 -RecipientAddress '<recipient-address>' -StartDate (Get-Date).AddHours(-1) -EndDate (Get-Date) | ft Received,SenderAddress,Subject,Status -EndDate is required whenever you use -StartDate. Times are shown in UTC. Remove the test pattern afterwards with Set-TransportRule … -FromAddressMatchesPatterns …. 6. In classic Outlook, go to File → Manage Rules & Alerts, untick the old forwarding/redirect rules, click Apply, and restart Outlook. After the above, the bar was gone, the forwarding kept working, and my other rules, including "run a script" rules, were not affected. Tips - Before you change anything, back up your rules: Manage Rules & Alerts → Options → Export Rules. - Edit the Inbox rules in classic Outlook rather than Outlook on the web or PowerShell. Editing them elsewhere can remove client-only rules. - From now on, add or remove senders on the mail flow rule. Any new forwarding or redirect Inbox rule brings the bar back.115Views0likes0CommentsOutlook for Mac Beta 16.116 — Repeated Calendar Widget Crashes
Since October 26, Outlook for Mac Beta 16.116 (build 16.116.26102843) has repeatedly generated CalendarWidgetExtension crash reports on macOS 27.2. The crashes occur even though I don’t use Outlook Calendar or its widgets. Outlook email continues working normally. Investigation of the crash reports indicates that the extension cannot locate mbuinstrument.framework, even though the framework is present in the Outlook application bundle. Examination of the extension executable suggests an incorrect framework search path. The embedded path references a directory outside the widget’s framework location. Disabling the extension through PlugInKit did not prevent additional crashes. This appears to be a framework packaging or runtime search-path issue in the current Outlook Beta build. Are other Outlook for Mac Beta users experiencing this? I can provide detailed crash reports and diagnostic findings.124Views0likes2CommentsUnable to receive emails/sync issue
Hi all I'm having problems for the last few days where Ive had no emails at all and trying to sync them doesn't work at all. I can sign in to my Outlook.com account normally and I can view existing emails and folders. I can send emails successfully but I am not receiving any incoming email. The issue occurs on Outlook.com in a web browser, the Outlook app, and other devices/platforms. Mailbox storage is not the issue (approximately 0.1 GB used out of 100 GB available). Forwarding is disabled. Inbox rules have been disabled and checked. New messages do not appear in Inbox, Junk Email, Deleted Items, or any other folder. Test messages sent from multiple external accounts are accepted by the sending systems but never appear in my mailbox. Using the Sync function shows "Syncing" briefly but no new mail is downloaded or displayed. I've used the live chat and spoken to 7 different agents that cant help and trying to get a ticket for tech support isnt working I had 2 differentagents try to get a ticket with Quick Assist sessions and they couldn'tget it to work either it just sends me to to live chat over and over. Like most people my lift is intertwined to email so this would be a massive help to get it fixed. Thanks.84Views0likes1CommentIMAP Migration from Google Workspace to Microsoft 365
Hello Team, Greetings!! We have recently been experiencing significant delays during IMAP migrations from Google Workspace to Microsoft 365 and would like to understand if there are any known issues or recent changes affecting IMAP migration performance. We are aware that Microsoft provides the native Google Workspace migration method, which would generally be preferable. However, in our migration scenarios, we have split routing/coexistence configured, with the domain configured as Internal Relay in Exchange Online. Because of this setup, we are currently unable to select/configure the required target delivery domain as expected during the native Google Workspace migration process. Could you please confirm: Whether there are any known issues, throttling, or performance degradation with IMAP migrations from Google Workspace to Microsoft 365 recently? Whether the Internal Relay/split-routing configuration can affect the native Google Workspace migration process or the availability of the target delivery domain option? Is there any recommended configuration or workaround that would allow us to use the native Google Workspace migration while maintaining split routing? Any guidance or recommended approach would be highly appreciated.262Views0likes1Comment