New Outlook Office.js Html body insert fails with error 9011 HtmlSanitizationFailure
I am building an Outlook web add-in for New Outlook on Windows. Calling mailbox.item.body.setSelectedDataAsync, prependAsync, or setAsync with CoercionType.Html fails with HtmlSanitizationFailure code 9011 on an empty HTML compose body, even for minimal Learn-style bold markup. CoercionType.Text works on the same client. Is 9011 a known New Outlook issue? Where is this error documented? What is the supported way to insert formatted HTML from an add-in?
Thousands of Sent Items moved to Deleted Items, no rules, no retention
Hello everyone, I'm investigating a very unusual Exchange Online mailbox issue and would appreciate any insights from anyone who has seen something similar. Environment Exchange Online (Microsoft 365) Mailbox: User mailbox Outlook for Mac Outlook for iOS Outlook Web (OWA) Incident Summary On August 13, 2026, approximately 4,997 messages were moved from: The activity occurred over roughly a 3-hour period. Mailbox audit logs show thousands of: Operation: MoveToDeletedItems events. Hourly breakdown: 01:00 - 2,046 events 02:00 - 1,540 events 03:00 - 1,408 events Audit Findings All sampled audit events show: LogonType = 0 (Owner) UserId = affected mailbox owner Result = Succeeded I sampled 5,000 records and all of them were: LogonType = 0 No events were recorded as: LogonType = 1 (Admin) LogonType = 2 (Delegate) Source and Destination Folders Examples from mailbox audit records: Folder : \Sent Items Destination : \Deleted Items Operation : MoveToDeletedItems Message Trace Findings Extended Message Trace was performed on one of the affected emails. The trace confirmed: CopiedToSentItems=True DeleteAfterSubmit=False which indicates: The email was successfully sent. The email was copied to Sent Items. Exchange did not delete the message during transport. So the message existed in Sent Items and was later moved to Deleted Items by a mailbox operation. Rules Investigation Checked: Get-InboxRule -Mailbox <mailbox> -IncludeHidden Findings: No Inbox Rules targeting Sent Items. No hidden Inbox Rules targeting Sent Items. Only two legitimate rules that delete messages from specific Jira/Confluence senders. Delegation Investigation Mailbox permissions reviewed. Known permissions exist, but mailbox audit logs show: 5000/5000 sampled events = LogonType 0 Therefore: No evidence of delegate activity. No evidence of administrative activity. Retention / Compliance Investigation Checked: Get-Mailbox Get-RetentionPolicy Get-RetentionPolicyTag Get-RetentionCompliancePolicy Get-RetentionComplianceRule Findings: No Sent Items retention tag. No retention policy targeting Sent Items. No Purview retention/compliance policy appears to explain this behavior. Activity pattern does not resemble normal retention processing. Add-ins Investigation Mailbox add-ins: Polls Share to Teams Send to OneNote Action Items Bing Maps My Templates Unsubscribe No third-party mailbox-management or archiving add-ins found. Client Information Seen During Investigation Examples observed in mailbox audit logs: Client=OutlookService;MacOutlook/16.112 a { text-decoration: none; color: #464feb; } tr th, tr td { border: 1px solid #e6e6e6; } tr th { background-color: #f5f5f5; } What Has Been Ruled Out ✅ Admin activity ✅ Delegate activity ✅ Inbox Rules ✅ Hidden Inbox Rules ✅ Outlook add-ins ✅ MRM retention policies ✅ Sent Items retention tags ✅ Purview compliance retention policies ✅ Exchange transport deleting the messages Question Has anyone encountered a similar case where: Thousands of messages were moved from Sent Items to Deleted Items Operation = MoveToDeletedItems LogonType = 0 (Owner) No rules No retention policy No delegate activity particularly involving: Outlook for iOS Outlook for Mac Client=OutlookService Any similar experiences, findings, or recommendations would be greatly appreciated. As we need to know the root cause for this issue. Thanks
User can't see some emails after loading PST
Recently I helped a user migrate from an IMAP mail to Outlook. I downloaded the PST file from the old IMAP account and loaded the file into his new account, all in Classic Outlook as this user refuses to use the new Outlook. However, during the load of old mail he would stop receiving any new mail. To fix this I created a new profile and that did allow new mail to arrive, however, the mail from the backup didn’t show. I then loaded the backup into the new Outlook and it only loaded mail up to 2022. After this, we loaded the PST into Outlook Classic on a different device as to not disrupt workflow, but that also didn’t solve the issue. I loaded the PST file into a testing account, and it did load all the files, from 2020 to the date the file was created.
Outlook.de DKIM and DMARC records broken
Outbound mail from outlook.de carries a DKIM-Signature with d=OUTLOOK.DE; s=selector1, but the corresponding DNS TXT record at selector1._domainkey.outlook.de does not exist. This causes receiving servers to report dkim=permerror (no key for signature). To reproduce: Send a mail from any @outlook.de account Check the DKIM-Signature header — it references selector1 Run: dig TXT selector1._domainkey.outlook.de — no record returned The domain outlook.de also has no DMARC record published (dmarc=none). Some header information: Received: by 2002:a05:6a11:e41c:b0:73b:6833:703f with SMTP id em28csp1732536pxc; Tue, 21 Jul 2026 07:23:10 -0700 (PDT) [...] ARC-Authentication-Results: i=2; mx.google.com; dkim=permerror (no key for signature) header.i=@OUTLOOK.DE header.s=selector1 header.b=mWWTJtqO; arc=pass (i=1); spf=pass (google.com: domain of email address removed for privacy reasons designates 2a01:111:f403:d20f::3 as permitted sender) [...] I leave out DNS this time as the discussion was marked as spam, but you can easily check it yourself: dig TXT selector1._domainkey.outlook.de and dig TXT _dmarc.outlook.de return no entries as all. So obviously the DNS records are not published. This leads to bad email reputation - so emails are either in SPAM folders or get rejected completely. Can someone from MS look into this and fix it. This is at least the case since June 2026 - see also https://borncity.com/blog/2026/07/02/patzt-microsoft-bei-dkim-fuer-outlook-de/ (which is in German unfortunately) - but that is the exact issue.
腾龙公司游戏官网
现场负责人威性【 u a a 2 2 0 0】 🐧 【 3 9 8 1 1 1 5 1 0 1】 1、注恻流程详细了解微信: 【a a 9 9 9 5 521 1 1 】 开设腾龙公司的账户通常涉及以下几个步骤， 2、填写申请表格，您可以在腾龙公司的官方网站-点——浏览器——上下载并填写申请表格,或直接在腾龙公司的营业现场部填写。 3、提交开户所需文件:完成申请后准备所需的文件，这通常通过身份证明文件以及地址证明文件、银行账户信息等。这些文件需要提交给腾龙公司，可以选择在营业部现场提交或通过邮寄方法提交。 4、开设账户，提交必要的文件后,您需要按照腾龙公司的指示进行开户流程，这可能包括提供手机号码、验证短信、设置密码等步骤。 5、账户验证,完成所有必要的信息并同意相关协议后您的账户即可开通。 6、请注意,具体的开户流程可能因公司和地区的不同而有所不同，因此建议直接访问腾龙公司的官方网站获取最准确的信息Shared Calendars No Longer Visible
For years, I've shared Outlook calendars between my Outlook accounts and with my husband's, without any issues. However, since mid-June the shared calendars have disappeared for no apparent reason. The sharing permissions are still in place, but the calendars are no longer visible or available to add on Android, in the Outlook desktop app, or on Outlook on the web. I've spent hours Googling and tried all the usual troubleshooting steps, but nothing has worked! As a workaround, I now have to invite all @outlook.com accounts to calendar events just so everyone can see them and avoid double bookings. Has anyone come across this before and found a fix that isn't one of the standard "how-to" suggestions? Note: these are personal paid Microsoft accounts.Teams Meeting Add-in Not Appearing in Outlook
The computer was rebuilt from scratch and reinstalled with a clean operating system. After the installation, all required Microsoft applications (Outlook, Teams, etc.) were installed and the user successfully signed in. However, the Teams Meeting add-in is not appearing in Outlook as expected. Within the Outlook Calendar/Appointment window, only the Skype Meeting option is visible, while the Teams Meeting option is completely missing. Checks Performed: New Microsoft Teams is installed and functioning properly. Outlook and Teams are both signed in with the user account. Outlook COM Add-ins have been checked. Disabled Items have been checked. Teams Meeting Add-in for Microsoft Office has been verified. Outlook updates have been checked. Microsoft Teams has been reinstalled. Outlook profile has been verified. Exchange mailbox is active and functioning correctly. Despite all the above checks, the Teams Meeting option is still not displayed in the Outlook Calendar/Appointment window, and only the Skype Meeting integration is available. Expected Behavior: The Teams Meeting button should be available within the Outlook Calendar/Appointment window, allowing users to create Teams meetings and automatically generate Teams meeting invitations. Request: Please why the Teams Meeting Add-in is not being loaded into Outlook and provide assistance in restoring the Teams Meeting functionality within the Outlook Calendar/Appointment interface. Attachments: Screenshot showing the current issue (Teams Meeting button missing) Screenshot showing the expected behavior (Teams Meeting button visible)Is a COM add-in the only way to add an add-in to a Gmail/IMAP account in classic Outlook?
I have an Outlook web add-in (Office.js, MailApp) that works fine on Exchange Online mailboxes. But on a Gmail account added to classic Outlook for Windows via IMAP, the add-in never activates, as I understand it, web add-ins need an Exchange backend to activate against, which an IMAP account doesn't have. Is that correct? And if so, is a traditional COM add-in (VSTO) the only supported way to surface an add-in on these IMAP/POP mailboxes in classic Outlook, or is there a web-add-in path I'm missing?
My Outlook for Mac HTML email reply quoted body blank, only headers show
I've been using Legacy Outlook for Mac for years without issues, but since Wednesday afternoon (June 17, CET) something broke after the latest update rolled out. When I reply to any HTML email, the quoted original message is completely blank. Only the From, Date, To and Subject headers show up — the actual email body is gone. It makes it impossible to have a proper email thread because the recipient can't see the conversation history. This started right after Version 16.110 (Build 26061317) was released on June 16, 2026. The release notes only mention "Quality and performance improvements" for Outlook, so whatever changed in this build seems to have broken HTML reply quoting as an unintended side effect. My setup: MacBook Air M5, macOS (Legacy Outlook for Mac Exchange on-premises account (EWS), domain login What I'm experiencing: Replying in HTML mode → quoted body is completely blank, only headers show Switching to plain text → body comes back but with massive blank line gaps throughout (not professional to send) Outlook Web (OWA) → works perfectly fine What I've already tried: Cleared app data (Document Cache + Experimental Features) — no fix Cleared Outlook cache manually — no fix Toggled composing settings — no fix Checked settings in Preferences → Email → Composing — everything looks correct I've also tested Apple Mail as an alternative but it breaks embedded signature images (CID images show as placeholders), and it doesn't support Teams meeting integration — so going back to Legacy Outlook is really the only option for my daily work. Outlook Web App OWA is my current workaround but it's not sustainable long term. I really hope this can be looked at as a regression fix in the next update. Has anyone else experienced this since the June 16 build? Does anyone has this issue as well?Shared Outlook Calendar disappeared
An Outlook Calendar that my wife and I share has suddenly disappeared from my Outlook Calendar. It still shows on my wife's computer. We set this up a number of years ago, so I have no idea where or how to troubleshoot this. I do recall that we had to each create outlook.com email addresses so that we could access Microsoft Exchange. We are using the Classic version of Outlook. In case it's useful, here's the exact information from the Outlook About page: "Microsoft® Outlook® for Microsoft 365 MSO (Version 2605 Build 16.0.20026.20168) 64-bit." Thanks to anyone who can help me solve this problem.
