Forum Widgets
Latest Discussions
How to set your display name in the New Outlook?
In Outlook Classic (or Legacy), I could easily set my display name by going to: File -> Account Settings -> Account Name and Sync Settings -> Your Name When configured this way, the emails I sent would display my name, followed by my email address in parentheses. This worked flawlessly for both my work and personal email accounts. However, when using the New Outlook, the emails I send only show my email address. My name is no longer displayed as the sender. Is there any way to make the New Outlook send emails with my name displayed as the Classic version does? Any help or workarounds would be greatly appreciated!
The Unnecessary Complexity of Microsoft 365 & Outlook Classic: A UX Admin Nightmare for BYOD
I recently needed to remove a corporate Exchange account from a personal device running Microsoft 365. What should have been a one-click action exposed a deeply flawed and convoluted architecture: Primary Account Lock: Outlook Classic fundamentally prevents the removal of a "Primary Account" from its GUI. The only functional workaround is completely destroying the Outlook profile via the Control Panel or Registry. MDM Overreach on BYOD: When adding a work account, MDM and Entra ID policies immediately override local user control. There is zero clear exit strategy or automated cleanup for the end-user when that corporate relationship ends. Monolithic Click-To-Run Architecture: Attempting to simply uninstall the obsolete Outlook Classic application is impossible through standard Windows settings. It required deploying the Office Deployment Tool (ODT) and executing a custom XML configuration script just to exclude a single application from the Microsoft 365 suite. This forced integration and lack of modularity is a highly anti-user experience. Microsoft must separate corporate security enforcement from personal device ownership and provide standard, modular uninstallation options for its desktop applications. Forcing users to use PowerShell and ODT for basic software management is an unacceptable standard for modern UX.
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.
Edited Netaddress Email Keeps Duplicating
In Outlook 2016 I have two IMAP accounts, one to exchange server that allows a read email subject line to be edited then saved without problem. The other is to a Netaddress email server. When I follow the same edit and save procedure in a Netaddress email it duplicates over and over, the only way to stop it is to close Outlook. So is this an undesirable feature of Outlook or is it a Netaddress problem or both?Intermittent connection error with an IMAP mailbox
One of our customers is having an issue with new Outlook where after we set up their email as IMAP (which we host), after a while Outlook would no longer recognize the password. When they went into Settings, it showed a message says "Sign-in is required. Click Sign in to resolve." The customer did that, and the sign in failed, so they closed new Outlook and did something else for a while we investigated. However, the user came back to the computer a little later, opened Outlook on a lark, and everything was back to normal and they could see all their email again. Does anyone have any idea of what might be causing that? The customer forwarded screenshots of the information they got when they clicked "Troubleshooting Details", but I don't know how helpful that will be for y'all.Outlook for Mac 16.113 Search not functioning in Legacy View
Title says it all. I have reindexed Spotlight, I have reverted backwards to .112 and .111 and no matter what I do, I can not get the search function to work again in Legacy view. Search works in the "new" Outlook for Mac, but not in Legacy, which I greatly prefer. Please help me, someone! I knew there were discussions about .112 search not working, and XML messages, but I haven't found this issue posted anywhere.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.
