iPhone 2.0: .Mac “Push” Email?

Ask and ye shall receive, dig deep into the code and ye shall find fresh-baked Apple-y goodness.
No sooner did Apple drop iPhone 2.0 SDK Beta 5, than the developers began scouring it for any hint of what’s to come, and as usually TUAW serves up what they found:
A certain, unnamed individual sent us some pictures of the latest build of the iPhone firmware showing .Mac push e-mail. The picture shows the main Settings page with a new button: “Fetch new data.” When you click the button, you are taken to a list of your mail accounts, where you can choose between either “fetch” or “push.” According to Mr. Anonymous, while .Mac is offering push e-mail, you are currently not able to do contact or calendar syncing.
Check out TUAW’s gallery for the pics.
Boy, Apple is pushing the features fast and furiously. We already knew about “push” via the Microsoft licensed ActiveSync, which offers full Exchange support, but complementing that with .Mac for non-Exchange users? Very nice!
(Of course, much as I love Back-to-My-Mac, iSync, iDisk, and other .Mac features, it really needs a more competitive feature-set upgrade — Imagine Google-like offerings and capacities with Apple’s ease of use and integration! — especially for the rather steep $100 a year.)
June really can’t come fast enough!










May 8th, 2008 at 12:35 am
What I do not understand about all that push mail hype: The normal, simple IMAP protocol has included push mail for years now. I had push mail on my Treo from a normal IMAP account of my employer using a normal e-mail software (chattermail). And it worked like a charm.
So why the heck should I have to pay for .mac to get push mail if this also works with normal e-mail accounts…? Or just be restricted to mail providers like Yahoo who are affiliated with Apple? (Which does, btw., not work reliably at all…)
I do not like to see Apple crippling standard IMAP features of their e-mail software to make money from some non-standard applications and protocols like .mac or from exclusive deals like the one with Yahoo. THIS is what this article should be about, and not “YEAH we get push mail via .mac”. But it looks like as a former PC user I have not quite tuned in into the “all Apple does is wonderful” chorus of you Apple fanboys….
May 8th, 2008 at 5:42 am
Hi RolloM,
My understanding is that regular vanilla IMAP does not offer “push-like” functionality. For that, we require support for IMAP IDLE. IMAP by itself is the same as POP; it is either on, polling the server for new messages, or off and not knowing whether new messages have arrived. IDLE adds an in-between state, where it issues IDLE commands to pick up new messages is a pseudo-”push-like” experience.
For this to work, however, the service provider has to support the IDLE on their end, and many don’t, including Gmail (I don’t remember if .Mac already does, but if they don’t Apple is adding support as a feature, which would make it more valuable for iPhone users). It is rare enough among freemail providers that Yahoo was the only one to take a stab at it in time for the iPhone. If/when Gmail does it (and remember, they just barely got a somewhat kludgy implementation of IMAP running very recently), we’ll probably see support for that as well.
True push, like Blackberry connect and Microsoft ActiveSync literally have the server keep track of the client and push notifications or messages directly to the client, no polling or command requests required.
On a side note, it’s very important that there are 2 kinds of IMAP, standard and IDLE enabled, because some of us, like me in Canada, pay HUGE premiums for data and if my phone was constantly polling a server, my data bill would require me to remortgage my house…
May 8th, 2008 at 5:44 am
I agree that Apple needs to get on the ball and implement the simple IDLE protocol for IMAP (that’s what makes IMAP mail push if both the server and client support it). I really wish they’d do push Gmail. Seems like Apple is buddy-buddy enough with Google. (I don’t know if Gmail mail servers implement the IDLE protocol, but they should.)
Getting off on a tangent, I find it interesting the balancing act Apple does between Google and Yahoo on the iPhone. Google is the default search engine and there’s Google Maps, but Yahoo has push email and powers the weather and stock applets. And Apple TV supports Flickr (Yahoo) but not Picasa (Google). I wish Apple would let Google have push Gmail on the iPhone and include Picasa support on Apple TV.
May 8th, 2008 at 6:28 am
@RolloM
In defense of Yahoo push on the iPhone, since the last outage a few months back I have had no issues what so ever. Look at all the Blackberry outages within the last year…
May 8th, 2008 at 8:05 am
@Bad Ash, It’s not that Yahoo email has outages (does it? I’ve never noticed one), it’s that the push email on the iPhone can be capricious- some times it just stops working. That doesn’t mean you can’t manually check for Yahoo emails - you can - but that the push notifications stop coming in (so you falsely assume that you don’t have any new emails when in fact you do). For me, either restarting the device or putting it in and out of airplane mode or simply turning push setting off then back on clears things up. IMO it’s been better since firmware 1.1.4 compared to earlier, but it’s still not 100% reliable. Push email that you can’t rely on to work isn’t particularly useful to me. I couldn’t tell you if it’s Yahoo’s fault or Apple’s, but it’s someone’s fault and Apple needs to make sure it gets sorted. I sincerely hope that push email for Exchange ActiveSync and .mac work reliably.
May 8th, 2008 at 10:21 am
It took Google YEARS just to get IMAP working — and working poorly in my humble opinion as the translation of labels to folders results in an incredible waste of bandwidth and space as each message can be in multiple folders at the same time — so IDLE may be a ways off for Gmail yet…
(I’m not sure how difficult/costly it is to implement either, as that may be a factor for “free” email providers — if everyone is polling their servers all the time, it could be too “expensive” at scale)