Good luck!
Since this is not the first time anyone has had to explain this, and
probably will not be the last, I've added the relevant information to
our FAQ:
http://growl.info/documentation/faq.php#growlmail-and-snow-leopard
They're given in the Info.plists of both Mail and the Message framework.
However, you can't be sure that a plug-in that worked with Mail 4.1
will work with Mail 4.2. Everyone who's tried it so far, and who did
the same after 10.6.1 came out, has been lucky. The very reason Apple
added this check is that they may change the way Mail works in any way
at any time. You cannot predict what will result from that.
GrowlMail is very paranoid about things in Mail changing, and will
shut itself off (as much as it can) if it detects any change. (This is
assuming you made it pass Mail's check.) But many other Mail plug-ins
are not so careful (GrowlMail wasn't, either, originally), and even we
can't predict every possible failure point.
Sometime this week, I'll turn Time Machine back on, then install
10.6.2, apply the UUID changes, and see what happens.
Run the “Uninstall GrowlMail” application on the Growl disk image.
Please post both crash logs.
Those aren't broken; they're working as intended. Apple intentionally
changes the plug-in compatibility UUIDs with every new version of Mac
OS X. While annoying, it is not a bug.
--
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=.
Thanks,
Calvin Hill
On Nov 9, 10:06 pm, Michelle Gill <michelle.lynn.g...@gmail.com>
wrote:
> Worked for several of my colleagues and myself. Also worked for two other mail plugins (DEVONThink and MailTags). Sorry, don't know what to tell you!
>
> Good luck!
>
> On Nov 9, 2009, at 10:01 PM, david toub wrote:
>
>
>
> > Unfortunately, this doesn't work for me. I added in the two strings,
> > replaced GM in the Bundles folder and restarted Mail. GM was disabled
> > again. Any ideas? Thanks.
>
> > On Nov 9, 9:39 pm, Michelle Gill <michelle.lynn.g...@gmail.com> wrote:
> >> I have Growl Mail (via Growl 1.2) working fine on 10.6.2. You have to
It always was. The problem is with GrowlMail.
> … and mail does not shift the bundle back to a disabled folder but I
> still get the message pop up when I start up Mail. Is that normal?
You have two copies of GrowlMail installed. Run the Uninstall
GrowlMail app, then install 1.2.1.
I'm going to go delete the GrowlMail Mike uploaded, since we now have
an official release that does the same thing.
There is no reason to do this hackery anymore. Use GrowlMail 1.2.1
instead: