Closed Bug 268453 Opened 20 years ago Closed 19 years ago

Replying to Rootsweb digests replies to whole digest not individual messages

Categories

(Thunderbird :: Message Compose Window, defect)

x86
Windows 98
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 204350

People

(Reporter: jon, Assigned: mscott)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Win98; rv:1.7.3) Gecko/20041001 Firefox/0.10.1
Build Identifier: Thunderbird version 0.9 (20041103)

I read mail digests from Rootsweb. When I try to reply to an individual message
in the digest Thunderbird replies to the whole digest, not the individual
author. This function works fine in Turnpike, my previous mail reader.

Reproducible: Always
Steps to Reproduce:
1. Select a digest message
2. Right click, select reply
3.

Actual Results:  
A message is composed to the digest source address, not the author of the
imdividual message.

Expected Results:  
Composed a reply to the author of the message

Default theme
I just wanted to add a feature request for this, there seems to be no proper
support for digest messages. Each digest message does show up as an attachement
and you can open it and reply to it, but it is very hard (close to impossible)
to open the right message if there is a long list.

Some specific navigation buttons for digest messages would be great (Next/Previous).

Marius
I would also very much like to get this feature in.
- Easily navigate digests (open and view individual messages without having to
reference a meaningless number).
- Reply to individual messages within a digest.

Pegasus mail does both of these quite easily.

It makes it very difficult to be a member of various open source project's
mailing lists without this feature.
A digest appears in Thunderbird with each message as an attachment in a box at
the foot of the page. Clicking on the attachment launches a new page with only
the one message in it, but the reply button greyed out. Is the fix as simple as
enabling this greyed out button?
Does anything happen when you report a bug, or is it just like **** in the wind?
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/
This is still a highly desired feature request. Quit sending stupid automated
messages to this database and get a developer to read the actual feature request.

We want to be able to reply to individual messages within a *digest*. Right now
you can only reply to the entire digest message which is incredibly stupid.
There are other free email programs that have this feature (Pegasus Mail).
The capability to reply to a  message/rfc822  attachment (as is typical 
for digests sent as multipart) has been added to the trunk (TB 1.6/2.0 and Seamonkey 1.8.1/1.9).

*** This bug has been marked as a duplicate of 204350 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.