Can't Open Mail after security update 10.6.8

Question

Can't Open Mail after security update 10.6.8

I can not get the mail app to run. This is the error message I keep getting.

Did the SecUpd2012-004 update.

After the update, I had (and still have) 2 copies of mail in my application folder.

I've repaired my permissions.

Tried to got back using the time machine (that was a waste of hours).

Also, deleted the mail app (8.1) and then reinstalled the SecUpd2012-004.

Only thing I haven't done is to do the Combo 10.6.8 update.

I've noticed that other people are starting similar threads. Anybody have a solution? I've been working on it all day and no joy.

Thanks in advance.

Mac Pro, Mac OS X (10.6.8)

Posted on Sep 25, 2012 4:14 PM

Reply

Answer 1

baltwo

Level 9

62,362 points

Sep 25, 2012 4:55 PM in response to Microbe Whisperer

Install the COMBO update and then try the Sec Upd again. The Sec Upd worked w/o issues the first time. You might want to manually DL the Sec Upd.

Reply

Answer 2

Sep 25, 2012 5:57 PM in response to baltwo

Well, I thought that we might have had a solution, but no such luck.

I did the combined update - and after that I had only one Mail app in the applications folder (encouraging) - and it appeared to be the correct one by it's icon.

Thought about doing a repair permissions but didn't do it after the combined update.

After the combined update, I did the secUpd, the second mail app was there with it's generic icon again and

Needless to say, I'm back to square 1.

So, I'm thinking I've got some options here. One of my options would be to get another HD, slug it into one of the open HD slots, take out my 10.6 CD format it and then if possible use time machine to put that drive in the state where everything worked right before the update. This would seem to be the fastest, time wise way of making the issue go away.

You guys think I could / should delete the 4.6 mail app and start over with the combined update and then do a permissions repair after the update?

Reply

Answer 3

baltwo

Level 9

62,362 points

Sep 25, 2012 6:04 PM in response to Microbe Whisperer

No, I think they have serious issues with the prematurely released update. Had to get it out for the iOS6 and iPhone5 rollout whether it was ready or not. All I can suggest is to File a bug reportwith Apple.

Reply

Answer 4

WZZZ

Level 6

13,220 points

Sep 25, 2012 7:14 PM in response to Microbe Whisperer

Did you try this? See the two following posts as well.

https://discussions.apple.com/thread/4311280?answerId=19711910022#19711910022

Reply

Answer 5

Sep 25, 2012 8:09 PM in response to Microbe Whisperer

I got mine to work.

Pretty much had the same problem... my Mail app had (original) after it. Tried everything, but it finally dawned on me that the updater could not recognize the app because of the (original).

Having nothing to loose, except time. I did this:

1. Went to app folder and did 'get info' on the mail (original) app.

2. In the get info window I went to the 'Sharing & Permissions:'

3. For 'everyone' I changed it from Read Only to Read & Write

4. Then the name was no longer grayed out. So I could select it.

5. Deleted everything in the name except 'Mail'.

6. Went back to 'Everyone' and set the privilege back to 'read only'

7. Closed the get info window.

It worked. !!!!

Hope this helps someone else.

Jah

Reply

Answer 6

WZZZ

Level 6

13,220 points

Sep 25, 2012 8:17 PM in response to Microbe Whisperer

What version is showing now from GetInfo; is it the 4.6? What do you see in /Applications? Is it showing as Mail.app?

Reply

Answer 7

Sep 25, 2012 8:22 PM in response to WZZZ

Maybe I didn't make it real clear.

After I changed the name, I ran the SecUpd2012-004 (spelling)

Then restarted the machine.

4.6 🙂

Reply

Answer 8

WZZZ

Level 6

13,220 points

Sep 25, 2012 8:22 PM in response to Microbe Whisperer

Amazingly simple fix, but one more thing: who is the owner now of Mail.app? Is it system (or root from the Unix Permissions), which it should be, or is it now your user?

Reply

Answer 9

Sep 25, 2012 8:25 PM in response to WZZZ

I'm the owner....

All of those years sitting at a Mac came in handy.

The fix for apple is to have the updater software recognize file names with (original) appended to them.

When that thought hit me, I felt real comfortable in understanding why the update didn't happen.

Reply

Answer 10

WZZZ

Level 6

13,220 points

Sep 25, 2012 8:50 PM in response to Microbe Whisperer

But system/root should be the owner. That's what I was afraid of. When you renamed it using the Finder instead of through the command line/Terminal, that changed the ownership and don't know what else. Might have wrecked the Permissions entirely for all the enclosed folders and files. Could run Permissions repair to see if this fixes it.

Or get BatChmod and drag in Mail.app. This is what it should look like. Don't hit Apply to enclosed, since they may not all be the same.

Reply

Answer 11

WZZZ

Level 6

13,220 points

Sep 25, 2012 9:04 PM in response to WZZZ

What I also don't understand -- and I should emphasize that I'm not certain of this -- about your fix is the Security Update appeared to make its changes by way of the small 8.1MB Mail -- that's where the newly modified files exist-- and, since you've left those out, it's possible you may have tricked the system into getting it to work, but I don't know if you haven't entirely bypassed the security patch that was intended for Mail by doing that.

This is what the resulting Package Contents should look like. Pay attention to the Dates Modified.

Message was edited by: WZZZ

Reply

Answer 12

Sep 26, 2012 5:47 AM in response to WZZZ

i knew that after doing the SecUP2012 there was a 2nd mail app in the folder. Which was the 8mb file you are referencing. But at some point in time Occam's razor comes in to play and that is when it dawned on me to do what I did.

The new mail application was there in the folder but the software updater would not/could not recognize the old mail application, because of the name (I assume).

So, at the end of the day, it appears that I've got the right program installed and running. If it comes to past that something is wrong, I'll deal with it then, but now I'm back in business.

Reply

Answer 13

WZZZ

Level 6

13,220 points

Sep 26, 2012 5:53 AM in response to Microbe Whisperer

I do understand your frustration and the need to get Mail going again, in whatever form. But, to recapitulate, it looks like you've probably skipped the Security Update for Mail and left youself open to whatever vulnerability it was meant to patch. And, the Permissions for Mail.app are wrong -- what the consequences of that may be down the road, it's hard to tell. But I wouldn't want to leave an application in that state for either of those issues on my system.

Reply

Answer 14

Sep 26, 2012 6:07 AM in response to WZZZ

THANK YOU, WZZZ. I followed your instructions exactly, and, guess what - I HAVE MY MAIL 4.6 BACK AGAIN!! Yes, it was the Security update that messed things up. I could go into the files and see that I had not lost the actual messages. It was just that Mail could not be opened.

These forums are wonderful for Apple members.

May I now delete the small app that is in the Trash?

Many thanks again.

Reply

Answer 15

WZZZ

Level 6

13,220 points

Sep 26, 2012 6:44 AM in response to fomamac2guy

To be clear, you are referring to these instructions:

https://discussions.apple.com/thread/4355201?answerId=19760703022#19760703022

not the ones in this thread.

It's looking good, but before you empty the trash with the small Mail folder, right-click (Control-click) on Mail.app to show Package Contents, open the appropriate disclosure triangles, as shown below, and compare it. Pay attention to the Dates Modified. Contents, CodeSignature and MacOS will probably show the date you just ran the update again. Mine shows 9/21 for those; that's when I installed the update. In fact, can you post a screenshot (Cmd-Shift-4 and use the Camera icon here) showing your package contents. That would be helpful

Reply