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"
- ~ 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 ↩
This worked perfectly after 10.6.5 just borked my Growlmail… thanks a bunch!
Yup! Saved us again from 10.6.5! Downloaded bundle worked without a hitch. Thanks.
Thanks, the bundle worked perfectly
Worked a charm, thanks!
This works great! Thanks a lot!
Worked perfectly! Thanks!
Also works for MailTags. Cheers!
It didn’t work writing the new UUIDs, but replacing the Contents folder worked. Thanks!
thx everything now works again
Thank you!
working fine also with Letterbox!
defaults write ~/Library/Mail/Bundles/Letterbox.mailbundle/Contents/Info SupportedPluginCompatibilityUUIDs -array-add "857A142A-AB81-4D99-BECC-D1B55A86D94E"
defaults write ~/Library/Mail/Bundles/Letterbox.mailbundle/Contents/Info SupportedPluginCompatibilityUUIDs -array-add "BDD81F4D-6881-4A8D-94A7-E67410089EEB"
Thanks a lot!
Thanks ! Very userfull
thank you so much !
works great..thanks!
thanks a lot
f*ing updates always break growl 
…and you saved our bacon once again. thanks.
Thanks for the gift of your knowledge to the community. You should get a medal, “Update Upset Preventer.”
Seems like it is not working for me.
I am running the new OS X 10.6.5 with Mail 4.4. I had GrowlMail under ~/Library/Mail/Bundles (Disabled) folder.
I dropped the patch you mention above. But as soon as I started Mail, it showed me the warning message that GrowlMail has been disabled.
Next, I downloaded a fresh copy of GrowlMail 1.2.2 and installed it. Opened mail and obviously the package was moved into the disabled folder. Next, I copied the bundle back to it correct location and deleted the disabled folder. Then I ran the commands via the Terminal. Started Mail and again the same error message and I see the app moved to the disable folder.
Am I missing something?
Please ignore the above comment… Its working now. I was not using the correct UUID. Now I manually editied the Info.plit file and it worked like a charm.
Cheers…
This worked like a charm…Thanks a “bundle.”
I also used the terminal UUID command with my OmniFocus bundle name substituted for growlmail and got it working too.
You’re awesome.
Hi: Thanks for this help. It works perfectly.
wonderful! thanks a lot!
Thanks!
Brilliant thanks Paul
Thank you sir!
Worked great after using Terminal
Where did you get the 2nd UUID and what is the latter one good for?
$ grep -E “857A142A|BDD81F4D” /Applications/Mail.app/Contents/Info.plist
BDD81F4D-6881-4A8D-94A7-E67410089EEB
$ grep -E “857A142A|BDD81F4D” GrowlMail.mailbundle/Contents/Info.plist
BDD81F4D-6881-4A8D-94A7-E67410089EEB
857A142A-AB81-4D99-BECC-D1B55A86D94E
And of course, thanks a lot for this post
Those who can read have a clear advantage
These UUIDs can be found in /Applications/Mail.app/Contents/Info.plist and /System/Library/Frameworks/Message.framework/Resources/Info.plist for when they inevitably change again.
Works!! Thanx a lot!!
works perfectly — thank you very much!
I got tired of this, so I wrote a dinky script to automate it. Assuming that the API doesn’t change and the current version of GrowlMail actually does still work, this will fix it for you. BY MAGICS!
http://lug.wsu.edu/node/2542
Works great and super easy to put in. Wow thank you for the consistent patches. If any of you cannot get it to work and you are doing just as the directions say:
1) Look around the entire ~Library/Mail/ directory for any additional Bundle(reject) folders that will contain your other attempts as well.
2) If it Still doesn’t work, (this was my case), it was because there was an even NEWER PATCH out.
Great work, again, thanks a lot.
Thank you again for your quick action on this. I’ve come to love growlmail!
The downloaded bundle worked great. Thanks.
Worked like a charm, thanks!
Ok, I’m baffled. Didn’t discover the problem until I loaded mail, and promptly got the “disabled” prompt. Dropped the fixed bundle in “bundles”, restarted mail. Growlmail still not working. Quit mail, ran the two commands above, restarted mail. Promptly got the “disabled” message again. Grrr. What’s going on?
Ok, that was exceedingly painful. It turned out there were multiple disabled bundle folders. What was required was to delete all of those, delete any existing growlmail bundles, re-install growlmail, and then replace the resulting growlmail bundle file with the fixed one (all of this to be done while mail.app was shut down). God, this is a pain in the ass – I wish we didn’t have to go through this every time (to be clear – this complaint is directed at Apple vice the growlmail folks or anyone here). At least it’s working again.
Worked perfectly. Got tired of waiting for the folks at Growl to patch this, so I did a search & found this site.
Outstanding & Thank You!
@Sean Peters, my script would have handled that for you. Just sayin.
es geht alles nicht!!!
Thanks much! This worked perfectly
Thanks for this.
Thank you so much, once again….
)