10.6.4 breaks GrowlMail compatibility

[Christopher Forsythe]

Folks,

As some of you are learning, 10.6.4 updates Apple's email client, Mail. As such, GrowlMail no longer functions with it.

We are aware of this, and are currently working through testing to ensure that GrowlMail does not need to change due to the changes in Apple Mail in 10.6.4.

Please be patient as we work through this update.

Chris

[Wahoo Charley]

This was to be expected, but can you approximate a turnaround time on
working through the update so we'll know about when to check back?

TiA,

BB

[codeman38]

On Jun 15, 5:19 pm, Christopher Forsythe <ch...@growl.info> wrote:

> Folks,
>
> As some of you are learning, 10.6.4 updates Apple's email client, Mail. As
> such, GrowlMail no longer functions with it.
>
> We are aware of this, and are currently working through testing to ensure
> that GrowlMail does not need to change due to the changes in Apple Mail in
> 10.6.4.

For those who want to try to fix this yourselves, the following seems
to fix it:

1. Go to ~/Library/Mail/Bundles (Disabled)/Growl Mail.mailbundle/
Contents.
2. Open Info.plist.
3. Add the following two items under
SupportedPluginCompatibilityUUIDs:
B842F7D0-4D81-4DDF-A672-129CA5B32D57
E71BD599-351A-42C5-9B63-EA5C47F7CE8E
4. Move Growl Mail.mailbundle back to the Bundles folder.

For the curious, those are the UUIDs for the 10.6.4 versions of
Mail.app and Message.framework, respectively.

Cody / code...@gmail.com

[codeman38]

On Jun 15, 8:32 pm, codeman38 <codema...@gmail.com> wrote:
> For those who want to try to fix this yourselves, the following seems
> to fix it:

Just as a disclaimer - I'm not sure if this version of GrowlMail is
entirely compatible. But it *seems* to work just from some preliminary
testing with those two keys added to the plist, at least for those of
you who are OK with testing beta-quality stuff. :)

Cody / code...@gmail.com

[zaxcom]

I tried updating the plist file, but it did not work. Mail still says
unsupported.

[Chris Forsythe]

You'll need to wait for us to put out an update then.

On Jun 15, 2010, at 7:53 PM, zaxcom <ellio...@gmail.com> wrote:

> I tried updating the plist file, but it did not work. Mail still says
> unsupported.
>

> --
> You received this message because you are subscribed to the Google
> Groups "Growl Discuss" group.
> To post to this group, send email to growld...@googlegroups.com.
> To unsubscribe from this group, send email to growldiscuss...@googlegroups.com
> .
> For more options, visit this group at http://groups.google.com/group/growldiscuss?hl=en
> .
>

[Chris Forsythe]

We don't publish release dates.

On Jun 15, 2010, at 6:59 PM, Wahoo Charley <bartbar...@gmail.com>
wrote:

[Wahoo Charley]

I didn't think I asked for a release date, just an approximation.
Would it be days, weeks, months?

Certainly didn't mean to POTP.

On Jun 15, 9:05 pm, Chris Forsythe <ch...@growl.info> wrote:
> We don't publish release dates.
>

> On Jun 15, 2010, at 6:59 PM, Wahoo Charley <bartbartholo...@gmail.com>  

[Wahoo Charley]

FWIW -

The temp fix works as advertised. Just remember to insert both UUIDs
between the <string></string> attributes in the correct element.

[BL420]

Make sure you have no leading or trailing whitespace in the <string></
string>, that was my problem when it didn't work for me the first
time- it looked like <string>B842F7D0-4D81-4DDF-A672-129CA5B32D57 </
string> and didn't work.

[Peter Hosey]

On Jun 15, 2010, at 18:13:16, Wahoo Charley wrote:
> Would it be days, weeks, months?

Yes, one of those.

It depends entirely on whether GrowlMail will work with no changes—that is, only the UUIDs—or requires fixes to work with the new code. The latter case leads us into a beta series, in which we'll also want to make sure we didn't break GrowlMail's compatibility with 10.6.3.

As long as we don't know how much work will be required to make GrowlMail 1.2.2 compatible with 10.6.4, we cannot predict how long that work will take.

[Peter Hosey]

On Jun 15, 2010, at 23:57:20, gs-dk wrote:
> Maybe a very stupid question.....but how do you open the "info.plist"?

You would have to open it in a text editor or a property-list editor.

> … do I then have to put the two sentences below into the script.

They are not sentences, and it is not a script. It is an XML document, and you would need to add the XML elements to it within the correct parent element.

Or you could wait for 1.2.2. That's easier.

> It's strange we have to go thru this every time the OS is updated.

No, it isn't. It happens because of measures Apple added to Mail under Snow Leopard:

http://growl.info/documentation/growlmail.php#growlmail-and-snow-leopard

[Piotr Wojciechowski]

Works well - thx

> Cody / codema...@gmail.com

[Piotr Wojciechowski]

Thx - works well

On 16 Cze, 02:32, codeman38 <codema...@gmail.com> wrote:

> Cody / codema...@gmail.com

[Brinky]

Thx for the Quick fix!

Works just fine, but as mentioned before, make sure not to add any
spaces (used property-list editor at first, in which it was a little
harder to see a space was also pasted in...)


Grtz

[gs-dk]

PERFECT!

[Friedrich]

hello -
problem here is that mail doesn't say anymore that it is not
compatible. the growl mail bundle stays in the folder also. BUT, growl
just doesn't work ;-/
maybe i am pasting the fix at the wrong place? here is what i did:

<?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.1</string>
<key>CFBundleSignature</key>
<string>emal</string>
<key>CFBundleVersion</key>
<string>1.2.1</string>
<key>NSPrincipalClass</key>
<string>GrowlMail</string>
<key>SupportedPluginCompatibilityUUIDs</key>
<array>
<string>B842F7D0-4D81-4DDF-A672-129CA5B32D57</string>
<string>E71BD599-351A-42C5-9B63-EA5C47F7CE8E</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>
</array>
</dict>
</plist>


where should it go do work?
thanks in advance!
Friedrich

[Peter Hosey]

On Jun 16, 2010, at 06:19:17, Friedrich wrote:
> the growl mail bundle stays in the folder also. BUT, growl just doesn't work ;-/

Growl doesn't, or GrowlMail doesn't?

Have you tried any other applications that support Growl?

What folder is GrowlMail staying in?

[Harry Flaxman]

Using Apple's plist editor, which should open when you double click the .plist file, it worked fine for me.

Are you manually editing, or using the editor app?

Harry

On Jun 16, 2010, at 9:19 AM, Friedrich wrote:

> hello -
> problem here is that mail doesn't say anymore that it is not
> compatible. the growl mail bundle stays in the folder also. BUT, growl
> just doesn't work ;-/
> maybe i am pasting the fix at the wrong place? here is what i did:

______________________________

Harry Flaxman 

Model Name: iMac
Model Identifier: iMac7,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2 GHz
Number Of Processors: 1
Total Number Of Cores: 2
Memory: 4 GB

OSX 10.6.4

[Friedrich]

thanks for the fast answers guys!-,

Peter:
-growl mail doesn't work, the growly rest of them seems to work just
fine.
-i put it back into the bundles folder as codeman38 has said:
~/Library/Mail/Bundles/GrowlMail.mailbundle/Contents

Harry:
-i used the editor app, i don't even know what "manual editing" means,
i'm not a coder.
-i just added the 2 codeman38 lines above the already existing lines.
when that didn't work, i killed the already existing lines and only
used the 2 codeman38 lines. same result…

[Peter Hosey]

On Jun 16, 2010, at 06:36:09, Friedrich wrote:
> -growl mail doesn't work, the growly rest of them seems to work just fine.
> -i put it back into the bundles folder as codeman38 has said:
> ~/Library/Mail/Bundles/GrowlMail.mailbundle/Contents

Does GrowlMail show up in Mail's Preferences window?

http://growl.info/documentation/growlmail.php#growlmail-doesnt-work

[Friedrich]

Peter, that solved it!
checked my mail prefs again, i had the "ony notify when mail.app in in
the background" ON! BUT, was staring at my mail app IN FRONT of me to
see if it works. pure user stupidity!
so yeah, the fix does work,great work codeman38!!!
Peter, Harry, thanks again, really appreciate!
best friedrich

[attheshow]

Subscribing

[Worldquester]

On Jun 16, 2:00 pm, Peter Hosey <p...@growl.info> wrote:
> On Jun 15, 2010, at 23:57:20, gs-dk wrote:
>
> > Maybe a very stupid question.....but how do you open the "info.plist"?
>
> You would have to open it in a text editor or a property-list editor.

Right... I had never done this before and did it successfully using
Apple's TextEdit. Thanks for the info, everyone.

[Fred]

I edited it with Emacs and it worked for me once I removed a stray
space in the string that slipped in... Thanks!

On Jun 17, 5:16 am, Worldquester <bangkoktraderedi...@gmail.com>
wrote:

[K 8GB]

Codeman and to those at Growl, thank you so much for this fix. It took
me all of 1 minute to follow the very clear directions to fix this
issue. Small item in this world filled with major problems, but Growl
Mail is one of those tools that make life easier for me during the
workday. Thanks again guys for taking the time to help. Rick

> Cody / codema...@gmail.com

[Jim Roberts]

Thanks codeman38

Worked like a charm. Off subj topic, can you recommend a good book on
OS X inner workings?

exjimmyr

On Jun 15, 8:32 pm, codeman38 <codema...@gmail.com> wrote:

> For those who want to try to fix this yourselves, the following seems
> to fix it:
>
> 1. Go to ~/Library/Mail/Bundles (Disabled)/Growl Mail.mailbundle/
> Contents.
> 2. Open Info.plist.
> 3. Add the following two items under
> SupportedPluginCompatibilityUUIDs:
>      B842F7D0-4D81-4DDF-A672-129CA5B32D57
>      E71BD599-351A-42C5-9B63-EA5C47F7CE8E
> 4. Move Growl Mail.mailbundle back to the Bundles folder.
>
> For the curious, those are the UUIDs for the 10.6.4 versions of
> Mail.app and Message.framework, respectively.
>

> Cody / codema...@gmail.com

[Peter Hosey]

On Jun 20, 2010, at 17:38:09, Jim Roberts wrote:
> Off subj topic, can you recommend a good book on OS X inner workings?

“Mac OS X Internals” by Amit Singh. It's old now, as it was current when Tiger had just come out, but still mostly accurate. It's in the class of books that I learn something from any time I open it.

http://osxbook.com/

[ShadowSwan]

Have pasted exactly this into the plist at Macintosh HD/Library/Mail/
Bundles/GrowlMail.mailbundle/Contents/info.plist and mail still says
Mail has disabled the following plug-ins:

GrowlMail

Contact the makers of these plug-ins for versions that are compatible
with Mail 4.3 and Message 4.3.

Why?

P

[Marco]

the fix works for me (and for many others). not sure why it does not
work for some people. what have you used to edit the .plist file?
apple's plist editor is best

[i.aten...@gmail.com]

There shouldn’t be a GrowlMail.bundle in the /Library off of your hard disk any more; new versions of GrowlMail are only installed per user in your Home Library folder.
Check in ~/Library/Mail/Bundles for a GrowlMail in there.

[gmanfan]

I do not see "SupportedPluginCompatibilityUUIDs". Below is what I have
available when editing with PlistEdit. Any thoughts?

File location: /Users/##/Documents/Mail\ Backup/Bundles\ \(Disabled\)/
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>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.1.4</string>

<key>CFBundleSignature</key>
<string>emal</string>
<key>CFBundleVersion</key>

<string>1.1.4</string>

<key>NSPrincipalClass</key>
<string>GrowlMail</string>

</dict>
</plist>
==

On Jun 15, 5:32 pm, codeman38 <codema...@gmail.com> wrote:
> On Jun 15, 5:19 pm, Christopher Forsythe <ch...@growl.info> wrote:
>
> > Folks,
>
> > As some of you are learning, 10.6.4 updates Apple's email client, Mail. As
> > such, GrowlMail no longer functions with it.
>
> > We are aware of this, and are currently working through testing to ensure
> > that GrowlMail does not need to change due to the changes in Apple Mail in
> > 10.6.4.
>

[i.aten...@gmail.com]

You have an old version of growlmail (1.1.4, as seen in the CFBundleVersion key)
Upgrade your growlmail to the latest version 1.2.1 first (downloadable from here: http://growl.info/growlmail/), or you may end up in all sorts of trouble, as your growlmail bundle itself as it is right now actually won’t be compatible! (Not that the latest is officially verified to be at this point in time, hence why there hasn’t been an official release and also why these compatibility numbers exist in fact…)

[Peter Hosey]

On Jun 23, 2010, at 11:29:19, i.aten...@gmail.com wrote:
> Not that the latest is officially verified to be at this point in time, hence why there hasn’t been an official release and also why these compatibility numbers exist in fact…

To clarify, the compatibility UUIDs are required by Mail to indicate that a bundle (such as GrowlMail) is compatible with it. Each version of GrowlMail includes the UUIDs for all of the versions of Mail and the Message framework that we know it is compatible with. GrowlMail 1.2.1, for example, includes the UUIDs required by Mac OS X 10.6.0 through 10.6.3. 1.2.2 will include the UUIDs for 10.6.4 as well.

[Myles Taylor]

The fix worked great for me. Thanks.