Forum Widgets
Latest Discussions
Long delay for incoming emails for one of my gmail accounts
I recently started using the new Outlook Mail and added multiple email accounts (hot mail, yahoo, and Gmail) and found that the incoming email for one of gmail accounts are delayed for hours (the 6:24pm email yesterday hasn't shown up at 10:30am today). Any advice are welcome! Thank you.
Outlook inbox double click to open a unread not working
Hello I work in an office where we work from assigned inboxes. Everyone has it set up that you have to double click on an email to open it (so that no one opens one accidentally). I also have this set up for which is working. HOWEVER, when i click ONCE on an unread, go to do something else, and go back to it, it has opened it! Can someone please advise as people in the office will start getting annoyed with me and i'm new 🥹😭. Thank you!
No "Add account" in View Settings ... Email account
I'm following this instruction Add or manage a Yahoo! email account in Outlook - Microsoft Support to try adding my YahooMail account to Outlook but get stuck on Step 3. I login at outlook.live.com, with either Chrome or Edge. Go to View -> View settings -> Settings -> Account -> Email account. In the "Email account" pane on the right, I see my outlook email and a button labeled "Manage". I don't see "Add account" nor a plus sign. Going into "Manage", I see Subscriptions for Microsoft 365 and Copilot. How do I add another account? Any help will be appreciated!
[SEMI-CRITICAL] Outlook rules aren't working when email encoding system is different
(First, note that I am a Korean, and my report may use a different term for the system because it's tedious to figure out the original term for what I am using. I believe you know the vibe I am talking about.) I figured using different character encoding system may result in failing outlook rules working. Basically, it appears Outlook is using UTF-8 based, but sometimes emails from other organisations use different. Let me show 2 receiver cases: To: =?utf-8?B?7ZmN6ri464+Z?= <johndoe@secret.secret> To: =?ks_c_5601-1987?B?yKux5rW/?= <johndoe@secret.secret> This is what you can see from an email header, and left encoded characters are a name of a person, and obviously right bracket ones are their email. You can see it uses different encoding system. Both are encoded from "홍길동" (this is identical to a random guy name as much as how john doe is.) We can guess the name of this outlook user is obviously "홍길동" and their email address is johndoe@secret.secret When you choose a rule [When an email has my name], the rule system will only work to the first case, the UTF-8 encoded one. It appears the rule [When an email has my name] only checks if an email has "?utf-8?B?7ZmN6ri464+Z?", but doesn't check "?ks_c_5601-1987?B?yKux5rW/?". However, both cases should work because both are their name. The only solution for this is adjusting senders' email system to use UTF-8 only, but that is not possible. Thus it fails checking those conditions. I am pretty sure this is why people have been complaining outlook rules doesn't work for years. I want rules having more possible case checks... but I have no idea where I can suggest this.
Email not showing in Outlook Inbox - but is on phone and Webmail?
Hi there... I am stumped. I am receiving email son my phone and Webmail - but my Outlook Inbox is not syncing the same. What is more weird is if I use Outlook to search for a NEW email (that is on my phone) - it actually does show up? Any help on this would be appreciatedChanging email providers, Can I just change server settings
We own 2 domains, mkchambers.net and mkchambers.com. Mkchambers.net is hosted at company A mkchambers.com is hosted at company B. Our email is hosted at company A, so our email addresses are ***@mkchambers.net. The web base email program company A uses allows to use alias email addresses, so we aliased everyone’s email address to ***@mkchambers.com. When we setup everyone’s email in Outlook 2019 we used ***@mkchambers.com for their email address. We are planning to switch our email host to company B so our email addresses won’t change they will still be ***@mkchambers.com. The question I have is will we need to export everyone’s email, setup a new email account in Outlook 2019 and then import the emails, or since the email addresses will be the same can we just change the server setting in Outlook to company B’s settings.
Outlook Legacy Mac doesn't display Latin1 & Unicode in Subject from Gmail correctly
[Second version of this post with fewer Latin1 & Unicode characters) Summary: Outlook Legacy on Mac is not correctly displaying non-ASCII characters in the subject line, when sent from other mail clients, including Gmail. From Apple Mail: Original subject line: Mail to Outlook: Latin1: “®©” Unicode: ✅🚩♻︎ Body: Mail to Outlook: Latin1: “®©” Unicode: ✅🚩♻︎ Displayed by Outlook: In the message list: Mail to Outlook: Latin1: ╲®©╡ Unicode: â˛∑›ƒ˚©â˙»ï¸⁄ In the MessageSource: Subject: Mail to Outlook: Latin1: ‚Äú¬Æ¬©‚Äù Unicode: ‚úÖüö©‚ôªÔ∏é Note that all of the characters in the original subject line display correctly in the message body. Some of the Latin1 characters are displaying correctly in the subject line (in this example the Copyright symbol), but not others, and none of the Unicode symbols. The same email displays correctly in Gmail. The test email sent directly from Gmail displays the same way in Outlook. However, when the message is sent FROM Outlook, the subject and body appear correct. MessageSource: Subject: Mail FROM Outlook: Latin1: =?UTF-8?B?4oCcwq7CqeKAnQ==?= Unicode: =?UTF-8?B?4pyF8J+aqeKZu++4jg==?= Details: Using MacOS 13.7, Outlook Version 16.91 (24111020) Gmail (Google Workspace) is the email provider. The problem occurs when sending via Gmail directly, or another email client like Apple Mail. I tested sending an email from outlook.office.com and the problem does not occur! Incoming MessageSource: Subject: =?utf-8?B?T3V0bG9va1dlYiB0byBPdXRsb29rOiBMYXRpbjE6IOKAnMKuwqnigJ0gVW5p?= =?utf-8?B?Y29kZTog4pyF8J+aqeKZu++4jg==?= This problem does not occur when switching to New Outlook, and the incoming messages display correctly from all sources. This leads me to believe it's an Outlook Legacy problem, not a Gmail encoding problem (ie. Legacy is just not supporting the specific subject-line encoding being used by Gmail.)
