Q: Why is mail running so slow

Also upgraded from SL to Lion, to ML, without performing one clean install. I had the file. Hmmm ...

After deleting all old Mail prefs, it was ok for some time but now again Mail sometimes moves into 70 / 80 / 90 % CPU usage and the fan is very noisy.   What is that?  Any other reasons why mails slows down so much?

You can always try this one:

http://support.apple.com/kb/PH4801

Reindexing messages didn't help and also the probelm appeared immedately after upgrading from Lion to Mountain Lion. I am now at 50-80% CPU usage, better than 100 with thre pref file mentioned above, but still disturbing.

I have the following plugins installed: Attachment Tamer, Mail Act-On, MailTags.

Well, there you are, then. Surely, third-party mail-plugins is the first thing to do away with when you troubleshoot Mail. Goes without saying.

Absolutely, goes without saying. And Mail is still eating a lot of % CPU usage. This without (and with the three plugins installed - I tested all possible variations of the three plugins installed and not installed). Basically this manifested directly after the Lion climbed the mountain and became a Mountain Lion.

Before starting Mail, start the Console.

After starting Mail, have a look at the messages in the Console and post them here.

So far in the Console messages are some private informations, like your username, replace them.

This is it:

27.08.12 09:40:29,592 SyncServer[651]: [0x7fe25040bd00] |DataManager|Warning| Client com.apple.Mail sync alert tool path /System/Library/Frameworks/Message.framework/Resources/MailSync does not exist.

It seems you have some problems with the Sync Services.

I also don't have the file mentioned in the /System-path.

You should reset the Sync Services.

This is described in the document:

http://support.apple.com/kb/TS1627

You find a description also for Mountain Lion.

simple solutions...to simple problems...you the man sberman! It worked for me and you are right it never hurts to rebuild, reset safari and trash those preferences.....etc.

I got the same problem with Mail becomes so slow in typing and receiving emails. I tried sberman's way with Rebuild function and it helped.

This is at least the 6th time I've posted on these forums for this same problem.  It seems every "expert" has a different diagnosis and a different solution.  Here's the problem.

1.  I upgraded to Mountain Lion about a year ago.

2.  Ever since then, on occasion, Mail slows down to a crawl (or slower).

3.  I log on to these forums and find some "solution" or other.  Some work, some don't, and some I don't remotely begin to understand (I'm a user, not a tech nerd - I've never used Terminal since my first Mac in 1989).

4.  A period of about three months has passed since my last major problem.  I've deleted all old (older than today's date) copies of mail.plist.  That had worked sort of in the past, but Mail doesn't seem to be creating new copies of this file anymore like it was for a long time after my ML upgrade.  Mail is now so slow that switching from one message to another takes upwards of a minute.  My fan is making audible noise that it never has before.

5.  There is only one copy of mail.plist (that I can find) in my system. 

6.  I have rebuilt my in-box - zero results.

7.  I'm getting REALLY tired of this crap.  This is Apple circa 1994, not Apple circa 2013. 

8.  Does anyone have a REAL FIX for this idiotic problem that doesn't require a computer science master's degree?

I'm dyin' here...

Okay. I have done almost everything on this thread and I still have MacMail running like a stray dog when I send a message. Can anyone else give a possible solution?

4/18/13 1:33:29.922 PM Mail[31642]: *** WARNING: -[NSImage compositeToPoint:operation:] is deprecated in MacOSX 10.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction:] instead.

This is what I get when I open Mail in command...any help?

Send Apple feedback. They won't answer, but at least will know there is a problem. If enough people send feedback, it may get the problem solved sooner.

Feedback