114410 - RFE wishlist: File mail with bookmarks

Status: RESOLVED EXPIRED

(SeaMonkey :: MailNews: Message Display, enhancement)

Description

[Chris Worley]

I'd like to be able to comingle my bookmarks with references to email.  The
email would still be in it's repective folders, but I'd like to be able to
bookmark the email and file it in a bookmark folder.

Comment 1

[David :Bienvenu]

not a database issue. I agree it would be nice, but that ship has sailed. In
fact, I think we can't do this now that we don't support rdf for messages,
right, Seth? This should be wontfix, I guess.

Comment 2

[Chris Worley]

For folks who use a browser and integrated mail as their PIM, with thousands of
emails and bookmarks, better organization is always helpfull.  In my case, I'm
part of many projects, and would like to organize both the relevent web pages
and email in one spot.

It was recently said that there's no innovation in Open Source... that we're
always playing catch-up.  I'm trying to come up with some useful innovations.

Comment 3

[Boris Zbarsky [:bzbarsky]]

confirming rfe

Comment 4

[Andy Edmonds]

Can one of the commenters confirm that that it's theoretically impractical to
create a url that unique identifies a message?  I recently wrote a parse for the
junk mail filter and was dissapointed to discover that there was no easy way to
go from the filter-log entry to the mail message.

The scenario for this bug might involve changes to message-window.xul to parse
the location.search instead of window.arguments.  

Comment 5

[R.K.Aa.]

related/dup of bug 14988

Comment 6

[Robert Kaiser]

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

Comment 7

[Robert Kaiser]

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