Mail is crashing all of a sudden for me. It is crashing right after starting it.
Attached is a text file with the CrashReporter text from Console.
Attached is a text file with the CrashReporter text from Console.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Mail crashing
- Thread starter creator2456
- Start date
- Sort by reaction score
try moving the Mail plist from your user account's Preferences folder and quickly setting up your email again to see if it crashes.
if it still crashes quit Mail and place the plist back to be back where you where before.
if it still crashes quit Mail and place the plist back to be back where you where before.
Seems to do the job, but I haven't set up all my accounts yet. It's just strange that it started to crash all of a sudden, no changes at all.
Had the same problem unfortunately. I deleted EVERYTHING from the mail folder in the library and let it rebuild, seemed to work.
Yeah dude, same story here. I did NOTHING different and it began to crash out of nowhere. 10.5.5 has been a ride
Well, it's crashing again. Glad there are other ways to check my mail, but nothing as easy as just opening one App.
I have been using 10.5.5 since it was released, why start crashing Mail now?
Gonna try that.
*edit*
I think the culprit is the Letterbox.mailbundle for me. Mail seems to crash with it installed within 10 minutes, but again, it's just odd that it's doing this all of a sudden. I have used Letterbox with Leopard since the Leopard update was released almost a year ago.
I have been using 10.5.5 since it was released, why start crashing Mail now?
Gonna try that.
*edit*
I think the culprit is the Letterbox.mailbundle for me. Mail seems to crash with it installed within 10 minutes, but again, it's just odd that it's doing this all of a sudden. I have used Letterbox with Leopard since the Leopard update was released almost a year ago.
I'm having the same problem. No issues at all in Leopard until... Safari 3.2(.1). So, I think that's the culprit. Though I can't imagine why it would be.