We don't know when the new GrowlMail will be out. Hopefully, we will
release a beta soon (I suggested this on the other thread).
== Known bugs in that build ==
- Mail complains that your bundles are outdated and disables GrowlMail
- You can't enable/disable accounts [Fixed]
- Inbox Only doesn't work [Fixed]
- GrowlMail notifies when you move messages [Fixed]
== What to do if GrowlMail doesn't notify and doesn't show up in the
Preferences ==
Download this, QUIT MAIL, and run the .command file inside:
http://growldiscuss.googlegroups.com/web/EnableMailBundles.command.zip
Then, run Mail. You should have GrowlMail back.
The Installer package is supposed to do this for you, and is supposed
to quit Mail for you, but some part of that doesn't seem to be
working for some people.
== What's this about a Leopard-compatible GrowlMail? ==
GrowlMail 1.1.2 doesn't work on Leopard. I rewrote it, and the
rewrite is compatible. However, the rewrite is buggy (but I repeat
myself), so people are having problems with it. Hence this thread.
Evan Schoenberg (a Growl developer) posted a build of the new
GrowlMail. I'll let him post the link in this thread if he wants to
continue providing it.
No. Right now, I'm punching the GrowlMail installer in the face
repeatedly; when I get it to co-operate, we'll be able to put out an
official beta, though I don't know exactly when we'll do it.
I switched off of growlmail since to me it makes
more sense to just have a widget open in dashboard than having to
leave Mail open to have meaningful growl notifications, ala you're
already to see you have new messages if Mail is already open.
The new GrowlMail has no new features over the old one.
What do you mean by “this”?
Please be more specific.
Download this, QUIT MAIL, and run the .command file inside:
http://growldiscuss.googlegroups.com/web/EnableMailBundles.command.zip
Then, drag GrowlMail.mailbundle from this folder:
Your startup disk
Library
Mail
Bundles (disabled)
to this folder:
Your startup disk
Library
Mail
Bundles
Then, launch Mail.
Did you run the .command file first?