You can follow any responses to this entry through the RSS 2.0 feed.
You can leave a response, or trackback from your own site.
Paypal Payment
Translate Blog
eMac Tag Cloud
AGO
Apple
Apple Developer Connection
Apple ID
AT&T
Attorney General's Office
blueHOST.com
Clients
CSS
Death Star
eMac Consulting
errors
folder
G5
hack
hot
How-To
iCal
iMac
IMAP
IMAP server process
iPhone
iPhone Dev-Team
iPhone Dev Center
iPhone Mail
Joe Hutsko
Joey Appleseed
JOEyGADGET
keyboard
laptop
mac computer help in seattle
Mac consulting seattle
mac crashing
mac help seattle
mac system design
mac troubleshooting
Mail.app
PHP
PwnageTool
reality distortion field
San Francisco
Steve Jobs
stunning
T-mobile
Twitter
Categories
- Apple (14)
- Apple LED Cinema Display (2)
- Client Work (2)
- Developer Connection (1)
- eMail (6)
- Events (4)
- Hardware (2)
- Hardware Update (3)
- How-To (5)
- iMac (2)
- iPad (1)
- iPhone (18)
- iPhone Mail (2)
- iPhone Issues (3)
- iPod (1)
- Issues (6)
- MacBook Pro (3)
- Macintosh (8)
- Mail.app (4)
- News (12)
- OS X 10.5 (6)
- OS X 10.6 (1)
- Programming (1)
- Review (3)
- Software (2)
- Software Update (5)
- System Update (3)
- Theme (2)
- Tips (5)
- Twitter (2)
- Website (1)
- Wordpress (3)
Recent Posts
- FAIL + Noise = Replaced Apple 24″ LED Cinema Display
- How To: Create A Folder in iPhone Mail
- iPad … It’s Magically Delicious!
- How To: Create IMAP Mail Account on iPhone
- Snow Leopard – Mail.app – PHP … Fail!
- My Hijacked Apple ID … continued …
- So many services. So little time.
- Tweetboard: Twitter Based Website Forum
- Apple Developer {dis} Connection or … How My Apple ID Was Hijacked
- I came. I saw. I pwned.
Recent Comments
- Joe Streno on FAIL + Noise = Replaced Apple 24″ LED Cinema Display
- JuanGuapo on FAIL + Noise = Replaced Apple 24″ LED Cinema Display
- 'App farming' update: Apple says only 400 accounts compromised on My Hijacked Apple ID … continued …
- Stuart on My Hijacked Apple ID … continued …
- Joe Streno on My Hijacked Apple ID … continued …
Mac OS X Hints
TUAW
MacWorld
Archives
- June 2010 (1)
- February 2010 (1)
- January 2010 (1)
- November 2009 (1)
- September 2009 (1)
- July 2009 (2)
- June 2009 (4)
- May 2009 (1)
- April 2009 (1)
- March 2009 (3)
- February 2009 (1)
- January 2009 (4)
- October 2007 (2)
- September 2007 (1)
- August 2007 (3)
- July 2007 (7)
- June 2007 (1)
Apple Inc
- Apple Inc
- Apple Store
- Repair Status
- Support
- Support: Hardware
- Support: iPhone
- Support: iPod
- Support: Mac OS



A process to a kill.
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.
I ended up doing my own research. I called my client, had them quit Mail.app on all 3 computers in that office. I went to their cPanel & killed any remaining processes. I then screen shared with each computer & started each remotely. For each user relaunched they created around 8 + processes each. And these IMAP processes would not die until Mail was quit, or killed manually. There were some IMAP processes that didn’t die and had to be killed manually.
I called BlueHost again today and got an amazing tech. I again explained the issue to him. “How odd” he said, “let’s see what we can find.” So we spent 30 minutes on the phone trying many different things. He on his end and me on mine. I even tried Entourage using IMAP. Entourage only opened 1 connection, and that was it. No multiples.
In searching Apple Support Forum I found this thread “Topic : Mail is killing the processes on my server with IMAP” talking about the very same issue. There were multiple people with different web hosting companies reporting the same behavior. So I’m not alone in this and the problem does indeed exist. The thread showed no “solution” to the issue yet. Bummer!
Now I hope Apple is listening, and fixes the issue very soon.
(I also sent this to MacFixtIt)