Closed Bug 215021 Opened 18 years ago Closed 15 years ago

Highlight threads that I have posted to in mail/news

Categories

(SeaMonkey :: MailNews: Message Display, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 11048

People

(Reporter: moreejt, Unassigned)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030703
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030703

It would be extremely helpful if Mozilla mail/news would highlight any threads
that I have been posting to.  Currently, I am involved in some lengthy threads
that can get lost and forgotten.  I have no way to distinguish new messages on a
given mailing list between postings that I am and am not involved in.  

The mail reader could look for a option (highlightmythreads) while displaying
each message.  If the message is in a thread that I have posted to then it
should be marked, highlighted or something.  

To know if I have posted to a thread:
1) each email message sent is logged to some thread index
2) or for each message being displayed, search for a message from me@my.com with
the same threading id

Should probably limit the searches to the same folder.

I have each mailing list sorted into separate folders on the server before I get
them but others might leave them all in one folder.  Either way I would not want
this feature searching all 5 thousand messages that I have on my IMAP server.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.
Summary: Feature request; highlighting threads that I have posted to in mail/news → Highlight threads that I have posted to in mail/news
I remember seeing a bug along these lines somewhere, but can't seem to find it
at the moment.

What I do is anytime I make a news post, I immediately flag the thread as
important.  (right-click context menu).   That way, I can zip through a thread
and see the red ones and if they have new posts.
But my method also allows for you to follow the thread when not in threaded view
The intent of this bug request, flagging articles posted in follow up to your
own, or articles which are of interest to your, really requires a small set of
enhancements - at minimum:

1. automatically create a filter or some other flagging machanism when you post, and
2. have the filter expire after xx days

for #1 see bug 148755 which has extensive discussion
for #2 see my bug 123375

bug 91052 goes a step further, asking for a special visual or audible notification 

I used tin newsreader (still do) where #1+#2 are taken for granted - it's just
there and it's indispensable is like bread and butter. I know many other
newsreaders have similar capability.  It's about time moz did too.
correction, bug 148755 in comment 3 above should read bug 148744
Blocks: 236849
Product: Browser → Seamonkey
Assignee: sspitzer → mail
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
I voted for this so that it might not get closed?  it's not a bug.  it's a 
feature request and should not be closed for inactivity.  The only reason to 
close would be it was implemented or it was stated that it COULD NOT/WOULD not 
be implemented. 
Status: NEW → ASSIGNED
didn't intend to assign
Status: ASSIGNED → NEW
QA Contact: esther

*** This bug has been marked as a duplicate of 11048 ***
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
No longer blocks: 236849
You need to log in before you can comment on or make changes to this bug.