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

10.5: A possible fix for Mail problems after 10.5 upgrade System 10.5
When upgrading a Tiger machine to Leopard, there seems to be some circumstances that prevent the upgrade of Mail data from completing. You can recognize this condition by these symptoms:
  • Message viewer window doesn't automatically appear
  • All mailboxes are present but empty
  • Activity Viewer shows connection attempt not proceeding
The Console logs can give some clues to the cause. Sometimes this is caused by conflicting or corrupt Junk Mail settings in the com.apple.mail.plist file.

The various values have changed in some version updates to Mac OS X. For some, it's the JunkMailInfoPanelHasBeenShown attribute. For me, it was changing JunkMailBehaviorHasBeenConfigured to false. Also, removing the JunkViewerAttributes setting seemed to be necessary. These can be changed using Property List Editor (installed with XCode developer tools), or it's possible it could be done in the Terminal with these commands:
$ defaults write com.apple.mail JunkMailBehaviorHasBeenConfigured false
$ defaults write com.apple.mail JunkMailInfoPanelHasBeenShown false
$ defaults delete com.apple.mail JunkViewerAttributes
[robg adds: I haven't heard about this issue before, so I can't confirm the issue or the solution.]
    •    
  • Currently 2.00 / 5
  You rated: 1 / 5 (10 votes cast)
 
[9,584 views]  

10.5: A possible fix for Mail problems after 10.5 upgrade | 11 comments | Create New Account
Click here to return to the '10.5: A possible fix for Mail problems after 10.5 upgrade' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.5: A possible fix for Mail problems after 10.5 upgrade
Authored by: scotty321 on Jun 03, '09 08:14:16AM

Yes, Mac OS X Leopard has always had serious bugs in upgrading Mail from Tiger to Leopard, particularly when you try to manually upgrade Mail (e.g. by manually moving the Mail folder and Mail preferences from a Tiger machine to a Leopard machine). Totally annoying beyond belief.

Haven't tried the hints outlined in this article, but here are the step-by-step instructions that we've been successfully using for how to fix the problem:

1. Start by carrying over the com.apple.mail.plist file in ~/Library/Preferences on the old machine into the same location on the new machine.

2. Next, carry over the ~/Library/Mail folder from the old machine BUT PUT IT ON THE DESKTOP OF THE NEW MACHINE.

3. Launch the Mail application.

4. Mail will now ask you if you want import your messages. DO NOT HIT CONTINUE YET!!

5. Go into ~/Library and you will notice that there is a NEW Mail folder that was created. Don't try to delete this folder yet because it is in use by mail so just rename this folder Mail2.

6. Now, drag your OLD mail folder located on your desktop to your ~/Library folder.

7. Go back to the Mail application and click continue. Your messages and settings should import fine now.

8. Verify that your messages and settings imported correctly and quit Mail.

9. Navigate back to ~/Library and delete the Mail2 folder.

10. Launch the Mail application again and make sure everything functions correctly.



[ Reply to This | # ]
10.5: A possible fix for Mail problems after 10.5 upgrade
Authored by: Auricchio on Jun 03, '09 08:28:24AM

This workaround works perfectly. I have had to use it several times when upgrading clients' systems.

Technically, you can drag the old Mail folder to the trash, just don't try emptying the trash. This avoids the renaming and later deletion steps.

---
EMOJO: mojo no longer workin'



[ Reply to This | # ]
10.5: A possible fix for Mail problems after 10.5 upgrade
Authored by: osxpounder on Jun 03, '09 10:02:35AM

I've used scotty321's technique successfully to fix my broken Mail after upgrading to Leopard.

It worked for me, but it took 2, maybe 3 tries. It might not have been the total solution, but I forget now what else I tried, because my troubleshooting was desperately quick, and because I had a backup I could restore, if needed.



[ Reply to This | # ]
10.5: A possible fix for Mail problems after 10.5 upgrade
Authored by: bcometa on Jun 08, '09 10:57:16AM
Totally agree that manual mail migration 10.4-10.5 is way too troublesome. Can't wait to try this technique on next client's upgrade. Thanks for sharing!
brian cometa

[ Reply to This | # ]
10.5: A possible fix for Mail problems after 10.5 upgrade
Authored by: neknek on Jun 03, '09 08:36:52AM
Or you could just do this:

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

I'm so glad I finally found that article.

[ Reply to This | # ]
10.5: A possible fix for Mail problems after 10.5 upgrade
Authored by: DAM78 on Jun 03, '09 08:40:58AM

I can CONFIRM that the Apple Support article is a fix.

This has happened to me a few times and it takes only a moment to resolve by following the article.

It's quick and easy



[ Reply to This | # ]
10.5: A possible fix for Mail problems after 10.5 upgrade
Authored by: osxpounder on Jun 03, '09 10:11:03AM

From my experience (above), I can confirm that the Apple solution DID NOT solve the problem for either of my Macs. I had to use the steps detailed in the original hint here.



[ Reply to This | # ]
10.5: A possible fix for Mail problems after 10.5 upgrade
Authored by: jiclark on Jun 03, '09 01:04:10PM

Just to be clear, osxpounder, when you say you used the steps in "the original hint here", you mean scotty321's steps, NOT the 'defaults write' steps outlined by ppp at the top of this page, right???

And I'll add my voice to the many that have run into this issue almost every time I've upgraded a client's machine to Leopard from Tiger. I don't trust the Migration Assistant (primarily because I'm usually migrating an older PPC machine to a new Intel one, while moving to Leopard at the same time: double-whammy!), so I migrate stuff manually, and Mail chokes just about every time...



[ Reply to This | # ]
10.5: A possible fix for Mail problems after 10.5 upgrade
Authored by: osxpounder on Jun 05, '09 11:56:47AM

Thanks for asking; I did make a mistake.

I used scotty321's detailed tip, at the top of the Comments on this page. That's what I used successfully (but it took more than 1 try, because the problem seemed fixed, but recurred the next day, or a few days later, for a week or more).

I should have been more careful. It seems I scrolled up until I saw scotty's long hint, and thought I was looking at the original hint. I'm very glad you asked, and sorry for my error. Also grateful to you for checking, and to all of you for sharing knowledge here.

Because I was trying other solutions before that one worked for me, it's possible that earlier attempts contributed to the eventual solution.



[ Reply to This | # ]
10.5: A possible fix for Mail problems after 10.5 upgrade
Authored by: jiclark on Jun 07, '09 12:43:01PM

No effusive apologies necessary! ;-}

I figured that's what you meant, and just thought it worth an attempt to clarify, for others looking for a fix in the future mostly...

Odd that his fix didn't stick though, isn't it? Leopard *still* makes me a bit uneasy because of these sorts of lingering issues. Of course, there're still lingering issues with 10.4.11, so I guess I shouldn't be surprised!!

You are a valuable contributor here, oxspounder, so just keep on posting! A slip-up now and then is to be expected, especially one as trivial as this...



[ Reply to This | # ]
It always happens on Tiger->Leo migrations
Authored by: cavenewt on Jun 05, '09 12:41:55PM

I've had it happen when using Migration Assistant (I don't think it happens on a simple Tiger to Leopard upgrade.) Sometimes trashing the messagesorting.plist and/or messagerules.plist files works, but usually I have to delete the ~Library/Preferences/com.apple.mail.plist file, then reconfigure Mail for all the accounts, to fix it.

One client had called Apple first, and was preparing to send his brand new MacBook in for a system reinstall (!), when he mentioned it to me and we fixed it in 30 seconds over the phone. Impressed the client no end.



[ Reply to This | # ]