Fixing GrowlMail in 10.6.4 (Mail 4.3)

Posted by Paul Kehrer on June 15, 2010 Leave a comment (77) Go to comments

Another OS X release, another broken GrowlMail bundle. I did a post just like this for 10.6.2. 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/ directory¹. If you want it available to multiple users on your system, use /Library/Mail/Bundles/.

Download patched bundle

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 "E71BD599-351A-42C5-9B63-EA5C47F7CE8E"
defaults write ~/Library/Mail/Bundles/GrowlMail.mailbundle/Contents/Info SupportedPluginCompatibilityUUIDs -array-add "B842F7D0-4D81-4DDF-A672-129CA5B32D57"

Global installation:

defaults write /Library/Mail/Bundles/GrowlMail.mailbundle/Contents/Info SupportedPluginCompatibilityUUIDs -array-add "E71BD599-351A-42C5-9B63-EA5C47F7CE8E"
defaults write /Library/Mail/Bundles/GrowlMail.mailbundle/Contents/Info SupportedPluginCompatibilityUUIDs -array-add "B842F7D0-4D81-4DDF-A672-129CA5B32D57"

~ 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 ↩

Postsbash, growlmail, mac, mail

← Tab Duplicator, A Safari 5 Extension

Updraft – A Cloud Backup and Restore Plugin For WordPress →

77 Comments.

DM June 20, 2010 at 11:31 am

Awesome. Thanks!
Dave June 20, 2010 at 7:09 pm

Great work, thanks
aepdev June 20, 2010 at 8:42 pm

Thanks for the tip. Where did you derive the UUID values
Sean June 20, 2010 at 8:48 pm

Worked great thanks
Evan June 21, 2010 at 12:44 pm

Worked great! Thanks so much. I was really missing GrownMail.
Marcus June 22, 2010 at 5:57 am

Thanks…. again!
Becky June 22, 2010 at 9:16 am

Thanks! I love GrowlMail and was really happy to see this. A quick, easy solution and Growl is up and running again.
beyond990 June 23, 2010 at 3:49 am

Thanks, you get so used to these little utils that make life so much easier. Where did you derive the UUID’s as it would be nice to fix this straight away the next time Apple make changes.

Again a big thanks Martin
Michael June 23, 2010 at 6:17 am

Hi
I can’t get this to work and I know it’s me I have moved the patched bundle to the correct directory but where do I start or configure Growl? Everytime I try to install it Mail.app moves it to the disable folder – even if the patched bundle is in the Bundles folder…
Edgy June 23, 2010 at 2:18 pm

Tried all of the above, still no growlmail.
Edgy June 23, 2010 at 2:19 pm

Tried all of above – still not working
Robert June 24, 2010 at 1:46 am

Excellent!
Edgy June 24, 2010 at 7:29 am

Finally got it to work after uninstalling Growl completely, then reinstalling, then going through the process above. Thanks!
great June 24, 2010 at 5:49 pm

great work. super easy and I needed growlmail back.
André June 26, 2010 at 1:54 pm

Bon travail. Merci. Thanks.
laurent June 30, 2010 at 1:51 am

10x so much
All Season Radial August 17, 2010 at 3:42 pm

After dropping the bundle in the directory, Mail quit as soon as it tried to use Growl. Removing the bundle from the directory allowed Mail to work again. Weird.
David August 27, 2010 at 12:21 pm

Thanks for making this available.

Two items:

1. I don’t seem to have a /Library/Mail …is that a problem?

2. Does the entire downloaded folder go into ~/Library/Mail/Bundles/?

or???