I’ve tried a number of Mac email clients over the years before settling (for now) on Postbox, but if I were running a company, I’d definitely give Hiri a whirl. Once your company grows, however, the chances are you’re going to need Office 365 and Exchange compatibility – and that’s what the company is now working on … Expand Expanding Close
If the rubber surface of your MacBook has separated from the bottom case, and you bought it between Oct 2009 and April 2011, you’re in luck: Apple has just extended warranty coverage of this specific issue to four years. Apple originally launched the replacement program in May 2011. Full details on the Apple support site (via MacRumors.)
As expected, Apple just released iOS 6.1.2 with a fix for the Exchange bug in iOS 6.1 that we previously reported. The 107mb update is available OTA and comes with build number 10B146 .We reported earlier this month that AOL had informed its corporate employees via email that it would temporarily disable the ability to manage meetings with Exchange on iOS devices running iOS 6.1. AOL confirmed it was working with Microsoft and Apple to fix the “continuous loop” bug, and many had highlighted the problem on Microsoft’s forums.
Fixes an Exchange calendar bug that could result in increased network activity and reduced battery life.
We tried the convoluted unlock exploit on our own iPhone and were able to unlock the screen successfully under iOS 6.1.1, and the same process once again unlocked the phone in iOS 6.1.2. Put simply: it doesn’t look like this update fixes the passcode unlock bug, according to our testing.
A previous report from iFun, which predicted today’s release of 6.1.2, claimed enhancements to maps in Japan that Apple introduced in the recent 6.1.1 beta would reach consumers in the coming weeks as iOS 6.1.3.
We reported on Friday that AOL had informed its corporate employees via email that it would be temporarily disabling the ability to manage meetings with Exchange on iOS devices running iOS 6.1. AOL confirmed that it was working with Microsoft and Apple to fix the “continuous loop” bug, and many had highlighted the problem on Microsoft’s forums. It doesn’t appear Apple addressed the issue with its recent release of iOS 6.1.1, and Microsoft has now published an official support document to detail workarounds for the bug.
When a user syncs a mailbox by using an iOS 6.1-based device, Microsoft Exchange Server 2010 Client Access server (CAS) and Mailbox (MBX) server resources are consumed, log growth becomes excessive, memory and CPU use may increase significantly, and server performance is affected. Additionally, Office 365 Exchange Online users receive an error message that resembles the following on an iOS 6.1-based device: Cannot Get Mail, The connection to the server failed.
Microsoft suggested a few workarounds for the issue while it waits for Apple to fix the bug. First, it informed customers to “not process Calendar items such as meeting requests on iOS 6.1 devices. Also, immediately restart the iOS 6.1 device.” If problems with Exchange continue, Microsoft recommended and provided instructions for removing and recreating the device partnership, creating a custom throttling policy for iOS 6.1 users, or blocking iOS 6.1 users entirely.
Microsoft said it is working with Apple to resolve the issue and recommended customers “open an Enterprise Support case with Apple”: Expand Expanding Close
