cocoaforge

If a user installs it and THEN reads the document, it's too late. That's not acceptable.

The_Tick wrote:If a user installs it and THEN reads the document, it's too late. That's not acceptable.

True. Isn't that why those documents are often called "Read Me First"?

And one called "Known Bugs", or at least a changelog, might help too. You can't help users who don't take notice of the help you offer them; but some will, and might even contribute. Like I'm trying to, honestly. (After all, we've helped two other people figure out how to stop their problem, and they've suffered no data loss.)

Anyhow, I've downloaded the source, and will see if I can make any inroads into why GrowlMail might in some circs corrupt the Envelope Index. This is a good thing, right?

You've downloaded the branch for the new growlmail work?

We have a changelog, btw. It's on the site.

People don't read readme's. We can't assume they'll read them when potentially destructive things can happen. I don't want to take that chance. We're pulling the current GrowlMail asap.

OK: feel free to laugh.

But having browsed the source code, looking at Message+GrowlMail.m, I think the problem lies in the attempt to get the messagebody.

When there's a slew of mail I suspect that Mail is updating Envelope Index but that GrowlMail somehow interferes with its reading of the arriving messages - perhaps IMAP mail is dealt with differently from POP. (Perhaps IMAP demands more checking with the server, or the mail message remains open.)

GrowlMail doesn't touch Envelope Index, does it? (Or does it?)

The fact that after these crashes I see an Envelope Index-Journaled suggests that Mail recognises something being wrong with the original Envelope Index. Beyond this I can't go - my Obj-C just isn't up to it.

As I said, feel free to laugh.

The_Tick wrote:We have a changelog, btw. It's on the site.

I'm sorry, but you're going to have to give me the URL. I've tried every page on Growl.info and haven't found anything that calls itself a changelog.

No search either. Google can help with that - custom Google search engine limiting itself to site:growl.info. Box at the top right and bingo! I'd find the changelog.

charlesarthur wrote:

The_Tick wrote:We have a changelog, btw. It's on the site.

I'm sorry, but you're going to have to give me the URL. I've tried every page on Growl.info and haven't found anything that calls itself a changelog.

Go to growl.info and then click on Version History

The_Tick wrote:Go to growl.info and then click on Version History

/me *feels stupid*. /

OK, I'll try GrowlMail 1.1.2 and see what happens.

charlesarthur wrote:

The_Tick wrote:Go to growl.info and then click on Version History

/me *feels stupid*. /

OK, I'll try GrowlMail 1.1.2 and see what happens.

Nah, don't feel stupid man, it's different wording than what you were looking for is all.

I was able to get Growl notifications working with Mail.app, but not with GrowlMail. I was able to get it to working with AppleScript and a Mail.app rule.

I wrote up what I did to get Growl notifications working with Mail.app (and without GrowlMail) using AppleScript and a Mail.app rule here:

http://www.opbarnes.com/blog/Mac/leopar ... _nice.html

Hello,

Just to say I have crashes with Growlmail on 10.4.10, growl 1.1.2 and IMAP as well, which is all supported. Mail.app just crashes all the time.

This is extremely scary when one's mail application, which you've been using for years, suddently just crashes all the time when there are too many messages waiting. Fortunately the crashes started appearing right after growlmail was installed to it was obvious where they were coming from.

However there is no easy way to remove growlmail. You have to use the Terminal.app and the command line, manually cd to /Library. Fortunately many are experiencing this problem so a quick Google search yields the solution.

Altogether very bad. The minimum would be instructions to remove growlmail, and I would suggest removing the package altogether at the moment.

People's mail is rather important !