Supporting Windows 8 Mail in your organization

Published Nov 26 2012 04:05 PM 193K Views

Windows 8 and Windows RT include a built-in email app named Mail (also referred to as Windows 8 Mail or the Windows 8 Mail app). The Windows 8 Mail app includes support for IMAP and Exchange ActiveSync (EAS) accounts.

This article includes some key technical details of the Windows 8 Mail app. Use the information to help you support the use of Windows 8 Mail app in your organization. Read this article start to finish, or jump to the topic that interests you. Use the reference links throughout the article for more information.

NOTE Mail, Calendar, People, and Messaging are apps that are built in to Windows 8 and Windows RT. Although this article discusses the Windows 8 Mail app, please note that much of the information in this article also applies to the Calendar, People, and Messaging apps. This is because, when connected to a server that supports Exchange ActiveSync, the Calendar, and People apps may also display data that was downloaded over the Exchange ActiveSync connection.

Protocol Support

The Windows 8 Mail app lets users connect to any service provider that supports either of the following two protocols:

  • Exchange ActiveSync

POP is not currently supported.

Exchange ActiveSync

Exchange ActiveSync can be used to sync data for email, contacts, and calendar. The Windows 8 Mail app supports EAS versions 2.5, 12.0, 12.1, and 14.0. For detailed protocol documentation, see Exchange Sever Protocol Documents on MSDN.

NOTE All Windows Communications apps (Mail, Calendar, and People) can use the data that is synchronized with Exchange ActiveSync. After a user connects to their account in the Windows 8 Mail app, their contacts and calendar data are available in the other Windows Communications Apps and vice versa.

The Mail app does not support certificate-based authentication of clients for Exchange ActiveSync.


The Windows 8 Mail app supports the following IMAP and SMTP standards:

IMAP/SMTP can be used to send and receive email only. Contacts data and calendar data is not synchronized when IMAP/SMTP is used. Microsoft Exchange does not support Public Folders via IMAP. For more details about IMAP support in Exchange, see POP3 and IMAP4 (for Exchange 2010, see Understanding POP3 and IMAP4).

Sync Configuration

The Windows 8 Mail app can be configured to synchronize data at different times as follows:

  • Push email (default)
  • Polling at fixed intervals
  • Manually

If a push email connection can’t be established, it will automatically switch to poll at fixed intervals.

Push Email

Push email requires that accounts are either Exchange ActiveSync (which all support Push) or IMAP with the IDLE extension. Not all IMAP servers support IDLE, and it is supported only for the Inbox folder.

When a push connection can’t be established, Mail will change to polling on 30 minute intervals. Push email on Exchange ActiveSync requires that HTTP connections must be maintained for up to 60 minutes, and IMAP IDLE requires TCP connections to be maintained for up to 30 minutes.

Account Setup Features

Windows 8 and Windows RT users can add email accounts to the Windows 8 Mail app using the Settings charm. The Settings charm is always available on the right side of the Windows 8 and Windows RT screen. (For more visual details about Charms & the Windows 8 user interface, see Search, share & more.)

NOTE This section provides an overview of Windows 8 Mail app account setup. For step-by-step procedures for setting up an account in the Windows 8 Mail app, see What else do I need to know? at the end of this guide.

To make it as easy as possible to add accounts, account setup only prompts the user to enter the email address and password for the account they want to set up. From that data, Mail attempts to automatically configure the account as follows:

  • The domain portion of the email address is matched against a database of well-known service providers. If it’s a match, its settings are automatically configured.
  • The domain portion of the email address is used to execute Exchange ActiveSync Autodiscover processes. For detailed information, see Autodiscover HTTP Service Protocol Specification on MSDN.
  • If still not configured, the user is prompted to provide detailed settings for their server.

Exchange ActiveSync

Screenshot: Exchange ActiveSync configuration in Windows Mail
Figure 1: Exchange ActiveSync (EAS) configuration in Windows Mail

Full details needed to connect to an Exchange server – needed only if Autodiscover failed

The information required to connect to a server via Exchange ActiveSync is:

  • Email address
  • Server address
  • Domain
  • Username
  • Password


Screenshot: IMAP/SMTP configuration in Windows Mail
Figure 2: IMAP/SMTP configuration in Windows Mail

The information required to connect to a server via IMAP/SMTP is:

  • Email address
  • Username
  • Password
  • IMAP email server
  • IMAP SSL (if your IMAP server requires SSL encryption)
  • IMAP port
  • SMTP email server
  • SMTP SSL (if your SMTP server requires SSL encryption)
  • SMTP port
  • Whether SMTP server requires authentication
  • Whether SMTP uses the same credentials as IMAP (If not, user must also provide SMTP credentials)

Security Features

Mail provides administrators with some level of security through Exchange ActiveSync policies. It doesn’t support any means of managing or securing PCs that are connected via IMAP.

Policy Support

Exchange ActiveSync devices can be managed using Exchange ActiveSync policies. Windows 8 Mail supports the following EAS policies. :

  • Password required
  • Allow simple password
  • Minimum password length (to a maximum of 8 characters)
  • Number of complex characters in password (to a maximum of 2 characters)
  • Password history
  • Password expiration
  • Device encryption required (on Windows RT and editions of Windows that support BitLocker. See What's New in BitLocker for details about BitLocker improvements in Windows 8.)
  • Maximum number of failed attempts to unlock device
  • Maximum time of inactivity before locking

Note that if AllowNonProvisionableDevices is set to false in an EAS policy and the policy contains settings are not part of this list, the device won’t be able to connect to the Exchange server.

Getting into Compliance

Most of the policies listed above can be automatically enabled by Mail, but there are certain cases where the user has to take action first. These are:

  • Server requires device encryption:
    • User has a device that supports BitLocker but BitLocker isn’t enabled. User must manually enable BitLocker.
    • User has a Windows RT device that supports device encryption but it is suspended. User must reboot.
    • User has a Windows RT device that supports device encryption, but it isn’t enabled. User must sign into Windows with a Microsoft account.
  • An admin on this PC doesn’t have a strong password: All admin accounts must have a strong password before continuing.
  • The user’s account doesn’t have a strong password: User must set a strong password before continuing.

ActiveSync Policy v/s Group Policy on domain-joined Windows 8 devices

If a Windows 8 PC is joined to an Active Directory domain and controlled by Group Policy, there may be conflicting policy settings between Group Policy and an Exchange ActiveSync policy. In the event of any conflict, the strictest rule in either policy takes precedence. The only exception is password complexity rules for domain accounts. Group policy rules for password complexity (length, expiry, history, number of complex characters) take precedence over Exchange ActiveSync policies – even if group policy rules for password complexity are less strict than Exchange ActiveSync rules, the domain account will be deemed in compliance with Exchange ActiveSync policy.

Remote Wipe

Mail supports the Exchange ActiveSync remote wipe directive, but unlike Windows Phones, the data deleted by this directive is scoped to the specified Exchange ActiveSync account. The user's personal data is not deleted. For example, if a user has an account for personal use and a account for work use, a remote wipe directive from the server would impact Windows 8 and Windows Phone 7 as follows:

DataWindows Phone 7Windows 8 Mail email Deleted Deleted contacts Deleted Deleted calendars Deleted Deleted email Deleted Not deleted contacts Deleted Not deleted calendars Deleted Not deleted
Other documents, files, pictures, etc. Deleted Not deleted

Account Roaming

To make it as easy as possible for users to have all of their accounts set up on all of their devices, Windows 8 uploads vital account information to the user’s Microsoft account. This information includes email address, server, server settings, and password. When a user signs into a new PC with their Microsoft account, their email accounts are automatically set up for them.

Passwords are not uploaded from a PC for any accounts which are controlled by any Exchange ActiveSync policies. Users will have to enter their password to begin syncing a policy-controlled account on a new PC.

Microsoft Accounts

Users are required to have a Microsoft Account, formerly known as Windows Live ID, to use the Windows Communications apps. This will usually be the Microsoft account that the user is signed into Windows with, but if they have not done so, they will be prompted to provide one before proceeding.

Microsoft accounts will automatically sync to Microsoft services using Exchange ActiveSync 14.0 when Mail starts. This will synchronize:

      • Email, if the user’s Microsoft account is also their Hotmail or account
      • Contacts from Windows Live
      • Calendar events

If the user’s Microsoft account is not a or Hotmail account (for example,, Mail will prompt the user to provide the password for their email account, which will be added automatically.

Data Consumption

By default, Mail only downloads the last two weeks of email. This is user configurable and can potentially download the user’s entire mailbox. For Exchange ActiveSync accounts, all contacts are downloaded and calendar events are downloaded only for three months behind the current date and 18 months ahead.

Additionally, messages are only partially downloaded to reduce bandwidth use as follows:

        • Message bodies are truncated to the first 100KB (20KB on metered networks). For more details see Engineering Windows 8 for mobile networks.
        • Attachments are not downloaded automatically.

Embedded images in email messages are downloaded on-demand as the user reads them, and attachments are downloaded on-demand as the user attempts to open them.

By default, Mail only downloads the user’s Inbox and Sent folders. Other folders are downloaded once the user accesses them for the first time.

Mail does not enforce any limits on how many or large of attachments users can send.


The following features are currently not supported by Mail:

  • Mailbox connections using POP:  IMAP and EAS are supported.

    (Note, this does not mean that Windows 8 does not support POP3. This post is about the Windows 8 Mail app. )

  • Servers that require self-signed certificates: Users can work around the self-signed certificate limitation by manually installing the certificate on their Windows 8 or Windows RT device. For additional information about the self-signed certificates, see Self-Signed Certificates section below.

  • Opaque-Signed and Encrypted S/MIME messages: When S/MIME messages are received in Windows 8 Mail, it displays an email item with a message body that begins with “This encrypted message can’t be displayed.”

    To view email items in the S/MIME format, users must open the message using Outlook Web App, Microsoft Outlook, or another email program that supports S/MIME messages. For more information, see Opaque-Signed and Encrypted S/MIME Message on MSDN.

Self-Signed Certificates

Users may experience connectivity errors when trying to connect to an Exchange servers that require self-signed certificates. The user may receive the following error messages.

Unable to connect. Ensure the information entered is correct.

<Email address> is unavailable

NOTE This issue may occur because the Mail app cannot connect to Exchange by using self-signed certificates.

Consider the following options to resolve this issue.

    1. Option 1: Install a certificate that is signed by a Microsoft-trusted root certification authority (CA) on the server

      This enables Exchange to work for all clients without prompting. For more information about the trust root CAs, see the following topics on TechNet:

    2. Option 2: Install a server’s self-signed certificate on a device

      This enables Exchange to work for Windows 8 devices that have the certificate installed.

Note To install a self-signed certificate for a domain’s certification authority, the administrator must provide a certificate file (.cer). The certificate can be installed to the trusted root certificate authority store for either of the following options:

  • For the current user This option does not require admin rights but must be completed for each user on the device.
  • For the local device This option requires administrator rights and needs to be done only one time for a device.

The user or the system administrator can use the .cer file to install the certificate. To do this, use one of the following methods:

  • Command-line tool

    At an elevated command prompt, run the following command:

    certutil.exe -f -addstore root <name_of_certificatefile>.cer

    NOTE The command installs the certificate for all users on the device.

  • User interface

    1. Double-click the certificate file. A certificate dialog opens.
    2. Click Install Certificate. A Certificate Import Wizard window opens.
    3. Select the option to install the certificate for only the current user or for the local device.
    4. Select Place all certificates in the following store
    5. Click Browse to open the store selection dialog. Select Trusted Root Certification Authorities.
    6. Select the store, and then click Ok. You are returned to Certificate Import Wizard dialog, and the certificate store and certificate to be installed into that store are displayed.

Troubleshooting Windows 8 Mail Client Connectivity

If Windows 8 Mail users can't successfully connect to their accounts, consider the following:

  • Verify that the user is using the latest version of the Windows 8 Mail app. A user can check for updates to the Windows 8 Mail app by doing the following: from the Start screen, go to Store > Settings > App updates > Check for updates.
  • The user should wait a few minutes and try again.
  • If the account is a cloud-based email account that requires registration (for example, a Microsoft Office 365 account), the user must register their account before they can set up their account in Windows 8 Mail. If the user is a Microsoft Office 365 user, they register their account when they sign in to Office 365 for the first time. If the user is not an Office 365 user, the user registers their account when they sign in to their account using Microsoft account or Outlook Web App.

TIP The user will see the following message if they haven't registered their account. In Windows 8 Mail, you will see the following message:
“We couldn’t find the settings for. Provide use with more info and we’ll try connecting again.”

For information about signing into Outlook Web App or the Office 365 Portal, see Sign In to Outlook Web App.

After the user signs in to your account using Outlook Web App, the user should sign out, and then try to connect using Windows 8 Mail.

What else do I need to know?


  • 11/26/2012: Updated info about AllowNonProvisionableDevices setting in EAS policies.
  • 11/27/2012: Added links to EAS policy documentation.
  • 11/27/2012: Added info about Public Folder support in IMAP and link to IMAP documentation.
  • 12/3/2012: Added link to Building the Mail app on the Building Windows 8 blog.
  • 12/21/2012: Added links to KB 2784275, 2792112 and 2464593.
  • 2/20/2013: Added note about Certificate-base authentication of clients for Exchange ActiveSync not being supported.
Not applicable

Two issues I've found.

1. The autodiscover doesn't work, at least when using SRV records. The site says the domain is configured correctly.

2. Non administrators cannot proceed when there are policies set (password required policies) the app informs you the user needs to be an administrator to continue, which is a little strange. Surely a non admin should be able to hookup their email etc. It would be better a lot easier if you could set Exchange 2010 not to apply policies to Windows8 devices.

Not applicable

Does the Windows 8 Mail Client work with client certificate-based authentication?

Windows 8 Phone and Windows Phone 7 work fine, but I have not had any  success so far with the Windows 8 Mail Client.

Not applicable

Same question as Alginald, does the Windows 8 Mail Client work with client certificate-based authentication?

I can never get it to work. Where are the logs for troubleshooting if the connection fails?

Not applicable

This is a great article, very helpfull. The only thing I'm missing is: where can we find the logfiles to further troubleshoot issues?

Not applicable

It doesn't work with our Exchange server. Going to results in a green pass. Our mobile devices work, but not Windows 8 mail.

Not applicable

Why the heck do the Communications apps REQUIRE a Microsoft account? I don't care about the syncing settings stuff, this makes absolutely no sense and makes distributing a device with these apps difficult. I don't care that Messages doesn't work because all I want in Mail and Calendar is my Exchange account!

Not applicable

The Windows 8 Mail app is no good. It is constantly having problems synching to Exchange in our company. By far the most complained about Modern UI app. It doesn't handle multiple mailboxes well, especially the notifications. It appears to lose IMAP-related e-mail like our users GMAIL mailboxes. Windows 8 mail is making all of us in IT look bad.

On the flip side, the Outlook 2013 application looks like all the color was removed and the 3d effects are gone. The integrated search is now missing and the notifications are non-interactive.

Basically the Windows 8 mail app is too basic and doesn't appear to work. The new full Outlook client looks like a major step backwards as well. We're forced to stick with Windows 7 and Outlook 2010 for now.

Not applicable

Looks complicated. Too complicated for most users to figure out and/or troubleshoot.

What I want to know is why I am forced to use a Microsoft Hotmail and/or outlook account to set up my mail in Windows 8. It forces me to use an account I don't want to use just to set up my mail. How can we get around this limitation?

Not applicable

Can someone put this article into plain English? I can't get my Surface device to connect to my Exchange 2010 service, but I can't understand this article. For example, I don't understand what an "IMAP SSL" is

Not applicable

Can the Mail App see Exchange Public folders?

Not applicable

@Plain English please: By default, IMAP listens on well-known

port 143 If your mail server has IMAP over SSL (IMAPS) enabled, it typically listens on the well-known

port 993. (Both ports TCP, but you don't need to specify that when configuring Mail). You must configure Windows 8 Mail with either IMAP or IMAP over SSL settings to access mail from your IMAP mailbox server.

This article is meant for IT pros to support Windows 8 Mail in organizations. You can find more details about IMAP4 in the IMAP RFC linked in the article. There are plenty of other great

resources for IMAP info on the web, including


Not applicable

@Don: Microsoft Exchange does not support Public Folder access over IMAP. See

Understanding POP3 and IMAP4 in Exchange2010 documentation.

Not applicable

@AM: Most organizations don't allow unmanaged devices (devices with no policies). Exchange ActiveSync policies are applied to mailbox users and thus applicable to all

EAS devices your users use. You can't exempt a specific device from EAS policies. You can use device access rules to allow, block or quarantine devices. See

Controlling Exchange ActiveSync device access using the Allow/Block/Quarantine list for details.

If you want to allow devices to connect without restrictions, you can modify the EAS policy (applicable to users - the default EAS policy if you haven't created any custom policies) to disable most settings. See

Understanding Exchange ActiveSync Mailbox Policies in Exchange 2010 documentation for details.

Not applicable


I'm still confused. I have no idea what you mean when you say "port 993". Are you on another planet?You might as well be speaking Latin. I talked with my IT folk and they say that Mail should not be using "IMAP" to connect to our Exchange. It should be using "Active Synch". It should not be prompting for a certificate either.

So, how do I fix it? please state things in plain English as I have no idea what you're talking about. All I want to do is get our Exchange mail application to work with my Windows Surface tablet I bought. Occur Exchange works with iPhones, iPads, Android Jelly Bean, Macs, and all the other devices. But it does not work with your own surface device.

Not applicable

@Plain English please: This blog is for IT pros and this post states the target audience (it's a technical post). End-users may find the technical details confusing. You should have your IT folks read this to get the info they need to support Windows 8 Mail users.

You can use Exchange ActiveSync - in which case you don't need to worry about IMAP4 or port numbers! See the articles linked in "What else do I need to know?" at the bottom of the post.

Not applicable

Can configuration of accounts be automated?

Not applicable

We are having the same problems as everyone else. We are on the verge of completely banning all Windows 8 and Windows RT devices. They are proving to be a complete pain all around. Much more difficult to manage than Windows 7.

Not applicable

Mail 8 is having problems connecting to Exchange. I get the same "unable to connect ensure the information is correct" whenever I try to get a users RT device to connect, but their iPhone works perfectly. We've never had any issues with connecting to Exchange until Windows Mail 8. That's the only application or device with problems.

Not applicable

@IMAP in Windows 8 Mail is completely FUBAR!!: The post you linked to is about Outlook 2013. Are you seeing the same issue in Mail?

Not applicable

Metro e-mail has to be the worst programmed, most basic e-mail application ever. It is embarrassing. To launch this travesty as the defacto e-mail client for Windows 8 and Windows RT devices is really just spitting in your users faces. You can't even select multiple items at the same time, imap connectivity loses mail constantly, and it forces you to use a MS_based account to force advertisements on you. If you have no account configured it just opens up with a blank white screen and you have to somehow figure out that you need to select the charms option. Finally, it doesn't connect to Exchange 2010 even with service pack 2 and the latest rollup 4 version 2 applied. A whale of a fail. Even Pine is better than the Metro e-mail client. At least Pine works.

Not applicable

It also seems that one cannot change the reply from e-mail address in Windows 8 Mail. I'm forced to reply using my Hotmail address and cannot change it to my business address. I have to copy the whole message and create a new one if I want to reply from a different e-mail address. This is not a good utility.

Not applicable

Still waiting for a reply regarding certificate-based authentication. Or will this question be "safely ignored", as nobody tested it, so nobody knows? At least let us know if it may be available in a future update of the Mail App, it's not rocket science.

Not applicable

Mail appears to simply not work with our Exchange infrastructure that uses HTTPS. My Windows Phone connects and downloads mail, the OAB, and everything just fine. My iPad does the same (running iOS 6. Mail doesn't appear to be able to connect at all. Did anyone test this before releasing it? Is there an update coming soon that will fix this problem?

Not applicable

@Alginald and others who asked about certificate-based authentication in Windows 8 Mail: The Windows Mail team is validating this. We'll update this post when we hear back.

@It does not work: It'd be safe to guess that almost all Exchange servers published to the Internt (for EAS) use SSL. My personal experience - I've tried it many times with different Exchange servers in different on-premises Orgs and in Exchange Online. I haven't had any issue at all connecting or syncing. You may need to contact Support to get help with a specific issue.

Not applicable

Cannot make windows 8 mail autodiscover work for us because it uses HTTP protocol and not HTTPS as we require. Any news on that?

Not applicable

None of the steps above work for me. I cannot get the Metro mail client to connect to Exchange. the testexchangeconnect site returns a green checkbox when I test. Outlook works too. The only tool that does not work is Metro mail.

Is Metro mail designed to work with RPC/HTTP and certificates on Exchange? It doesn't appear to work for me either.

Not applicable

@Robert Miner: As indicated in the post, Mail only works with Exchange ActiveSync and IMAP4. RPC over HTTP is an Outlook feature.

Not applicable

Whatever the case, I cannot get it to work. I've loaded the trial version of Office/Outlook 2010 on the desktop and that works with no issue. Metro mail does not work for our configuration.

Also, can you clarify why we have to set up a separate Hotmail account to get Metro mail to set up a business profile?

Not applicable

Is it true that flagging of E-Mails is not supported? I can't find the function.

Not applicable

@Robert Miner: Please contact Support for resolving specific issues.

As stated in the Microsoft Accounts section in this post:

Users are required to have a Microsoft Account, formerly known as Windows Live ID, to use the Windows Communications apps.

Not applicable

@Bharat Suneja: That's all fine and dandy, but why? Why do I need a Microsoft account to use an e-mail application to connect to my Exchange server? I don't see any explanation being offered as to why this is a requirement, nor how it helps me in any way to now have to manage two accounts in Metro to use the application. Is Microsoft tracking my e-mails or harvesting data from my device? I can see no other reason for this requirement other than Microsoft wants to snoop on my activities.

Not applicable

We have followed all of the supported security settings on our Exchange 2007 EAS policy and we still cannot get the mail app to work on Windows 8 RT or Windows 8 Pro.  It always says "This PC can't meet the security requirements...."  Can anyone help with this?  We require device encryption, passwords, and do not all non provisionable devices.

Not applicable

@Robert Miner: The post does explain what the Microsoft account is used for, but your (and others') feedback on making this optional and not a requirement has been passed on to the Windows Mail team.

Your privacy concerns are valid, but you can't be serious about the snooping question! Microsoft has one of the best records as far as privacy is concerned. See the Microsoft Privacy site ( for details, including Microsoft Privacy Principles.

Not applicable

Yes, I am very serious about the snooping thing. After realizing I can't connect my Metro mail to my Exchange server (both of which are Microsoft products), I say anything goes at this point. I have no idea why you'd require a separate log on unless you were using the data from it. Otherwise, you are inconveniencing every single person using the mail app for no reason whatsoever.

Not applicable

I have to agree with Robert. What is the reasoning behind making people sign in with a Microsoft Account? Sounds very much like Google, and we know how Google are with their information...targeted adverts based on search history etc. Windows 8 Default should be to set up the system with a local account and then the user can choose if they want to convert this to an Online account, not the other way around.

Not applicable

I can't open attachments in the Surface mail app? Any ideas

Not applicable

@JP - I can't figure out how to flag e-mails either.

Does anyone know how to get this to work? Selecting individual e-mails is a complete pain in the ass. I'm finding that all of the Metro apps are complete pains in the ass and lack even basic features.

In any case, how do I flag e-mails?

Not applicable

Is there a version of this article that makes sense to non-IT people? This is too complicated.

Not applicable

@Beyond confused!: See the first two links under

What else do I need to know? section (pasted below), which are for users.

  • Set up email in Windows 8 Mail
  • Mail: Frequently asked questions
  • Not applicable

    @DC: Thanks for the feedback!

    Not applicable

    Thanks for the info, but I'm still confused. The "set up email in Windows 8 Mail" referenced doesn't contain a single screen shot or anything. I'm lost about 8 paragraphs into it. The "Mail: Frequently asked questions" reference only contains 6 things which do not apply.

    Is there not a simple, easy to understand method with screenshots and an absolutely "idiot proof" way to set things up and make them work?

    Not applicable

    Don't work. Is a lurpin broke. Bad man not talk exchagny

    Not applicable

    I've read carefully through all of the above. I'm not a sysadmin, so it's a bit tough for me to follow when you state things like "Exchange ActiveSync 14.0". I have not a clue what that means. What I do know is that both myself and our sysadmins have been working for about 4 hours now to get my new 64GB Surface to work with our mail exchange software.

    1. We continually get a failure to sync error when connecting Windows 8 Mail. We cannot get past this point.

    2. Our sysadmins are unwilling to allow me to import a certificate. They state that this is not required on Apple or Google devices, so why is Microsoft requiring this extra step?

    3. As a third question, why am I being required to enter an e-mail address when I am connecting to my e-mail address at my company? None of the sysadmins can figure out why this is required. Again, this does not occur on Apple or Google devices, so why on a Microsoft device?

    All I want to do is get mail working on my tablet, but I'm starting to feel sick about even buying the surface at this point. Can you help?

    Thank you in advance.

    Not applicable

    "Users are required to have a Microsoft Account, formerly known as Windows Live ID, to use the Windows Communications apps. "

    Can anyone tell us why this is a requirement?

    Not applicable

    Any update from the "Windows Mail team" regarding the certificate authentication issue?

    "@Bharat Suneja [MSFT]: @Alginald and others who asked about certificate-based authentication in Windows 8 Mail: The Windows Mail team is validating this. We'll update this post when we hear back."

    I am also experiencing this issue, and have been waiting to hear the follow up. Also hoping to hear if it will be addressed in an coming update or not.

    Not applicable


    Not applicable

    Windows 8 Mail is too limiting and basic -----

    Want to sort messages in some way other then by date  - you cant

    Want to be able to see more messages in the list by switching to a 1-line display - you cant

    Want messages to go into multiple folders when they arrive - you cant

    Want something to happen automatically when a message arrives, such as a reply or forwarding - you cant

    Want the text to be bigger/smaller on the screen - you cant

    want the colors changed on the screen - you cant

    Want to ignore known bad senders - you cant

    Want to only download images from known good addresses - you cant

    Want to be able to say an email is spam - you cant

    want to be able to send a basic-text (instead of html) email - you cant

    Want to automatically update a calendar other than (such as corporate Exchange or gmail) - you cant

    Why did Microsoft release such an awful app as the default mail client on millions and millions of Windows 8 machines? Do you hate your customers?

    Not applicable

    Who specifically designed the Windows 8 Mail client and approved it for release? Who can we pin the blame on for this massive travesty? Never in my 18 years of consulting have I stumbled on such a terrible excuse for a program.

    Not applicable


    Please i need to be sure if Mail App in Windows RT or Windows 8 can support Client Certification Base Authentication (CBA) for ActiveSync.

    I spent a lot of time testing all versions of Windows RT and Windows 8 (With network capturing) and my conclusion is they doesn't work : My Client certification doesn't sent (while using Internet Explorer it is sent).


    Not applicable


    CBA does not work in Windows 8 mail. Most people can't even get it to work with any Exchange server or POP. IMAP is also very flakey.

    Version history
    Last update:
    ‎Jul 01 2019 04:10 PM
    Updated by: