Forum Widgets
Latest Discussions
Outlook Search Folder for External Senders
I'm using the Outlook M365 desktop app on the current channel and Exchnage 2019 in Hybrid mode with Exchange Online. We route all mail inbound and outbound via Exchange Server. I'd like to create a search folder in Outlook to show only mails from external senders. The issue is the only criteria I can seem to create would rely on the From field and this seems to map to the SenderName on the MailItem object in Outlook. This is not the actual sender's mail address that would include the @domain etc but rather seems to be the senders name which is arbitrary from I can see e.g SomeSender. How to create a search folder based on the senders actual address?shockoApr 24, 2025Steel Contributor129Views0likes2CommentsHow does Purview/data lifecycle management on Mailboxes work for deleted mailboxes?
I have an inkling that it more or less keeps the Mailbox in the Recoverable Items set//folder/dimension, but I don't want to guess. We do not have a license for Purview, I just have discovered that we have policies in here setup and forgotten about (or migrated Compliance and Security, and forgotten about). I say this because I don't fully understand Purview (because I don't want to use it, and we don't have it), yet I have a 'keep forever' policy set on ALL Exchange Mailboxes, but it doesn't actually prevent me from Deleting them. Reading this and this doc, the word 'mailbox' appears 54 times. I have responsibilities and a life, but I did manage to find out when MAIL is deleted from Deleted Items, it goes to 'recoverable items' - a folder that exists in (somewhere). What I don't know is what happens if the entire Mailbox is deleted. I have archiving turned off. I notice that there is a separate 'inactive mailbox' article. I genuinely do not have the time or patience to read these massive docs, or the 100 other docs they link to, for a platform way outside my scale, that I don't intend on using. Anyone know? I need to understand how this works before I get approval on removing it.underQualifriedApr 24, 2025Brass Contributor10Views0likes1CommentAuthentication issues after upgrading to 2019/CU15
After upgrading to Exchange Server 2019 CU15, we started having many authentication issues. They appear in many forms. Executing a get powershell command on any virtual directory will fail for the remote system (I currently have 2 servers configured). It will log in the event viewer a DCOM 10028 error: DCOM was unable to communicate with the computer (other system FQDN name) using any of the configured protocols; requested by PID 570 (c:\windows\system32\inetsrv\w3wp.exe), while activating CLSID {2B72133B-3F5B-4602-8952-803546CE3344}. It is intermittent in nature. At first, I thought executing the Reset-ComputerMachinePassword would solve the issue, but it does not always work. We have one Windows 2025 DC in our infrastructure as we have seen some domain trust issues that have been a result of the 2025 DC. Microsoft recommends running this for those client systems. But those systems usually had an event logged in the DC indicating the need for resetting this password. This is not appearing for the Exchange servers. When the get command fails, other issues such as Outlook clients not authenticating occur as well. The Outlook clients continuously prompt for credentials without accepting them, even though correct values have been entered. However, when the get command succeeds, so does Outlook. Anyone experiencing this as well?SolvedsimdocApr 24, 2025Copper Contributor426Views0likes3CommentsPerformance Issues with Outlook When Delegating Large Mailboxes (Exchange Online)
Hello! We're using Exchange Online, and most users access their mail through the Outlook (classic) desktop app. A common scenario in our organization is that users need temporary access to a coworker’s mailbox when that person is out on PTO. We typically grant this via mailbox delegation (Read and Manage + Send As), and the mailbox remains a standard UserMailbox, not converted to a shared mailbox. The issue: When the delegate accesses the mailbox, Outlook often becomes sluggish or unresponsive, presumably due to syncing the delegated mailbox — these are usually large (30–40 GB). We've noticed major performance degradation during this sync process. What I’ve Tried: Unchecked "Download Shared Folders" (Account Settings > Account Settings> Change > More Settings > Advanced) Adjusted Offline Cached Exchange Mode to sync fewer months Unfortunately, these haven't resolved the issue. My Questions: Is there a way to delegate access without triggering a full sync of the mailbox data to Outlook? (Users are not open to switching to OWA as they rely heavily on Outlook for their primary mailbox.) What’s the best practice for temporarily granting access to large mailboxes in Exchange Online without impacting Outlook performance? Any insights or workarounds would be greatly appreciated! Thanks in advance! -AdamAdam_BApr 23, 2025Copper Contributor91Views0likes3CommentsIf Basic SMTP Auth will be disabled in Sept. 2025, how does one send SQL Server Database Mail?
According to this article: Exchange Online to retire Basic auth for Client Submission (SMTP AUTH) | Microsoft Community Hub, basic SMTP Auth will be disabled in Sept. 2025. I know it was already disabled previously but we were able to create an authentication policy to allow it. This sounds like it will be permanently disabled come September. In SQL Server, we have database mail configured to send mail using Basic Authentication. Windows Auth and Anonymous auth do not work. How will this work come September?BobwillyApr 23, 2025Occasional Reader6Views0likes0CommentsDMarc/DKIM Issues
I have enabled DKIM in Microsoft 365, and according to Microsoft 365 Defender page, it is enabled and valid for my Exchange domains. I have created a TXT _dmarc record: v=DMARC1; p=quarantine; pct=100; rua=mailto:email address removed for privacy reasons; ruf=email address removed for privacy reasons Yet I keep receiving problem reports like the one below. How can I fix this? <feedback xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <version>1.0</version> <report_metadata> <org_name>Enterprise Outlook</org_name> <email>email address removed for privacy reasons</email> <report_id>640f326a62f640e4815e84e6f0020d9c</report_id> <date_range> <begin>1730764800</begin> <end>1730851200</end> </date_range> </report_metadata> <policy_published> <domain>z.com</domain> <adkim>r</adkim> <aspf>r</aspf> <p>none</p> <sp>none</sp> <pct>100</pct> <fo>0</fo> </policy_published> <record> <row> <source_ip>40.107.96.92</source_ip> <count>1</count> <policy_evaluated> <disposition>none</disposition> <dkim>fail</dkim> <spf>fail</spf> </policy_evaluated> </row> <identifiers> <envelope_to>b.n</envelope_to> <envelope_from>z.com</envelope_from> <header_from>z.com</header_from> </identifiers> <auth_results> <dkim> <domain>onmicrosoft.com</domain> <selector>-onmicrosoft-com</selector> <result>fail</result> </dkim> <spf> <domain>z.com</domain> <scope>mfrom</scope> <result>none</result> </spf> </auth_results> </record> </feedback>Eric RintellApr 23, 2025Copper Contributor43Views0likes1CommentDatabaseCopyActivationDisabledAndMoveNow issue
Hey all, Some info first: Two Exchange 2019 CU14 in a DAG on Server 2022 Two mailbox databases I just installed the latest SU on the second server and when it came time to move the Active databases back I got this error: Server "exchange1" is enabled for DatabaseCopyActivationDisabledAndMoveNow. Moving databases to such servers may be ineffective because the system will automatically attempt to move again as soon as a healthy copy is detected. I thought I had already set that back to False so I checked: Get-MailboxServer Exchange1 | Format-List DatabaseCopyActivationDisabledAndMoveNow DatabaseCopyActivationDisabledAndMoveNow : False I ran the command again to set it to False just in case, but I still get the same error when trying to move the databases. The databases show as Healthy on Exchange1, and Exchange is functioning fine otherwise. I cannot see anything obvious in the event logs. Does anyone know what the issue might be? thanks Justin EDIT: Bah! Nevermind, it took over a half hour but I was just able to move the databases back, and everything appears fine.justletmelogin50Apr 23, 2025Brass Contributor169Views0likes1CommentMicrosoft Retires Exchange Server OWA Access to Online Archives
Microsoft’s April 17 announcement that OWA in Exchange Server will not support access to online archives after May 12, 2025, surprised quite a few people. However, the decision is entirely logical and is driven by falling mailbox numbers on-premises and the need to match engineering and support costs with revenue. Outlook classic continues to support access to online archives. Maybe Outlook will be the Exchange on-premises client for the future. https://office365itpros.com/2025/04/23/owa-online-archives/27Views0likes0CommentsIssue with Queue Viewer after Exchange 2019 CU15 Upgrade (Hybrid Mode Environment)
Hi everyone, I recently upgraded Exchange 2019 from CU12 SU5 to CU15 in a hybrid environment, and I'm now seeing an issue with Queue Viewer on the upgraded server. When I try to open Queue Viewer from the Exchange Toolbox, I get this error: "Failed to enable constraints. One or more rows contain values violating non-null, unique, or foreign-key constraints." Columns listed in the error: NextHopDomain, DeliveryType, Status, MessageCount, NextRetryTime, LastRetryTime, LastError, Identity, CanSuspend, CanResume, CanRemove, CanForceRetry Environment: .NET Framework version: 528049 OS: Windows 10.0.17763.6414 Exchange 2019 Hybrid (on-prem + Exchange Online) Additional Info: The issue only appears on the CU15-upgraded node Queue Viewer still works fine on a CU12 node From that CU12 node, I can connect to the CU15 node and use Queue Viewer without errors Has anyone seen this before or have any ideas for a fix? Thanks in advance!haniamoodiApr 23, 2025Copper Contributor27Views0likes0CommentsExchange Online Moves Closer to Dumping EWS
Microsoft is introducing a Dedicated Exchange Hybrid App to facilitate the transition away from EWS to use Graph API requests for rich hybrid coexistence (free/busy, Mail Tips, and user photos). The plan involves the creation of an Entra ID app to hold EWS permissions (stage 1) followed by Graph permissions (stage 2). Everything has to be complete by October 1, 2026, because that’s when EWS goes away. https://office365itpros.com/2025/04/22/dedicated-exchange-hybrid-app/28Views0likes0Comments
Resources
Tags
- exchange online2,475 Topics
- Exchange Server2,257 Topics
- office 3651,214 Topics
- hybrid845 Topics
- outlook739 Topics
- 2016732 Topics
- admin652 Topics
- 2013277 Topics
- 2010159 Topics
- 201978 Topics