Microsoft Exchange Clients Mac
Posted on by admin
-->
-->
Jan 25, 2019 Outlook for Mac works with Microsoft Exchange, Office 365, Outlook.com (including Hotmail and MSN), Gmail, Yahoo Mail, and iCloud Learn more about Office 365 Office 365 is a cloud-based subscription service that brings together premium versions of Word, Excel, PowerPoint, Outlook and OneDrive, with the best tools for the way people work today. Mac and iOS users: How to leave Outlook behind forever Apple offers better mobile clients than Microsoft does, as well as a superior desktop experience woodleywonderworks (CC BY 2.0).
The Exchange Server supportability matrix provides a central source for Exchange administrators to easily locate information about the level of support available for any configuration or required component for supported versions of Microsoft Exchange Server.
Access Exchange Online from your Mac. In the past, Mac users have faced a difficult decision. Use a Mac and struggle with compatibility with the corporate e-mail system or use a PC and use Outlook for full integration. Exchange Online supports the popular Outlook for Mac 2011, which provides similar integration to Outlook for the PC. Jan 26, 2015 You can help protect yourself from scammers by verifying that the contact is a Microsoft. Outlook for MAC 2011 Kerberos with Exchange 2013. The MAC Clients can.
Release model
The following table identifies the release model for each supported version of Exchange.
In Exchange Server 2010 and earlier, each update rollup package (RU) is cumulative. An RU for Exchange Server 2010 includes all fixes for Exchange Server from all previous update rollup packages, so you only need to install the latest RU to apply all of the fixes that were released up to that point. However, individual updates or hotfixes for Exchange 2010 or earlier do not contain all previous fixes for Exchange Server. The updated files that are included in an individual update or hotfix include all updates that were applied only to those specific files by all previous updates, but any other files on Exchange Server will not be updated. For more information, see Exchange 2010 Servicing.
In Exchange Server 2013 or later, we changed the way we deliver hotfixes and service packs by using a scheduled delivery model. In this model, cumulative updates (CUs) are released quarterly (every three months). Each CU is a full installation of Exchange that includes updates and changes from all previous CUs, so you don't need to install any previous CUs or Exchange Server RTM first. For more information, see Updates for Exchange Server.
| Servicing release model | Exchange 2019 | Exchange 2016 | Exchange 2013 | Exchange 2010 |
|---|---|---|---|---|
| Cumulative updates (CUs) | Yes | Yes | Yes | No |
| Update rollups (RUs) | No | No | No | Yes |
| Security hotfixes delivered separately | Yes | Yes | Yes | No |
Note
At this time, no additional CUs are planned for Exchange Server 2013 and no additional RUs are planned for Exchange Server 2010.
Support lifecycle
For more information about the support lifecycle for specific versions of Exchange, Windows Server, or Windows client operating systems, see the Microsoft Support Lifecycle page. For more information about the Microsoft Support Lifecycle, see the Microsoft Support Lifecycle Policy FAQ.
Exchange Server 2007 End-of life
Exchange 2007 reached end of support on April 11, 2017, per the Microsoft Lifecycle Policy. There will be no new security updates, non-security updates, free or paid assisted support options, or online technical content updates. Furthermore, as adoption of Office 365 accelerates and cloud usage increases, custom support options for Office products will not be available. This includes Exchange Server, as well as Microsoft Office, SharePoint Server, Office Communications Server, Lync Server, Skype for Business Server, Project Server, and Visio. At this time, we encourage customers to complete their migration and upgrade plans. We recommend that customers leverage deployment benefits provided by Microsoft and Microsoft Certified Partners including Microsoft FastTrack for cloud migrations, and Software Assurance Planning Services for on-premises upgrades.
Supported operating system platforms
The following tables identify the operating system platforms on which each version of Exchange can run.
Important
Releases of Windows Server and Windows client that aren't listed in the tables below are not supported for use with any version or release of Exchange.
| Server operating system | Exchange 2019 | Exchange 2016 CU3 and later | Exchange 2016 CU2 and earlier | Exchange 2013 SP1 and later | Exchange 2010 SP3 |
|---|---|---|---|---|---|
| Windows Server 2019 | Supported | Not supported | Not supported | Not supported | Not supported |
| Windows Server 2016 | Not supported | Supported | Not supported | Not supported | Not supported |
| Windows Server 2012 R2 | Not supported | Supported | Supported | Supported | Supported |
| Windows Server 2012 | Not supported | Supported | Supported | Supported | Supported |
| Windows Server 2008 R2 SP1 | Not supported | Not supported | Not supported | Supported | Supported |
| Windows Server 2008 SP2 | Not supported | Not supported | Not supported | Not supported | Supported |
Note
Client operating systems only support the Exchange management tools.
| Client operating system | Exchange 2019 | Exchange 2016 CU3 and later | Exchange 2013 SP1 and later | Exchange 2010 SP3 |
|---|---|---|---|---|
| Windows 10 | Supported | Supported | Not supported | Not supported |
| Windows 8.1 | Not supported | Supported | Supported | Not supported |
| Windows 8 | Not supported | Not supported | Supported | Supported |
Supported Active Directory environments
The following table identifies the Active Directory environments that Exchange can communicate with. An Active Directory server refers to both writable global catalog servers and to writable domain controllers. Read-only global catalog servers and read-only domain controllers are not supported.
| Operating system environment | Exchange 2019 | Exchange 2016 CU12 and later | Exchange 2016 CU7 and later | Exchange 2016 CU3 to CU6 | Exchange 2016 CU2 and earlier | Exchange 2013 SP1 and later | Exchange 2010 SP3 RU22 or later | Exchange 2010 SP3 RU5 - RU21 |
|---|---|---|---|---|---|---|---|---|
| Windows Server 2019 Active Directory servers | Supported | Supported | Not supported | Not supported | Not supported | Not supported | Not supported | Not supported |
| Windows Server 2016 Active Directory servers | Supported | Supported | Supported | Supported | Supported | Supported | Supported | Not supported |
| Windows Server 2012 R2 Active Directory servers | Supported | Supported | Supported | Supported | Supported | Supported | Supported | Supported |
| Windows Server 2012 Active Directory servers | Not supported | Supported | Supported | Supported | Supported | Supported | Supported | Supported |
| Windows Server 2008 R2 SP1 Active Directory servers | Not supported | Supported | Supported | Supported | Supported | Supported | Supported | Supported |
| Windows Server 2008 SP2 Active Directory servers | Not supported | Not supported | Supported | Supported | Supported | Supported | Supported | |
| Windows Server 2003 SP2 Active Directory servers | Not supported | Not supported | Not supported | Not supported | Supported | Supported | Supported | Supported |
| AD forest functional level | Exchange 2019 | Exchange 2016 CU7 and later | Exchange 2016 CU3 to CU6 | Exchange 2016 CU2 and earlier | Exchange 2013 SP1 and later | Exchange 2010 SP3 RU22 or later | Exchange 2010 SP3 RU5 - RU21 |
|---|---|---|---|---|---|---|---|
| Windows Server 2016 | Supported | Supported | Supported | Supported | Supported | Supported | Not supported |
| Windows Server 2012 R2 | Supported | Supported | Supported | Supported | Supported | Supported | Supported |
| Windows Server 2012 | Not supported | Supported | Supported | Supported | Supported | Supported | Supported |
| Windows Server 2008 R2 | Not supported | Supported | Supported | Supported | Supported | Supported | Supported |
| Windows Server 2008 | Not supported | Not supported | Supported | Supported | Supported | Supported | Supported |
| Windows Server 2003 | Not supported | Not supported | Not supported | Supported | Supported | Supported | Supported |
Web browsers supported for use with the premium version of Outlook Web App or Outlook on the web
The following table identifies the web browsers supported for use together with the premium version of Outlook Web App or Outlook on the web.
| Browser | Exchange 2019 | Exchange 2016 | Exchange 2013 SP1 and later | Exchange 2010 SP3 |
|---|---|---|---|---|
| Microsoft Edge | Supported | Supported | Not supported | Not supported |
| Internet Explorer 11 | Supported | Supported | Supported | Supported |
| Internet Explorer 10 | Not supported | Not supported | Supported | Supported |
| Internet Explorer 9 | Not supported | Not supported | Supported | Supported |
| Internet Explorer 8 | Not supported | Not supported | Supported | Supported |
| Internet Explorer 7 | Not supported | Not supported | Not supported | Supported |
| Firefox | Current release of Firefox* | Current release of Firefox* | Not supported | Not supported |
| Firefox 3.0.1 or later | Not supported | Not supported | Not supported | Supported |
| Firefox 12 or later | Not supported | Not supported | Supported | Supported |
| Safari | Current release of Safari | Current release of Safari | Not supported | Not supported |
| Safari 3.1 or later | Not supported | Not supported | Not supported | Supported |
| Safari 5.0 or later | Not supported | Not supported | Supported | Supported |
| Chrome | Current release of Chrome* | Current release of Chrome* | Not supported | Not supported |
| Chrome 3.0.195 or later | Not supported | Not supported | Not supported | Supported |
| Chrome 18 or later | Not supported | Not supported | Supported | Supported |
* Current release of Firefox or Chrome refers to the latest version or the immediately previous version.
Web browsers supported for use with the basic version of Outlook Web App or Outlook on the web
The following table identifies the web browsers supported for use together with the light (basic) version of Outlook Web App or Outlook on the web.
Note
Outlook Web App Basic (Outlook Web App Light) is supported for use in mobile browsers. However, if rendering or authentication issues occur in a mobile browser, determine whether the issue can be reproduced by using Outlook Web App Light in the full client of a supported browser. For example, test the use of Outlook Web App Light in Safari, Chrome, or Internet Explorer. If the issue can't be reproduced in the full client, we recommend that you contact the mobile device vendor for help. In these cases, we collaborate with the vendor as appropriate.
| Browser | Exchange 2019 | Exchange 2016 | Exchange 2013 | Exchange 2010 SP3 |
|---|---|---|---|---|
| Microsoft Edge | Supported | Supported | Not supported | Not supported |
| Internet Explorer 11 | Supported | Supported | Supported | Supported |
| Internet Explorer 10 | Not supported | Not supported | Supported | Supported |
| Internet Explorer 9 | Not supported | Not supported | Supported | Supported |
| Internet Explorer 8 | Not supported | Not supported | Supported | Supported |
| Internet Explorer 7 | Not supported | Not supported | Supported | Supported |
| Safari | Current release of Safari | Current release of Safari | Supported | Supported |
| Firefox | Not supported | Current release of Firefox* | Supported | Supported |
| Chrome | Not supported | Current release of Chrome* | Not supported | Not supported |
| Opera | Not supported | Not supported | Supported | Supported |
* Current release of Firefox or Chrome refers to the latest version or the immediately previous version.
Web browsers supported for use of S/MIME with Outlook Web App or Outlook on the web
The following table identifies the web browsers supported for the use of S/MIME together with Outlook Web App or Outlook on the web.
| Browser | Exchange 2019 | Exchange 2016 | Exchange 2013 SP1 and later | Exchange 2010 SP3 |
|---|---|---|---|---|
| Microsoft Edge | Supported | Not supported | Not supported | Not supported |
| Internet Explorer 11 | Supported | Supported | Supported | Supported |
| Internet Explorer 10 | Not supported | Not supported | Supported | Supported |
| Internet Explorer 9 | Not supported | Not supported | Supported | Supported |
| Internet Explorer 8 | Not supported | Not supported | Not supported | Supported |
| Internet Explorer 7 | Not supported | Not supported | Not supported | Supported |
Clients
The following tables identify the mail clients that are supported for use together with each version of Exchange.
| Client | Exchange 2019 | Exchange 2016 | Exchange 2013 SP1 and later | Exchange 2010 SP3 |
|---|---|---|---|---|
| Office 365 ProPlus | Supported | Supported | Supported | Not supported |
| Outlook 2019 | Supported | Supported | Supported | Not supported |
| Outlook 2016 | Supported1 | Supported1 | Supported | Supported |
| Outlook 2013 | Supported1 | Supported1 | Supported | Supported |
| Outlook 2010 | Not supported | Supported1 | Supported2 | Supported |
| Outlook 2007 | Not supported | Not supported | Supported3 | Supported |
| Outlook for Mac for Office 365 | Not supported | Supported1 | Supported | Supported |
| Entourage 2008 (EWS) | Not supported | Supported4 | Supported4 | Supported4 |
1 Requires the latest Office service pack and the latest public update.
2 Requires Outlook 2010 Service Pack 1 and the latest public update.
3 Requires Outlook 2007 Service Pack 3 and the latest public update.
4 EWS only. There is no DAV support for Exchange 2010.
Microsoft .NET Framework
The following tables identify the versions of the Microsoft .NET Framework that can be used with the specified versions of Exchange.
Important
Versions of the .NET Framework that aren't listed in the tables below are not supported on any version of Exchange. This includes minor and patch-level releases of the .NET Framework.
If you are upgrading Exchange Server from an unsupported CU to the current CU and no intermediate CUs are available, you should first upgrade to the latest version of .NET that's supported by your version of Exchange Server and then immediately upgrade to the current CU. This method doesn't replace the need to keep your Exchange servers up to date and on the latest supported CU. Microsoft makes no claim that an upgrade failure will not occur using this method, which may result in the need to contact Microsoft Support Services.
Exchange 2019
| .NET Framework version | CU5, CU4 | CU3, CU2 | CU1, RTM |
|---|---|---|---|
| 4.8 | Supported | Supported | Not supported |
| 4.7.2 | Not supported | Supported | Supported |
Exchange 2016
Microsoft Exchange App Mac
| .NET Framework version | CU16, CU15 | CU14, CU13 | CU12, CU11 | CU10 | CU9, CU8 | CU7, CU6, CU5 | CU4, CU3 | CU2 | CU1, RTM |
|---|---|---|---|---|---|---|---|---|---|
| 4.8 | Supported | Supported | Not supported | Not supported | Not supported | Not supported | Not supported | Not supported | Not supported |
| 4.7.2 | Not supported | Supported | Supported | Not supported | Not supported | Not supported | Not supported | Not supported | Not supported |
| 4.7.1 | Not supported | Not supported | Supported | Supported | Supported | Not supported | Not supported | Not supported | Not supported |
| 4.6.2 | Not supported | Not supported | Not supported | Not supported | Supported | Supported | Supported | Not supported | Not supported |
| 4.6.1* | Not supported | Not supported | Not supported | Not supported | Not supported | Not supported | Supported | Supported | Not supported |
| 4.5.2 | Not supported | Not supported | Not supported | Not supported | Not supported | Not supported | Supported | Supported | Supported |
* .NET Framework 4.6.1 also requires a hotfix, and a different hotfix is required for different versions of Windows. For more information, see Released: June 2016 Quarterly Exchange Updates.
Exchange 2013
| .NET Framework version | CU23 | CU21, CU22 | CU19, CU20 | CU16, CU17, CU18 | CU15 | CU13, CU14 | CU12 to SP1 | CU3 to RTM |
|---|---|---|---|---|---|---|---|---|
| 4.8 | Supported | Not supported | Not supported | Not supported | Not supported | Not supported | Not supported | Not supported |
| 4.7.2 | Supported | Supported | Not supported | Not supported | Not supported | Not supported | Not supported | Not supported |
| 4.7.1 | Not supported | Supported | Supported | Not supported | Not supported | Not supported | Not supported | Not supported |
| 4.6.2 | Not supported | Not supported | Supported | Supported | Supported | Not supported | Not supported | Not supported |
| 4.6.1* | Not supported | Not supported | Not supported | Not supported | Supported | Supported | Not supported | Not supported |
| 4.5.2 | Not supported | Not supported | Not supported | Not supported | Supported | Supported | Supported | Not supported |
| 4.5.1 | Not supported | Not supported | Not supported | Not supported | Supported | Supported | Supported | Not supported |
| 4.5 | Not supported | Not supported | Not supported | Not supported | Not supported | Supported | Supported | Supported |
* .NET Framework 4.6.1 also requires a hotfix, and a different hotfix is required for different versions of Windows. For more information, see Released: June 2016 Quarterly Exchange Updates.
Exchange 2010 SP3
| .NET Framework version | Exchange 2010 SP3 |
|---|---|
| .NET Framework 4.5 | Supported1,2 |
| .NET Framework 4.0 | Supported1,2 |
| .NET Framework 3.5 SP1 | Supported |
| .NET Framework 3.5 | Supported1 |
1 On Windows Server 2012, you need to install the .NET Framework 3.5 before you can use Exchange 2010 SP3.
2 Exchange 2010 uses only the .NET Framework 3.5 and the .NET Framework 3.5 SP1 libraries. It doesn't use the .NET Framework 4.5 libraries if they're installed on the server. We support the installation of any version of the .NET Framework 4.5 (for example, .NET Framework 4.5.1, .NET Framework 4.5.2, etc.) as long as the .NET Framework 3.5 or the .NET Framework 3.5 SP1 is also installed on the server.
Windows PowerShell
Exchange 2013 or later requires the version of Windows PowerShell that's included in Windows (unless otherwise specified by an Exchange Setup-enforced prerequisite rule).
Exchange 2010 requires Windows PowerShell 2.0 on all supported versions of Windows.
Microsoft office mac pc compatibility. Exchange does not support the use of Windows Management Framework add-ons on any version of Windows PowerShell or Windows. If there are other installed versions of Windows PowerShell that support side-by-side operation, Exchange will use only the version that it requires.
Microsoft Management Console
The following table identifies the version of Microsoft Management Console (MMC) that can be used together with each version of Exchange.
| MMC | Exchange 2016 | Exchange 2013 SP1 and later | Exchange 2010 SP3 |
|---|---|---|---|
| MMC 3.0 | Supported | Supported | Supported |
Windows Installer
The following table identifies the version of Windows Installer that is used together with each version of Exchange.
| Windows Installer | Exchange 2016 | Exchange 2013 SP1 and later | Exchange 2010 SP3 |
|---|---|---|---|
| Windows Installer 4.5 | Supported | Supported | Supported |
| Windows Installer 5.0 | Supported | Supported | Not supported |
MailTips are informative messages displayed to users while they're composing a message. While a new message is open and being composed, Exchange analyzes the message (including recipients). If a potential problem is detected, the user is notified with a MailTip prior to sending the message. Using the information in the MailTip, the user can adjust the message to avoid undesirable situations or non-delivery reports (also known as NDRs or bounce messages).
How MailTips work
MailTips are implemented as a web service in Exchange. When a sender is composing a message, the client software makes an Exchange web service call to the Client Access server to get the list of MailTips. The server responds with the list of MailTips that apply to that message, and the client software displays the MailTips to the sender.
The following unproductive messaging scenarios are common in any messaging environment:
NDRs resulting from messages that violate organization-wide message restrictions (for example, message size restrictions or maximum number of recipients per message).
NDRs resulting from messages sent to non-existent recipients, restricted recipients, or users with full mailboxes.
Sending messages to users with Automatic Replies configured.
All of these scenarios involve the user sending a message, expecting it to be delivered, and instead receiving a response stating that the message isn't delivered. Even in the best-case scenario, like the automatic reply, these events result in lost productivity. In the case of an NDR, this scenario could result in a costly call to the help desk.
Microsoft Exchange Client Access Rules
There are also several scenarios where sending a message won't result in an error, but can have undesirable, even embarrassing consequences:
Messages sent to extremely large distribution groups.
Messages sent to inappropriate distribution groups.
Messages inadvertently sent to recipients outside your organization.
Selecting Reply to All to a message that was received as a Bcc recipient.
All of these problematic scenarios can be mitigated by informing users of the possible outcome of sending the message as they're composing the message. For example, if senders are notified that the size of their message will exceed the maximum allowed value, they won't attempt to send the message. Similarly, if senders are notified that their message will be delivered to people outside the organization, they're more likely to ensure that the content and the tone of the message are appropriate.
Exchange Email Client
The following messaging clients support MailTips:
Outlook on the web (formerly known as Outlook Web App)
Microsoft Outlook 2010 or later
MailTips in Exchange Online
The following table lists the available MailTips in Exchange Online.
Microsoft has made the Silverlight for macOS browser plug-in freely available for all supported platforms and browsers. Microsoft silverlight for mac safe version. The app is a free plug-in, powered by the.NET framework and compatible with multiple, devices and operating systems, bringing a new level of interactivity wherever the Web works. Microsoft Silverlight for Mac is a powerful development tool for creating engaging, interactive user experiences for Web and mobile applications.
| MailTip | Availability | Scenario |
|---|---|---|
| Invalid Internal Recipient | Outlook | The sender adds an internal recipient that doesn't exist. For example: • The non-existent recipient resolves due to an entry in the sender's Auto-Complete List (also known as the nickname cache) or an entry in the sender's Contacts folder. • The sender types a non-existent internal email address, and the email address is in an accepted domain (an authoritative domain) for the Exchange organization. The MailTip indicates the invalid recipient and gives the sender the option to remove the recipient from the message. |
| Mailbox Full | Outlook Outlook on the web | The sender adds an internal recipient whose mailbox exceeds the maximum mailbox size (the ProhibitSendReceive quota on the mailbox or organization). The MailTip indicates the recipient whose mailbox is full and gives the sender the option to remove the recipient from the message. The MailTip is accurate at the time of display. If the message isn't immediately sent, the MailTip is updated every two hours. This also applies to messages that were saved in the Drafts folder and reopened after two hours. |
| Automatic Replies | Outlook Outlook on the web | The sender adds an internal recipient* who has turned on Automatic Replies. The MailTip indicates the recipient has Automatic Replies turned on and also displays the first 175 characters of the automatic reply text. The MailTip is accurate at the time of display. If the message isn't immediately sent, the MailTip is updated every two hours. This also applies to messages that were saved in the Drafts folder and reopened after two hours. *If the recipient is external, but the recipient's domain is configured as a remote domain, the AllowedOOFType and IsInternal settings determine whether the sender receives the internal automatic reply, the external automatic reply, or no automatic reply at all. |
| Custom | Outlook Outlook on the web | The sender adds an internal recipient that has a custom MailTip configured. A custom MailTip can be useful for providing specific information about a recipient. For example, you can create a custom MailTip for a distribution group explaining its purpose to reduce its misuse. For more information, see Configure custom MailTips for recipients. By default, custom MailTips aren't displayed if the sender isn't allowed to send messages to the recipient (the Restricted Recipient MailTip is displayed instead). However, you can change this configuration and have the custom MailTip also display. |
| Restricted Recipient | Outlook Outlook on the web | The sender adds a recipient that they're not allowed to send messages to (delivery restrictions are configured between the sender and the recipient). The MailTip indicates the prohibited recipient and gives the sender the option to remove the recipient from the message. It also clearly informs the sender that the message can't be delivered to the restricted recipient. If the restricted recipient is external or is a distribution group that contains external recipients, this MailTip is also provided to the sender. However, the following MailTips aren't displayed (if applicable): • Automatic Replies • Mailbox Full • Custom MailTip • Moderated Recipient • Oversize Message |
| External Recipients | Outlook Outlook on the web Outlook Mobile | The sender adds an external recipient* or a distribution group that contains external recipients. The MailTip informs the sender that the message will leave the organization, which can help them make the correct decisions about wording, tone, and content. By default, this MailTip is turned off. You can turn it on using the Set-OrganizationConfig cmdlet. For details, see MailTips over organization relationships. *If the recipient is external, but the recipient's domain is configured as a remote domain, the IsInternal setting determines whether the sender receives this MailTip (the External Recipients MailTip doesn't apply to internal recipients). Note: The External Recipients MailTip isn't evaluated for external distribution group recipients where the distribution group is in a remote domain. Note 2: Outlook Mobile only supports the External Recipients MailTip for Office 365 and for on-premises Exchange mailboxes that use Hybrid Modern Authentication (HMA). |
| Large Audience | Outlook Outlook on the web | The sender adds a distribution group that has more members than the configured large audience size (the default size is more than 25 members). For details, see Configure the large audience size for your organization. The number of distribution group members isn't calculated each time. Instead, the distribution group information is read from group metrics data. |
| Moderated Recipient | Outlook Outlook on the web | The sender adds a moderated recipient (a recipient that requires message approval). The MailTip identifies the moderated recipient and informs the sender that moderation might result in delayed delivery. The MailTip is not displayed if: • The sender is a moderator for the recipient. • The sender has been explicitly allowed to send messages to the recipient (by adding the sender's name to the Accept Messages Only From list for the recipient). To configure moderated recipients in Exchange Online, see Configure a moderated recipient in Exchange Online. |
| Reply-All on Bcc | Outlook on the web | A Bcc recipient selects Reply All a message. The MailTip appears in the reply message. Bcc recipients revealing themselves to other recipients is universally bad, and the MailTip explains this. |
| Oversize Message | Outlook | The message is larger than the maximum allowed message size. The MailTip is displayed if the message size violates one of the following message size restrictions: • Maximum send size setting on the sender's mailbox. • Maximum receive size setting on the recipient's mailbox. • Maximum message size restriction for the organization. Note: Message size limits on connectors aren't evaluated for this MailTip. |
MailTip restrictions
MailTips are subject to the following restrictions:
MailTips aren't supported when working in offline mode in Outlook.
When a message is addressed to a distribution group, the MailTips for individual recipients that are members of that distribution group aren't evaluated. However, if any of the members are external recipients, the External Recipients MailTip is displayed, which shows the sender the number of external recipients in the distribution group.
If the message is addressed to more than 200 recipients, individual mailbox MailTips aren't evaluated due to performance reasons.
Custom MailTips are limited to 175 characters.
While older versions of Exchange Server would populate MailTips in their entirety, Exchange Online will only display up to 1000 characters.
If the sender starts composing a message and leaves it open for an extended period of time, the Automatic Replies and Mailbox Full MailTips are evaluated every two hours.