Comment 59 for bug 849416

I'd just like to put in a vote for this bug: I have messages that come from colleagues using WebEx and they are all multipart/alternative with the last alternative being text/calendar. Stupid. The icing on the cake is that the last part is base64 encoded, so even looking at the message source (which I'm totally willing to do) won't reveal the source of the message invite. Did I mention that WebEx doesn't put the date and time of the meeting into the text portion of the message? So I get these meeting invites all the time that say "come to my meeting" and I have absolutely no idea when the meeting is going to be. Stupid. Not tb's fault - to be sure - but insanely frustrating nonetheless.

I read the long and nasty saga of bug 674473 and I certainly wouldn't want to repeat that here. Jim, thanks for taking on the responsibility for both bug 674473 and for taking a swing at this one.

Jim: if your fix only works 5% of the time, would you feel comfortable releasing it so at least 5% of the time I can read these messages? Or is the other 95% such a horrible failure that it's worse than the current behavior?

I'm happy to provide raw material for test case email messages if that would be helpful.

Thanks to everyone on the tb team for years of great work: I've been using tb since before it had a name and have always been very happy with it. Keep up the great work!