Closed Bug 279240 Opened 20 years ago Closed 19 years ago

Extract email addresses from list

Categories

(SeaMonkey :: MailNews: Message Display, enhancement)

1.7 Branch
x86
Windows XP
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: kepes.krisztian, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041217
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041217

Many times I use email address collections.
But sometimes I get mail from the member of a collection (named Joke). In this
time, when I want to forward this mail to all of the members of the Joke, except
this man, I can do these things:
- I send to the collection, but this member is get his forwarded mail
- I get the mail addresses manually, and copy-paste to mail comp. window.

The "collected mail addresses" extracting is a better thing, I think.
It is split the addresses to individ. addresses, and I can delete one, or more
from that.

And when I need to send this mail to more collections, but many addresses are
same in these collections, the extractor is extract them in _only one address_ !

Example:
Joke: Mary, John, Carol
Private: Mary, Jane, Queen, Carol

I get mail from Mary. I want to send it to Joke's members. Extractor is extract,
and I can delete Mary from the "To" field. She is don't get his mail.

Or I get mail from Mary. I want to send it to Joke/Private. Mary and Carol is
get this mail in two times.
Extractor can extract them once.



So I think, that is needed to mozilla mail to simplify the address handling.

Reproducible: Always
Assignee: general → sspitzer
Component: General → MailNews: Main Mail Window
QA Contact: general
Summary: Extract Collection of Email Address → Extract email addresses from list
Version: 1.7 Branch → unspecified
Version: unspecified → 1.7 Branch
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/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.