cocoaforge

I disagree that it has nothing to do with your problem. [...] I have not idea if this is your particular problem, I was just throwing it out there from my own experiences. Okay, now I see what you're getting at. My error stems from the rather unusual way that Mail.app refers to the namespace. In th...

Anyone have a workaround/fix, or know if an older version of GrowlMail does not have this problem? I'm running an older version on my Mini which seems to behave okay for me.. I think it's the version that came with Growl 0.7.4, but the plugin doesn't report its own version number, so I'm not certain.

Do your mailboxes appear as sub boxes of your Inbox? Or are they listed "evenly" on the column The mailboxes I'm talking about are not inboxes. If it's the latter, you can find out what the MailBox Prefix is of your IMAP server and put that in for the "Mailbox path prefix" under...

I should have mentionned that "enable logging" is NOT checked in Growl's PrefPane. Hrm.. then that sounds like a bug to me. I'm just another user like you though, so I can't say with certainty that's not the intended behaviour. Hopefully someone who can say one way or the other will reply.

To log or not log is a feature of Growl itself. From the Growl prefs pane you can tell it to log to some file other than console.log if you need logging, but don't want it interfering with the rest of your system logging.

The subject says it all. Activating the "Inbox only" checkbox in the GrowlMail pane in Mail.app prefs has no effect on GrowlMail's behaviour. GrowlMail still reports new messages for all mailboxes. Mail in my IMAP accounts is separated into different mailboxes on the server by rules there,...