Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Stop Mail.app from caching too many IMAP folders' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Stop Mail.app from caching too many IMAP folders
Authored by: yogieric on Aug 23, '05 02:22:58PM
I tried to call Apple-support and they said apple was unaware of the problem and that it would take multiple people reporting bugs before they fixed it. I filed a bug. Here's the correct way to file a bug:

1. Create an apple developer account (they're free and you don't have to be a developer):
http://developer.apple.com/membership/?nav (click "Join Now")
1b. You will get an email and have to confirm you setup your account properly.
2. File a bug:
https://bugreport.apple.com/cgi-bin/WebObjects/RadarWeb.woa (login and then select "new problem")

I recommend you include a link to this page.

This bug is a major problem IMHO. Every company I've worked at for the past 10 years has had exchange with huge public folders. My PowerBook G4 1.25GHz spends 30-50% of its CPU most days and nights running Mail alone.

I just installed the latest security patch which brought mail from 10.4.2's 2.0.2 to 2.0.3. The problem is not resolved. I think the best solution is probably to go back to 10.4.1 at this point. And maybe backup Mail 2.0.1 and see if it will run under 10.4.2+ releases. This is not a task I look forward to... I'll probably stop at an apple store and try and get one of their guru's walk me through it.

BTW, my setup in mail is to configure my exchange account as an IMAP email account. I've had no problems with that configuration unlike one other user that chimed in here.

[ Reply to This | # ]

Stop Mail.app from caching too many IMAP folders
Authored by: Carphunter on Aug 30, '05 04:39:12PM

I went ahead and created a bug report... but it just got marked as Duplicate and they don't acknowledge if they're looking at the problem.


The big problem from my point of view is that when Mail hammers the Exchange server, it generates a huge number of errors (even though at the Mac's end...everything seems hunky dory). Our Exchange admins have already decided that if they see Macs coming in with Mail...they'll shut off the mail account so they don't have to deal with the server problems.



[ Reply to This | # ]
Stop Mail.app from caching too many IMAP folders
Authored by: Carphunter on Nov 02, '05 05:41:11AM

Just an update... Mail 2.05 included with 10.4.3 still hasn't addressed the problems. Server still fires off millions of errors.



[ Reply to This | # ]
Stop Mail.app from caching too many IMAP folders
Authored by: alan-trewartha on Oct 25, '05 06:43:47AM

YOU ARE TOTALLY SPOT ON. we are resisting a move to tiger with our ~100 clients until Mail can deal with IMAP/exchange accounts correctly. this IMAP scope issue is an absolute pain.

we tried the perl workaround (above) to no good effect yet (actually to a BAD effect, but that was accidental)

so thanks for the bug submission



[ Reply to This | # ]
Stop Mail.app from caching too many IMAP folders
Authored by: sjk on Oct 25, '05 07:53:36PM

I'll be reporting this, too, hopefully incrementing the duplicate counter closer to what's necessary for Apple to take action and fix it. I'm eventually migrating from Mulberry (sadly, its company recently filed for bankruptcy) and this is one of several key IMAP-related issues that need fixing before I'd seriously consider Apple Mail as a replacement. With some help from Cyrus Daboo (orĀ other equally talented, experienced IMAP expert) as a technical consultant Apple might get the half-baked implementation closer to being fully cooked.

Excluding Mulberry, Thunderbird may have the best IMAP support of any OS X mail client right now but I'd rather not use it for reasons that are important to me. Unfortunately other choices go down hill quickly. There may be hope for Qualcomm's Cocoa re-implementation of Eudora but a public beta hasn't been released yet.

E-mail is the world's most popular online service yet finding an acceptably tolerable client (it needn't be perfect) remains frustratingly elusive for me.



[ Reply to This | # ]