Fixing GrowlMail with Mac OS X 10.6.7 and Mail 4.5

thank you, it works…

Paul

Thanks it works.

Eroan

Thanks, it works for me too.

Chris

Many thanks for this – much appreciated!

Joe

Thursday, March 24, 2011

Nice one!

Jeanette

Thursday, March 24, 2011

Worked perfectly! Thanks a bunch!

Jami

Can you translate this (exact location of where to put the two lines) for people (like me!) who don’t know computer language? In other words, exactly where should I put these lines/where are the boundaries for the arrays? THANKS!

Yeri Tiete

Did you find the correct directory ?

This is what my file looks like (~/Library/Mail/Bundles/GrowlMail.mailbundle/Contents/Info.plist):

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>CFBundleDevelopmentRegion</key>
	<string>English</string>
	<key>CFBundleExecutable</key>
	<string>GrowlMail</string>
	<key>CFBundleIconFile</key>
	<string>GrowlMail.icns</string>
	<key>CFBundleIdentifier</key>
	<string>com.growl.GrowlMail</string>
	<key>CFBundleInfoDictionaryVersion</key>
	<string>6.0</string>
	<key>CFBundlePackageType</key>
	<string>BNDL</string>
	<key>CFBundleShortVersionString</key>
	<string>1.2.3</string>
	<key>CFBundleSignature</key>
	<string>emal</string>
	<key>CFBundleVersion</key>
	<string>1.2.3</string>
	<key>NSPrincipalClass</key>
	<string>GrowlMail</string>
	<key>SupportedPluginCompatibilityUUIDs</key>
	<array>
		<string>BDD81F4D-6881-4A8D-94A7-E67410089EEB</string>
		<string>857A142A-AB81-4D99-BECC-D1B55A86D94E</string>
		<string>B3F3FC72-315D-4323-BE85-7AB76090224D</string>
		<string>225E0A48-2CDB-44A6-8D99-A9BB8AF6BA04</string>
		<string>99BB3782-6C16-4C6F-B910-25ED1C1CB38B</string>
		<string>2610F061-32C6-4C6B-B90A-7A3102F9B9C8</string>
		<string>2F0CF6F9-35BA-4812-9CB2-155C0FDB9B0F</string>
		<string>0CB5F2A0-A173-4809-86E3-9317261F1745</string>
		<string>B842F7D0-4D81-4DDF-A672-129CA5B32D57</string>
		<string>E71BD599-351A-42C5-9B63-EA5C47F7CE8E</string>
		<string>9049EF7D-5873-4F54-A447-51D722009310</string>
		<string>1C58722D-AFBD-464E-81BB-0E05C108BE06</string>
	</array>
</dict>
</plist>

So just add the red part between the array-part.

You can open the .plist file with something like TextEdit.

jean

Worked fine !!

But one question : You wrote :
“These UUIDs can be found in these two files (they get updated every Mac OS X update, and thus break plugins each time):”

What we should do with those files ?

Thxs.

Yeri Tiete

Nothing, that’s just how you get the UUID’s (next time Mac OS X updates, for example).

But now you can ignore it (as I provided you with the correct UUIDs in my first post).

James Hobson

Saturday, March 26, 2011

Cool – these new UUIDs fixed both growl and letterbox extensions for mail 4.5.
Added the strings to both info.plist files.
Thanks

Jami

Saturday, March 26, 2011

Yeri, thanks. Mine didn’t look like that (it was all in paragraph form, so hard to decipher). I’ll check again. Thank you.

Yeri Tiete

Saturday, March 26, 2011

You probably need to open it with a different text editor. Try Fraise.

Rob

Monday, March 28, 2011

Thank you!!! I can’t live without GrowlMail.

Wednesday, March 30, 2011

Yeri Tiete

Are you sure GrowlMail is configured correctly ? You can see it’s loaded in preferences?

Check the settings:

Wednesday, March 30, 2011

Russell

Thanks for the info – having applied these changes to the local library I still recieved the warning that Mail was disabling GrowlMail – applying the changes to the global library the warning goes away and it reports that GrowlMail is OK – but still no Growl notifications on mail delivery – arggh – it is so useful.

Any ideas?

Is OSX finally going the way of microsoft ?

mail 4.5 (1084)
osx 10.6.7

Arão

Monday, April 4, 2011

The content of the Info.plist file in my folder is the following:

bplist00Û

_CFBundleShortVersionString_CFBundleIdentifier_!SupportedPluginCompatibilityUUIDs_CFBundleIconFile_CFBundleSignature_CFBundleInfoDictionaryVersion_CFBundleDevelopmentRegion_CFBundleExecutable_CFBundlePackageType_CFBundleVersion_NSPrincipalClassU1.2.1_com.growl.GrowlMailª_$B3F3FC72-315D-4323-BE85-7AB76090224D_$225E0A48-2CDB-44A6-8D99-A9BB8AF6BA04_$99BB3782-6C16-4C6F-B910-25ED1C1CB38B_$2610F061-32C6-4C6B-B90A-7A3102F9B9C8_$2F0CF6F9-35BA-4812-9CB2-155C0FDB9B0F_$0CB5F2A0-A173-4809-86E3-9317261F1745_$E71BD599-351A-42C5-9B63-EA5C47F7CE8E_$B842F7D0-4D81-4DDF-A672-129CA5B32D57_$857A142A-AB81-4D99-BECC-D1B55A86D94E_$BDD81F4D-6881-4A8D-94A7-E67410089EEB^GrowlMail.icnsTemalS6.0WEnglishYGrowlMailTBNDL<Qu¼Øí(.DOvÄë9`®Õäéíõÿ

Not quite the same as mentioned here. I've opened it with Fraise and with TextEditor and it always looks the same. How shall I make the changes?

Yeri Tiete

Monday, April 4, 2011

The XML tags are either hidden or removed. Probably removed if you opened it with Fraise.

I’d suggest reinstalling GrowlMail first, and then reopening the file with Fraise (not TextEdit). This should solve your problem.

Carol R.

Thursday, April 14, 2011

This fix has now worked for me twice with new Apple updates in the past few months, latest was yesterday 4/13/11/ THANK YOU!! I tried editing the plist ~/Library/Mail/Bundles/GrowlMail.mailbundle/Contents/ But even though I fixed the permissions for this file, it would not let me save the changes (i.e., adding the two lines you provided). However, when I added the two lines to the other plist, found in the first location you gave, ~/Library/Mail/Bundles/GrowlMail.mailbundle/Contents/ , it did allow the plist to be saved (was open in TextEdit). Sort of puzzling that even with correct permissions, one plist would allow changes and the other plist would not. In any case, changing one of them seems to be sufficient for GrowlMail to work with the new updates, but I thought based on the above procedure that you gave, that I needed to add the two lines to BOTH plists. Maybe one is enough. Now it’s working, as another poster said, I can’t live without GrowlMail! Love it! Thank you!

Allan W.

Tuesday, May 31, 2011

Well, I just got a new iMac (i5) and I made the changes suggested to the ~/…/plist. Before making them, the bundle was moved to disabled each time Mail was started. Now it is not moved and everything functions just fine except at Mail startup it tells me that Growlmail is incompatible and has been disabled, which it has not as it continues to work once Mail gets going. The error message is annoying, however, as it prevents mail from going on with startup until it is dismissed.
I have also applied the changed to the System Library bundles file to no avail.

Any help? Thanks!

Yeri Tiete

Tuesday, May 31, 2011

Tried reinstalling the whole plugin? And delete all old files.

Might help.

Allan W.

Wednesday, June 1, 2011

Is there anything else besides the files in ~Library/Mail/GrowlMail.mailbundle? If there are no other files, I tried that and it continues with the error message, which is apparently in error itself as Growlmail continues to operate as advertised after startup.

Yeri Tiete

Wednesday, June 1, 2011

No, I don’t think so. Tried the uninstall option from the GrowlMail installer? I believe there should be an uninstaller.

And be sure the UUIDs are entirely correct ?

Not really sure what might be causing this issue.

Allan W.

Wednesday, June 1, 2011

Bingo! Thanks for the help. I had thought to look for the Uninstaller, but looked in Finder list format and missed it because of file name truncation. You got mew to look more carefully and found it.

Yeri Tiete

Thursday, June 2, 2011

cool 🙂 hope it’s fixed then