Q: How do I create a folder in the iPhone Mail app?

A: YOU CAN’T!

It’s another mystery of life. Why in the world can’t you create a folder in the iPhone Mail app!!?? You can move an eMail message, or a group of messages from one folder to another, but you can’t create a Mail folder on the iPhone. It’s just another of the glaring oddities of the iPhone.

I can understand not being able to do this with a POP account, because iPhone Mail doesn’t sync the mail messages themselves via iTunes. So it would follow, you couldn’t sync newly created folders with moved messages from the iPhone.

One would think though, it could be done with an IMAP eMail account. But it’s just not so.

It’s an enigma wrapped in an enigma wrapped in a burrito …

My only suggestion to all offended and incredulous iPhone user, is

And so it has come to pass. The magic “Jesus Tablet” has come to mere mortals. And it’s name is iPad! Like Manna from Steve Jobs and company, it has been delivered unto us this holy day Wednesday, January 27th 2010. Steve came from the mount @ 1 Infinite Loop and presided over his flock from a singular leather chair, stage left of the Yerba Buena Center for the Arts Theater, San Francisco. The “reality distortion field” is strong with this one. I could only imagine the excitement of the yet unanointed.

With so many rumors flying, no one knew what to expect. Would Steve start with something innocuous, the new iPhone OS (which didn’t happen) or a new iPhone (which also didn’t happen) and then at the last moment …. oh … just one more thing. No. He launched straight away into setting up and introducing the new iPad.

There will be those that will rip it apart for what it doesn’t do. No phone. No Camera. No Verizon. No multitasking. But as a consultant, I need to talk about what it does do. And the possibilities it brings. Oh. And the joy!

Okay. That may be a little harsh … but you would think after paying for a system upgrade, that was supposed to be rewritten from the ground up … a major bug like the IMAP/PHP bug would have been fixed. I know this problem is still effecting people. They are still logging complaints at Apple’s Discussion Groups. I was hoping … but no go!

I have been an Apple user/evangelist (current translation: fanboy) since I bought my first Mac Plus sometime in 1986. I purchased that little beige wonder to use in my recording studio in Asbury Park, NJ. I always thought Apple was bulletproof. They could do no wrong, and always cared about the experience of the Mac user.

Do I still feel that way? I’d be a blind zealot if I said yes. There have always been questionable calls on Apple’s part throughout the years. But at some point Apple stepped up to the plate, took responsibility and made things right. No matter what the cost. Financial or otherwise. It seems this concept gets harder and harder for Apple. For whatever reason.

It started June 25th with my post “Apple Developer {dis} Connection or … How My Apple ID Was Hijacked“. I explained how my Apple ID was hijacked by someone,

Warning: This post in not about programing. It’s about an Apple ID security breach.

Updated: 07.02.09
Updated: 06.28.2009
Updated: 06.26.2009

I have always had a fascination with the idea of developing for the Mac. I guess those seeds were planted “… way back in the days of old” when I was creating custom stacks in Apple’s HyperCard, or creating custom databases in Filemaker. Developing for the Mac, or now for the iPhone, is one of those dreams many Apple Fan Boys and Girls have had. To build that one illusive application that everyone wants. Needs. Must have! Cha ching! Hey … I didn’t say my motives were altruistic.

It was with these thoughts in mind that I went out the other day and bought “Programming in Objective-C 2.0” by Stephen G Kochan and Erica Sadun’s “The iPhone Developer’s Cookbook“. Yesterday I started reading Programming in Objective-C 2.0. To get started I needed to log into my Apple Developer Connection account and download the latest version of the Apple developer tools which includes Xcode, Apple’s programing environment.

While I was there I also registered for the iPhone Dev Center. To do so I had to register with my current Apple ID. I then needed to fill out an iPhone developer questionnaire. With that done I could then download the latest version of the 2.08GB Apple iPhone SDK.

Sometimes things don’t always go as planned …

Woke up this morning and I got myself a …. PwnageTool. Been waiting for this since iPhone OS 3.0 was released in iTunes Wednesday (6.17.09). Well me and thousands of others who were “refreshing” the crap out of the Dev-Team blog/website the past several days, or following the Dev-Team on Twitter, waiting for PwnageTool to post. That may not seem like a long time to most, it’s like seven lifetimes to those caught up in the iPhone reality distortion field. But here it is, with its new updated app smell. And it’s ability to unlock my 1st Generation iPhone.

You have to love these guys. They are modern day heros. Now Apple might think contrary, but you have to admire the Dev-Team’s vibrato. Their stamina. Their commitment. This disparate group of programmers, hackers, telecom industry workers, et al, from all over the world, doing what Apple should have done all along. Make the iPhone open to any and all GSM networks around the world.

Sound the horns! Release the doves! Call your Mom! iPhone OS 3.0 is coming! Tomorrow! (06/17/2009) There has been so much hype leading up to this release you’d think it was the second coming. But it’s not. It’s the third … coming of the iPhone OS that is. Along with it will come a new iPhone too. The iPhone 3G S. They say the “S” is for speed. I think the “S” is for “Sales” through the roof. Even before its release, preorders are sold out. Undoubtedly there will be lines starting at an Apple or AT&T store near you.

There has been a huge ramp-up for the release, starting long before last weeks “World Wide Developers Conference” (WWDC). The fan-boy blogs and the Twitter-verse has been on fire.

I always use to think that the squeaky wheel always got the proverbial grease. In most case this may be true. With Apple … not so much.

Apple just released Mac OS X 10.5.7 update. Being a consultant I always have to do updates on the day they arrive. I do this to try to see what my clients might have to deal with if they choose to do it on their own. Though most of my clients will wait for me to “feel the pain” so they don’t have to.

This update, I did feel the pain! Since I bought my new MacBook Pro, I have been doing updates via Software Update. This time around I chose to download the Combo Updater & give it a whirl. Once downloaded I opened the image and started the process. When the 729 MB update was finished, I restarted the computer. Or at least tried to.

In my previous post “A process to a kill” I outlined an issue with Apple’s Mail.app creating too many IMPA processes on the web hosting server it was connecting to. Read the previous post for the details. With the help of a senior tech at blueHOST.com I have found a temporary fix, until Apple addresses the issue.
For those with access to the cPanel for their hosting account, you will need to create a Cron Job. At blueHOST.com I have access to this feature. Using the blueHOST GUI interface for the UNIX crontab program, I created a cron job via the cPanel to run every two minutes (because I have so many users running mail at the same time.) And the command is “killall imap” (without the quotes). This will do as advertised, kill all imap processes, old and new, every two minutes. You can set the amount of minutes to anything you want.

Since one of the more recent updates, (I wish I could pinpoint the exact one) when starting up Mail.app multiple processes are opened on my web hosting company’s (blueHOST.com) server. Most times between 8-10. The big problem is they won’t die until either I close Mail.app or kill the process manually via my cPanel’s process manager. As a single user in a one man company, this doesn’t really effect me. In an office of 3 or more people this is a BIG issue. Especially if their website or blog is hosted by the same company, on the same server.

I discovered this issue while working on a clients website. Each time I tried to connect to their blog I’d get a server side page that said, to many processes try again later. Or something to that effect. I called blueHOST.com but got a 1st level tech who had to put me on hold, ask someone questions then come back with not many answers. To be fair to blueHOST this was an exception to always stellar tech support.