Outlook web UTF-8 charset
Outlook Web sends emails in my organization using the ISO-8859-1 character set. However, Copilot claims: "Outlook Web (Outlook on the Web, OWA) does not generate your messages in ISO-8859-1. It always uses UTF-8." My Outlook Web only switches to the UTF-8 character set if the email contains Unicode characters that cannot be displayed in ISO-8859-1. How can I enforce UTF-8 globally for my organization?Exchange database dismounted due to NTFS file extent limit reached – unexpected outage
Hi everyone, We experienced a serious outage on our Exchange 2016 server recently, and I wanted to share what we found during the root cause analysis – in case it helps someone else avoid the same scenario. Summary: After digging deep, we discovered that the issue was caused by the NTFS file system hitting its internal file extent limit on the .edb file. Once this threshold was reached, the database could no longer grow, and the system dismounted the database unexpectedly. No prior warning, just service interruption. Details: The .edb was around 1.2 TB in size. This isn’t a limit on database size itself — it’s about how fragmented the file is on disk. Once NTFS couldn’t track any more extents, the database stopped working. Microsoft doesn’t publish a clear fix for this; only scattered references to similar behavior in past cases. What we did: Created a fresh, clean database. Manually moved user mailboxes into the new DB. The old database couldn't be mounted anymore, so we brought the system live without historical mail – just to maintain continuity. We're now working on extracting data from the unmounted .edb using third-party tools. Looking for thoughts: Has anyone else hit the NTFS extent wall with Exchange? How do you monitor extent growth proactively? Did switching to ReFS solve this for you long-term? Open to any input or similar experiences – appreciate it in advance. Thanks!
I can't add an O365 email to Outlook desktop client but I can access it from the web
I can't add a O365 to Outlook desktop client but I can access from the web This a weird thing, whenever I try to add in Outlook from File > Add Account I get the message "Something went wrong and Outlook couldn't set up your account". From Control Panel > Mail > Email accounts > New > Manual Setup > here I put the email and gets stuck at "Searching for... Settings" and then " An encrypted connection to your email is not available, click Next to attempt using an unencrypted connection", so I do that and get the error "We're sorry we couldn't set up your account automatically. To try setting up the account yourself click Next" which is basically the same. Everything works fine in the browser, any ideas on this?
Assist me with Shared Mailbox Alias Configuration in Outlook 365
We have a shared mailbox with different email alias configurations for various applications. Each application needs to send emails using its respective alias. Shared Mailbox Name: email address removed for privacy reasons Application 1: From email ID – email address removed for privacy reasons Application 2: From email ID – email address removed for privacy reasons Similarly, I need to define aliases for each application. Could you please assist me with setting this up in Outlook 365? Additionally, could you explain if there are any limitations related to using aliases?Outlook Not Syncing
Outlook is not syncing my emails properly. New emails are not coming, and sometimes sent emails stay in the outbox. I also get connection or server error messages. I have checked my internet connection and restarted Outlook, but the problem still continues. Please suggest how to fix this issue.
Opening .msg files from sharepoint natively in Outlook
Hi I am wondering if there is a method of opening .msg files in a similar manner to .xls and .docx, where you can open them natively. The current way sharepoint opens .msg files does not allow access to the attachments in the emails, nor can the message be forwarded unless explicitly downloaded. Classic sharepoint immediately downloads the file, so it does not mitigate the issue experienced here.
