Messaging and Collaboration

2024-08-06T09:00:00.000-07:00

How to Configure DKIM for a Custom Domain in Office 365

Enhancing Email Security with DKIM in Office 365

DomainKeys Identified Mail (DKIM) is a crucial email authentication protocol that helps verify the legitimacy of an email sender's domain, ensuring that email content remains unaltered during transit. By enabling DKIM in Office 365, organizations can significantly enhance their email security and improve deliverability. This article provides a detailed, step-by-step guide on setting up DKIM for custom domains in Office 365.

What is DKIM?

DKIM adds digital signatures to outgoing emails, allowing receiving servers to validate the message's origin and integrity. The process involves creating a private key associated with your domain name, which is then used to sign outgoing emails. The receiving mail servers use the public key published on DNS to verify these signatures, ensuring that the emails are genuine and not spoofed.

Step-by-Step Guide to Setting Up DKIM

Step 1: Create Office 365 DKIM Keys

1. Sign in to the Microsoft 365 Security Center:

- Navigate to the Microsoft 365 Security Center and sign in.

- Expand Email & Collaboration and click on Policies & Rules.

2. Access DKIM Settings:

- On the Policies & Rules page, select Threat Policies.

- Scroll down and under Rules, click on Email Authentication Settings.

- Click on DKIM and double-click on your custom domain (e.g., Cloudomega.site).

3. Generate DKIM Keys:

- Click on Create DKIM Keys to generate the signature keys.

- Copy the generated keys to a text editor like Notepad for later use.

Step 2: Add Office 365 DKIM CNAME Records to the Domain’s Registrar

1. Access Your Domain’s Registrar:

- Go to your domain registrar (e.g., Namecheap.com), and navigate to the advanced DNS settings.

2. Add CNAME Records:

- Add the two CNAME records copied from the Microsoft Security Center.

- Refresh the DNS settings page and return to the Microsoft 365 Security Center.

3. Enable DKIM:

- Enable DKIM for your Office 365 domain and click OK.

Step 3: DKIM Record Check

1. Verify DKIM Records:

- Visit [Mxtoolbox.com](https://mxtoolbox.com) and select DomainKeys Identified Mail under All Tools.

- Input your domain name (e.g., Cloudomega.site), use Selector1, and perform a DKIM Lookup.

2. Check Selector2:

- Perform the lookup for Selector2. If no DKIM record is found, return to the Microsoft Security Center and rotate the DKIM keys.

- Repeat the DKIM lookup on Mxtoolbox after rotating the keys.

Step 4: Verify with Message Header Analyzer

1. Send a Test Email:

- Send an email from your Office 365 mailbox to an external address.

2. Analyze Email Headers:

- In Outlook, view the message details by clicking the three dots and selecting View Message Details.

- Copy the message details and visit [mha.azurewebsites.net](https://mha.azurewebsites.net).

- Paste the message details into the analyzer and click Analyze Header. A successful configuration will show DKIM=pass.

By following these steps, you can ensure that DKIM is correctly configured for your custom domain in Office 365, enhancing your email security and improving deliverability.

Conclusion

Configuring DKIM is an essential step in securing your organization's email communication. It helps prevent email spoofing and ensures the integrity of your emails, thereby fostering trust with recipients. By following this guide, Office 365 users can efficiently set up DKIM for their custom domains.

#EmailSecurity #Office365 #DKIM #CyberSecurity #TechTips #ITSecurity #EmailAuthentication #DomainSecurity #TechGuide #CloudComputing #Office365Tips #SecurityAwareness #EmailProtection #BusinessSecurity #DigitalSecurity

Troubleshooting issues with Exchange ActiveSync

2012-02-27T05:26:00.001-08:00

Original Link Here

This is really a nice link to troubleshoot Exchange ActiveSync issues, just make sure that you have IIS logging enabled..

IIS 7

In IIS Manager, expand the server name i.e. ExchangeServer (Contoso\Administrator)
In the Features View, double click Logging in the IIS section.

IIS 6

In IIS Manager, right click the web site name (for most it should be Default Web Site) and chooseProperties
Click on the Web Site tab.

You can use a number of queries as per your requirement and can take it in a nice HTML format as well..

There is yet another site that talks about common error codes in Exchange Active Sync along with there resolution

Exchange ActiveSync error codes

I’ve been troubleshooting Exchange ActiveSync issues on WP7 for a while and thought I would collate all error codes from my personal notes.

You won’t see any official Microsoft documentation supporting these steps, so use it at your own risk.

Error	Solution
0×85010014	Another website other than the “Default website” with host header value same as OWA url
	Improper authentication and settings on virtual directories
	Allow inheritable permissions were unchecked on user’s properties.
0x80072F0D	Invalid certificate on the server
	Root certificate missing on the device
0×85010013	Re-install CAS role along with the latest Service Pack and update rollups
	Set AllowNonProvisionableDevices $true
0×85030027	Allow inheritable permissions were unchecked on user’s properties.
	Microsoft Server ActiveSync directory corruption. Recreated it
0x80072f0d	Removed HTTP redirect from the Microsoft-Server-ActiveSync virtual directory from all the exchange boxes
	Certificate missing external URL
0x80072F17	Allow inheritable permissions were unchecked on user’s properties.
	Invalid certificate on the server
	Root certificate missing on the device
0x80072f05	Root certificate missing on the device
	Invalid certificate on the server
0x80072EE2	Port 80 Blocked from CAS to MBX server
	Certificate missing external URL
0x86000c0a	Allow inheritable permissions were unchecked on user’s properties.
0×85010017	Allow inheritable permissions were unchecked on user’s properties.
0X85010019	Issue with invalid certificate
0×80070057	Recreate Autodiscover virtual directory

Record your PowerShell sessions

2012-01-02T05:23:00.000-08:00

In-case if you want to record your session in PowerShell and wants to take output in a text file for each and every steps that you have done in PowerShell, below are the steps

In PowerShell run the following command (Change location to wherever you would like)

Start-Transcript c:\Powershell.txt –Append

Now use PowerShell as you usually would, once you are done with PowerShell run the following command

“Stop-Transcript” (without quotes)

If you now open the “PowerShell.txt” you will see everything you have just done in your PowerShell session.

********************************************
Windows PowerShell Transcript Start
Start time: 20120102173323
Username : PowerShell User
Machine : Windows 2008 R2 (Microsoft Windows NT 6.1.7600.0)
********************************************
Transcript started, output file is c:\MySession.txt
[PS] C:\>Get-Mailbox –Identity Daniel

Name Alias ServerName
—- —– ———-
Daniel Dan Exchange2010

[PS] C:\>Get-User -Identity Daniel -RecipientTypeDetails

Name RecipientType
—- ————-
Daniel MailUser

[PS] C:\>Stop-Transcript

Happy Recording :-)

OWA Cross-Site Silent Redirection in Exchange 2010 SP2

2011-12-13T22:32:00.000-08:00

Now with the advent of Exchange 2010 Service Pack 2, there is a new feature added that you all might be aware off, which is Cross-Site Silent Redirection. This can be seamlessly achieved by using the CrossSiteRedirectType parameter added to Set-OWAVirtualDirectory command.

There is a beautiful article on Microsoft Exchange Team's webpage which suggests and even demonstrates with a Video about how to achieve this.

MSExchangeTeam Link

Exchange 2010 SP2 Update Issue

2011-12-09T08:32:00.000-08:00

Ever wonder why you are getting an error for when running Client Access Role Prerequisities 'The IIS 6 WMI Compatibility' component is required. Install the component via Server Manager.
This error occurs because a new feature of Exchange 2010 SP2 called Outlook Web App Mini requires that IIS component to be installed on Client Access servers.
You can install the component manually by opening a PowerShell window and running the following commands.

Import-Module servermanager
Add-WindowsFeature Web-WMI
You should get an output as below

Success Restart Needed Exit Code Feature Result
------- -------------- --------- --------------
True No Success {IIS 6 WMI Compatibility}

or alternatively you can run the upgrade command using the following switch
setup /mode:upgrade /installwindowscomponents and upgraded the server

FAQ Questions and Issues related to iPhones connecting to Exchange Servers

2011-12-07T04:20:00.001-08:00

IMPORTANT: iPhone support requires that Exchange is running Exchange Server 2003 Service Pack 2 or Exchange 2007 SP1 or later.

1. Do we have a list that compares the features available and not available when connecting to Exchange ActiveSync using an iPhone?

Exchange ActiveSync Client Comparison Table

2. I'm unable to configure an iPhone with my test environment. Are there any screen shots that show what the device looks like in Exchange Management Console and OWA's Mobile Options after an iPhone has successfully connected?

http://blogs.technet.com/b/exchange/archive/2008/07/11/3405745.aspx

3. If I need to identify connections made by iPhone users, what can I search on in the IIS logs?

Do a string search for "Apple-iPhone".

4. How do I find more information on what policies the iPhone supports, how it connects to an Exchange server and other administrative questions?

Apple's iPhone Enterprise Deployment Guide

5. How can I see how many iPhones are connecting to my server and which users have them?

export-activesynclog -Filename:<IISlog dir>\*.log -outputpath:<output path>

6. Does the iPhone support Autodiscover?

Yes, when connecting to Exchange 2007 and Exchange 2010.

7. Does the iPhone support HTML email?

Yes. iPhone views HTML e-mail as a webpage. This means if there is an image or chart pasted into the message, the width is always that width. This means that reading the message is very difficult as you have to zoom in and then scroll the screen back and forth to read the message.

8. Why does the iPhone support HTML email against Exchange 2003 but Windows Mobile does not unless I'm running WM 6.x against an Exchange 2007 server?

Window Mobile uses the AirSync body property which did not support HTML until Exchange 2007. Apple uses a different implementation. Questions about what Apple does should be directed to Apple. But there is no secret HTML interface in Exchange 2003 ActiveSync.

9. Do the iPhones support Direct Push?

Yes, but EAS Direct Push may not work on iPhones that have multiple mail accounts setup that are also in Push mode. Examples of this would be Yahoo Mail in Push mode. Simply disable Push notification for the non-Exchange mail accounts and EAS Direct Push should start working.

10. Self-signed SSL certificates - There is no "simple" way to install a self-signed certificate to the iPhone. Customers can contact Apple for instructions on how to do this. The iPhone can "read" .pfx files for example, so if you can get the certificate to be opened on the iPhone whether through a webmail

client or otherwise, then you should be able to import a self-signed certificate to the iPhone. Apple does have instructions on this listed in the Enterprise Deployment Guide. Link:
<http://manuals.info.apple.com/en_US/Enterprise_Deployment_Guide.pdf> (see page 36).

11. Performance questions - Customers asking for direction regarding the load an iPhone EAS client will place on their servers should be told the iPhone's load should be no different than any other Windows Mobile EAS client. The only caveat is the iPhone downloads the ENTIRE message vs. Windows

Mobile's .5k / 2k / etc. configurable chunk size. This can create more traffic for iPhone EAS clients.

12. I'm getting an, "Exchange account verification failed", error message. What do I do?

Here are some things to try:

a. Disable WiFi during setup (make sure they're only going over the cell connection)

b. Make sure they're putting in domain/username, then try with domain\username (note backslash direction). If that doesn't work, try using just username with no domain.

c. Try with & without SSL. When you get the error "Exchange account verification failed", click Next then Save, then edit the mail profile in Settings (off home screen) and set SSL to OFF vs. ON.

d. Use the same FQDN name of the server (usually users call this their "OWA" address), or external IP address.

e. As a test, temporarily disable certificate verification (certificate authentication) on the /Microsoft-Server-ActiveSync virtual directory by selecting the "Ignore Client Certificates" option (if it were set to cert verification, the setting for "Accept client certificates" would have been selected). Don’t forget

to disable it if the customer has that intention. The iPhone may just need to have a certificate loaded (have customer review Apple’s Enterprise Deployment Guide for the iPhone).

13. User is CC'd on every reply all - If an iPhone user configures their Exchange ActiveSync profile using something other than their default SMTP address, then the iPhone will add this [non-default SMTP] e-mail address to all Reply All messages. The solution is to configure using whatever is listed as the

default SMTP address for that user in the company GAL. To find that value: look the user up in Outlook and click the E-mail Addresses tab. Use the value next to the capital letter SMTP. The listing is usually something like this:
SMTP:usera@domain.com
smtp:user.a@domain.com
smtp:usera@mail.domain.com
In the above example, the user should be using usera@domain.com.

14. Does iPhone support Certificate Based Authentication when using iPhones.

Both Microsoft AND Apple do NOT support certificate authentication when connecting using iPhones and Exchange ActiveSync.

16. I'm able to successfully create a profile on my device and am able to successfully connect to Exchange, but I'm not able to synchronize my Inbox, Calendar, or Contacts? What gives?

Check to be sure that Exchange is running Exchange Server 2003 with Service Pack 2 or later. Previous versions are NOT supported and can cause this issue.

17. When using an iphone with Exchange ActiveSync, email attachments may not download for some users. Tapping the attachment to start the download shows a spinning wheel which never stops.

This issue can occur when you're running Exchange 2007 RTM. To resolve the issue, install Exchange 2007 Service Pack 1. For more information, see Apple's documentation: http://support.apple.com/kb/TS1946

There is another WONDERFUL E-E article that talks about Exchange 2003 and ActiveSync connections problems and gives a deep dive into resolution as well
Exchange 2003 - Activesync Connection Problems FAQ

If you are facing isssues with only a few set of users not able to sync there mobile phones using Exchange ActiveSync irrelevant of type of device that they are using, check this another E-E link
Activesync Working But Only For Some Users On Exchange 2007 / 2010

Happy ActiveSyncing :-)

Microsoft Exchange Server 2010 Service Pack 2 (SP2) now available for download

2011-12-06T23:26:00.000-08:00

Microsoft Download Center Link

Default IIS Authentication for Exchange 2003, 2007 and 2010

2011-11-30T06:06:00.000-08:00

Exchange Server 2003
Front End and Back End Topology
Virtual Directory	FE	SSL Required	BE	SSL Required
Default Web Site	Anonymous	Optional	Anonymous	No
Exadmin	Integrated	No	Integrated	No
Exchange	Basic	Optional	Basic/integrated	No
Exchweb	Anonymous	No	Anonymous	No
Active Sync	Basic	Optional	Basic	No
Public	Basic	No	Basic/integrated	No

Exchange Server 2003
Single Server Topology
Virtual Directory	Server	SSL Required
Default Web Site	Anonymous	Optional
Exadmin	Integrated	No
Exchange	Basic/integrated	No	If SSL is required then follow KB-817379
Exchweb	Anonymous	No
Active Sync	Basic	Optional
Public	Basic/integrated	No

·Default Authentication of IIS

Exchange 2007 Client Access Server
Location	Authentication	SSL Setting	Comments
Default Web Site	Anonymous	Required	"Enable HTTP Keep-Alives" setting should be enabled on Web Site tab
/Owa	Basic	Required	Management of authentication setting should be done in Exchange Management Console
/Exchange	Basic	Required	Management of authentication setting should be done in Exchange Management Console
/Public	Basic	Required	Management of authentication setting should be done in Exchange Management Console
/Exchweb	Basic	Required	Management of authentication setting should be done in Exchange Management Console
/Oab	Integrated	Not required
/Autodiscover	Basic and Integrated	Required
/Ews	Integrated	Required
/UnifiedMessaging	Integrated	Required
/Microsoft-Server-Activesync	Basic	Required	Management of authentication setting should be done in Exchange Management Console
/Rpc	Basic and Integrated	Required	Technically, this is a Windows component but I've added it here since Outlook Anywhere depends on the installation of this virtual directory

Exchange 2007 Mailbox Server
Location	Authentication	SSL Setting	Comments
Default Web Site	Anonymous	Not required
/Exadmin	Basic and Integrated	Not required
/Exchange	Basic and Integrated	Not required	Management of authentication setting should be done in Exchange Management Console
/Public	Basic and Integrated	Not required	Management of authentication setting should be done in Exchange Management Console

Exchange 2007 CAS + HUB + MBX
Location	Authentication	SSL Setting	Comments
Default Web Site	Anonymous	Required	"Enable HTTP Keep-Alives" setting should be enabled on Web Site tab
/Owa	Basic	Required	Management of authentication setting should be done in Exchange Management Console
/Exchange	Basic and Integrated	Required	Management of authentication setting should be done in Exchange Management Console
/Public	Basic and Integrated	Required	Management of authentication setting should be done in Exchange Management Console
/Exchweb	Basic and Integrated	Required	Management of authentication setting should be done in Exchange Management Console
/Oab	Integrated	Not required
/Autodiscover	Basic and Integrated	Required
/Ews	Integrated	Required
/UnifiedMessaging	Integrated	Required
/Microsoft-Server-Activesync	Basic	Required	Management of authentication setting should be done in Exchange Management Console
/Rpc	Basic and Integrated	Required	Technically, this is a Windows component but I've added it here since Outlook Anywhere depends on the installation of this virtual directory

Exchange 2010 All in One Box

Virtual Directory	Default Auth Setting
/Autodiscover	Anonymous, Basic, WIA
/ECP	Anonymous, Basic
/EWS	Anonymous, WIA
/MS-Server-Activesync	Basic
/OAB	WIA
/OWA	Basic
/PowerShell	Anonymous
/RPC	Basic, WIA

Recommended Windows Hotfix for Database Availability Groups running Windows Server 2008 R2

2011-11-30T06:00:00.000-08:00

If you are using DAG configuration on your Windows Server 2008 R2 Servers consider applying the following hotfixes.

http://support.microsoft.com/kb/2549472 - Cluster node cannot rejoin the cluster after the node is restarted or removed from the cluster in Windows Server 2008 R2

http://support.microsoft.com/kb/2549448 - Cluster service still uses the default time-out value after you configure the regroup time-out setting in Windows Server 2008 R2

http://support.microsoft.com/kb/2552040 - A Windows Server 2008 R2 failover cluster loses quorum when an asymmetric communication fail

Original Link

PowerShell for Microsoft Exchange 2010 Cheat Sheet!

2011-11-07T08:35:00.000-08:00

Extract from PowerShell for Microsoft Exchange 2010 Cheat Sheet!
When working with customers, everyone who is new to Windows PowerShell finds it to be an amazing idea, but very daunting. Once you start using it, you will quickly pick up the syntax and how to structure your commands. However, it can take a while to get to know which cmdlet to use, and what each cmdlet can do!
To help address this, Matt Abraham has created a “Cheat Sheet” with a list of some of the most important Exchange 2010 PowerShell Cmdlets. A lot of these can also be used with Exchange 2007 as well!

Cheat Sheet Download Link!!

Exchange Posters, Visio Stencils, and More

2011-08-06T07:15:00.000-07:00

On this Exchange TechNet Wiki page you find the various posters and Visio stencils that exist for Exchange 2007 and 2010.

http://social.technet.microsoft.com/wiki/contents/articles/exchange-posters-visio-stencils-and-more.aspx

Bye Bye IPv4.. last day June 8, 2011

2011-07-07T09:03:00.000-07:00

Today is the last day for IPv4, now On June 8, 2011, Bing.com, Xbox.com, along with Internet properties from a host of technology companies, will be participating in World IPv6 Day.

Check World IPv6 Day and Windows for more information...

Scroll to the bottom of the page and you World IPv6 day page and check if you are ready

I have checked my machine and made sure that I am ready for IPv6 are you??

Exchange Server and Update Rollups Builds Numbers

2011-07-07T08:44:00.000-07:00

Every wondered how can you verify the built number when working on some issue with Exchange?
Here is the link that is updated regularly with the latest builds and make sure that scroll to the bottom of the page where you will find a nice link from Bhargav Shukla - MSFT that gives you the PS script to find it.

How To Find Which Exchange 2010 CAS Node a Client Connects To in a CAS array Scenario

2011-05-22T09:24:00.001-07:00

In an CAS array scenario we cannot be certain as to which CAS server we are connected to as the request is catered by CAS array

There is a way by which we can find the CAS NETBiOS name from where the request is catered from: -
Open Outlook Web Access if its working :-) and Click on “?” and then click “About”
The window will show you a lot of information, including a field called “Exchange Client Access server name” that will tell you the CAS array node name which you are connected to.

This can help in many ways wherein you are troubleshooting CAS array issues, and can let you concentrate on a single node first and then moving on.

Announcing a Windows Phone app for the Exchange Team Blog

2011-05-15T12:33:00.000-07:00

Take it with you where ever you go :-) Click on the link below to read more..

Announcing a Windows Phone app for the Exchange Team Blog

I completely agree with Bhargav's point here “any Exchange engineer not reading EHLO blog is NOT an Exchange engineer, period.”

Exchange ActiveSync Error Code 80072FA8

2011-04-20T06:07:00.000-07:00

Recently I stumbled upon an issue wherein ONLY Windows Mobile 7 devices were not able to sync with Exchange 2003, when we tried to sync a Windows Mobile 6.5 device it worked like a grace

When trying to sync a WM 7 device with Exchange ActiveSync we were getting error 80072FA8

Obviously it was nothing from the server end that we needed to check since all other Mobile Devices were syncing fine

We checked with APN settings on WM 7 devices and corrected it

Steps: -

1. Start (menu) Button;

2. Choose Settings from the program list;

3. Make sure the system settings are selected in the panorama (and not the application settings);

4. Scroll down to cellular

5. Click on the edit apn button to hard reset your Windows Phone 7 device;

6. Enter the APN settings: APN, username, password

7. Confirm by clicking on the left check-icon in the slide-up menu.

A nice screenshot can be found @

http://www.mobilityminded.com/10663/how-to-change-data-connection-settings-like-apn-in-windows-phone-7

Announcing the Re-release of Exchange 2010 Service Pack 1 Update Rollup 3 (V3)

2011-04-09T11:12:00.000-07:00

After a few initial hiccups Microsoft has finally managed to re-release RU3 for Exchange 2010 SP1
More information can be read here

My First Blog and Post :-)

2011-04-01T12:41:00.000-07:00

This thought of writing blog was going on in my mind since looong but finally I am making an attempt to write something and want to share my experience with this world of IT.

Incase, if you find anything that needs attention or change feel free to respond with your comments..

I want to start with sharing
Announcing some cool new features coming soon to a server near you

Today seemed like a perfect day for us to share a few very special announcements with our customers. We are always looking for ways to make Exchange better. Here are some of the new features we've planned for Exchange 2010 SP2.

OWA Automobile Edition: Exchange team and a major US automaker will soon announce OWA integration into new line of cars to maximize end-user productivity. Car windshields are to be replaced with LCDs (who needs windshields anyway?) Additionally, when it's time for oil change, you will get a reminder popup.
Twitter-Ready Mail: Exchange 2010 SP2 will enforce a maximum email length of 140 characters to ensure all email is Twitter-ready. If you have more than 140 characters of things to say, you are clearly egotistical and self-centered. To help you save the characters, we will also enforce all email to be in clear text format. An 80-page whitepaper with business-ready abbreviations to use will be published at release time.
Boss OOFs: Out of Office Assistant (Automatic Replies) now has a “boss” feature, which will send a different message to your upward reporting chain in the GAL than everyone else. Now, you can be “out sick with the flu” to your boss while “kicking ass and taking names” in Vegas to your buddies.
Email Etiquette Enforcement (EEE) Agent: We are finalizing the steps to implement a new Email Etiquette Enforcement Agent. The EEE Agent will enforce a uniform email etiquette within your organization by allowing you to create Email Etiquette Rules, similar in concept to Transport Rules. Exchange will ship with a few pre-canned Email Etiquette Rules, such as the "Exceeded Max Recipients You Should Be Replying To Per Good Email Etiquette" rule. If the offending user replies to "all" on a very large distribution group with something totally meaningless, the system will send a custom DSN to that user every 10 minutes for a week, as a reminder of what he has done. Currently, two DSN wordings that we're looking at are:

5.7.11.1 Srsly? You did that? Will you do it again?
and

5.7.11.1 How do YOU like to have your mailbox filled up with useless replies?
Another EEE rule will detect the number of messages a user sends with a Read Receipt requested, and if it exceeds 10% of all email sent by the user, the EEE agent will respond by automatically modifying all messages received by that user to require a read receipt'.
Automatic Randomized MRM (ARM) Assistant: Based on the success of the MRM feature in Exchange, we are taking MRM a step further by creating an Automatic Randomized MRM (ARM) Assistant. This takes all of the work out of configuring MRM policies; the Assistant will simply pick messages from your mailbox randomly and archive them for you – at random intervals; to random places. No user or administrator configuration is necessary (or possible).
Active Inbox Rules (AIR) Agent: The Exchange engineering team is especially proud of its extensibility features. The AIR Agent is a step in this direction, allowing you to manage users' email based on their past behavior, and reduce TCO. The AIR agent interfaces with your helpdesk system and reads the number of "I can't find my email" tickets created by a user. If the message is found to have been automatically moved by an Inbox rule that the user created, the AIR agent automatically creates a server-side rule to move such items back to the Inbox. This should greatly reduce the number of helpdesk tickets created by the user.
If the user creates any additional rules to move messages, the agent responds by creating server-side rules to move messages from all folders back to the Inbox. This action is completely transparent to the user.
Mobile Read Receipts: Given so many of you now consume email on your mobile devices, we are positive you'll find this new mobile feature quite useful. When you receive a message with a read receipt requested on your mobile device, the mobile email client will activate the camera on your mobile device and transmit a video to the sender, really proving you've actually read the message. Mobile Read Receipts are sent with important metadata information such as your expressions (visual and verbal), and your GPS coordinates.
Exchange Configuration: Due to long-lasting popularity of public folders, we are making required engineering changes to store Exchange configuration data in public folders, rather than Active Directory. We are now working through seemingly paradox fact that in order to read that configuration, public folder database needs to be mounted; which requires configuration to be read in the first place. From public folders... which are not mounted... because configuration is not accessible, as the folders are not up at the time. Anyway, we are sure we'll figure it out by SP2 RU1.

Isn't this AWESOME??