-
📨 SMTPUTF8 in Mixed Exchange Environments (2019 ⇄ 2016): Why Your Go (gomail) App Fails — and How to Fix It
Mixed Exchange 2019↔2016 can break SMTP submissions from Go/gomail when FE 2019 advertises SMTPUTF8 and the session is proxied to BE 2016 that doesn’t support it. The fix: disable SMTPUTF8 on the 2019 connector, adjust the client, or finish migrating to 2019.
-
🔍 Granting Cross-Forest Mailbox Access: Linked Mailbox or Full Access?
Two forests, one mailbox. Should you just assign Full Access or go with a Linked Mailbox? Here’s the difference, a real-world error we hit, and why linked mailboxes often win for long-term stability.
-
🔍 Slow Room Availability Lookup in Outlook: Why It’s Not Always Exchange
Room list performance in Outlook isn’t always about the server. In this case, 60 rooms = 20 seconds load time — and Exchange was fine. The real bottleneck? Client-side visualization. Learn why and how to optimize room lists for a better user experience
-
🔍 Why Get-Volume Output Differs After Migrating from Windows Server 2012 R2 to 2016+ in Exchange DAG Environments
When migrating from Windows Server 2012 R2 to 2016+ in Exchange DAG environments, Get-Volume may return unexpected results. Unlike in 2012 R2, where the cmdlet showed only local volumes, Windows Server 2016 and later operate in a cluster-aware mode. This means volumes from other nodes can appear in the output, even if they are not…
-
🔍 Federation Certificate Renewal in Exchange: When It’s Not Just About the Certificate
Expired federation certificate in Exchange? Sometimes it’s not just a simple renewal. In this real-world case, we explored why recreating the trust was necessary, why Test-OrganizationRelationship isn’t always the whole truth, and how a simple EWS app pool restart fixed what the official docs don’t mention.
Available categories:
EWS Free Area 