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. On completion the update stayed at the “blue screen” with the progress indicator spinning and spinning. After about 15 minutes, I just forced a shut down, and restarted, After about 2 reboots of its own, the computer started up and booted into the Finder. Once there, I rebooted once more for good measure, to be certain things were working okay.
I looked around for any obvious “newness” but didn’t see anything I could identify as new. So my first stop after that was to launch Safari and go to my BlueHOST cPanel. I started the process manager and finally launched Mail.app.
I was hoping that the infernal and internal IMAP process bug was fixed. Upon going back to Safari and refreshing the process manager, to my horror and profanity, there they were … the 16 IMAP processes that I hoped would not be there. Grrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr!
So the one thing I was hoping to be fixed was not. I immediatly went to the Apple Forum and posted to the “Topic : Mail is killing the processes on my server with IMAP” thread and posted my findings. I also wrote up the issue AGAIN and sent it to MacFixIt, who also promptly ignored my eMail and did not report the issue. And today I made a comment on the Troubleshooting Roundup: Mac OS X 10.5.7 Update article on TUAW about the issue. With any luck they will look into it further.
I’m not going to deal with any of the other bugs introduced, or not fixed, because so many of the other online mags & blogs have covered these ad nauseam. I have my axe to grind and this IMAP issue is mine. Double Grrrrrrrrrrrrrrrrrrrrrrrrrr!
At this point I feel like I’m talking to myself. Though there are those on the Apple Forums who are also feeling the pain … because Apple’s not listening. I guess I could switch eMail clients, but I WANT to use Mail.app. I even looked into a few other mail applications … but none have the features I can get with Mail.app and 3rd party plug-ins. So I’ll bare my cross and stick with my mission … to get someone else to lay into Apple to fix the problem.
