In our organisation I see the following: Someone created some software, and someone else sends his comments on the software via mail to the author. The author prints the mail, takes a marker, and marks all important things in yellow, and things he has taken care of with a cross. This paper waste happens in a lot of organisation. Wouldn't it be nice if the mail client could facilitate this? Much like the 'label' feature in Mail/News, to label an entire mail, it would be nice to be able to mark certain lines or words in the text. If you read over the mail again, you immediately see your markings. This is a feature I haven't seen in any mailclient, and would in my opinion be a cool feature for Mozilla.
If I understand this feature request, you want the ability to hilite pieces of text like with a hilite marker? If so, you might want to go to Composer and enable css editing and see if you like the hiliting functionality there and see if that is what you want.
Almost. But I didn't mean the composing of messages, but in messages I've received. To explain a bit further: I run an open source project (http://www.achievo.org), and every now and then I receive mails from people with a list of features they want added, or bugs they need fixed. It would be nice if I could read the mail and then mark the parts of the message that I find important. The features that I'm going to implement etc. Often I print the message and highlight the points I've fixed with a marker. Would be nice if that could be done in the app itself: I like paperless offices :).
If this bug gets through, an additional feature could be that you could also mark part of the mail as junk, to more selectively train the junkfilter. This would also solve the problem described in bug 181953.
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago. Because of this, we're resolving the bug as EXPIRED. If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component. Query tag for this change: EXPIRED-20100420