Fixing GrowlMail in 10.6.5 (Mail 4.4)

Update: Fix for 10.6.7 and Mail 4.5

Another OS X release (beta as of this posting), another broken GrowlMail bundle. I did a post just like this for 10.6.2 (and 10.6.4). Check it out if you want more background on why this occurs.

Easy Fix

Download a pre-patched GrowlMail.bundle and drop it in your ~/Library/Mail/Bundles/ directory1. If you want it available to multiple users on your system, use /Library/Mail/Bundles/.

Download GrowlMail 10.6.5 mailbundle

If you use this method you’re all set; no need to use the command line solution below.

Add New UUIDs to SupportedPluginCompatibilityUUIDs

If you have already had your plugins disabled by opening Mail.app you’ll need to look in ~/Library/Mail (or /Library/Mail if you installed globally) and move the files back to the active bundles directory. They’ll typically be in Bundles (Disabled), so quit Mail, find them, and move them back into the proper directory.

If you have a local installation:

defaults write ~/Library/Mail/Bundles/GrowlMail.mailbundle/Contents/Info SupportedPluginCompatibilityUUIDs -array-add "857A142A-AB81-4D99-BECC-D1B55A86D94E"
defaults write ~/Library/Mail/Bundles/GrowlMail.mailbundle/Contents/Info SupportedPluginCompatibilityUUIDs -array-add "BDD81F4D-6881-4A8D-94A7-E67410089EEB"

Global installation:

defaults write /Library/Mail/Bundles/GrowlMail.mailbundle/Contents/Info SupportedPluginCompatibilityUUIDs -array-add "857A142A-AB81-4D99-BECC-D1B55A86D94E"
defaults write /Library/Mail/Bundles/GrowlMail.mailbundle/Contents/Info SupportedPluginCompatibilityUUIDs -array-add "BDD81F4D-6881-4A8D-94A7-E67410089EEB"
  1. ~ means your home directory if you’re unfamiliar with the syntax. You can click the home icon on your Finder sidebar if you’re still confused
Leave a comment ?

73 Comments.

  1. Oh, muchas gracias. :mrgreen:

  2. I’ve tried everything and it won’t work. I trid uninstalling growl, quitting mail, deleting the bundles(disabled) folder, reinstalling all of growl/growlmail, downloading the package. Running the package by going into the mailbundle MacOS folder and running the terminal. Then opening mail. Nothing. I noticed when I run terminal there is an error message something like: binary file cannot be executed. Is that the problem? Also I do not have a directory folder in the bundles folder. What else can possible be going wrong (I don’t know anything about programming)? I’ve been at this for about an hour. I’d use the other method but I can’tfind info.plist.

  3. Worked great, thanks alot for the fix!

  4. thanks for this!

  5. Many thanks! Works fine!

  6. Thanks!

  7. Thanks! I’ve been missing this!

  8. Thank U! Works perfect fo me!

  9. thank you very much for the tip and the download – it worked, yes!

  10. thnx again for the working fix!

  11. Mac Update 10.6.5 Borked « Threat Researcher | Life Blog - pingback on December 10, 2010 at 10:22 pm
  12. Thank you very much, Paul.

  13. Thank you SO much, finally something that worked. :)

  14. Great solution, thanks a lot!

  15. ive tried several times and it still deactivates when starting mail app.

    Help! :cry:

  16. Thanks, it really worked. @thomas: I removed the installed version and replaced it with the downloaded version. After that I restarted my Macbook. (Just to be on the save side.) :grin:

  17. Thanks for the post, you saved me a bunch of irritating work.

  18. Hi I didn’t see a bundl;es folder in library/mail. icreated a bundles folder, placed he patch in it and still have the problem.

    Any sugestions ? thanks so much.

  19. Im on 10.6.6. I have tried above method, but get error message that it is not compatible with mail 4.4 and message 4.4.1
    Is there a new update already?
    Thanks

  20. @Ben: Thanks so much for the script! I’d spent half an hour messing around with the bundle and I tried everything other people suggested in the comments, but nothing worked.

Leave a Comment


NOTE - You can use these HTML tags and attributes:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> <pre lang="" line="" escaped="" highlight="">