Closed
Bug 191912
Opened 22 years ago
Closed 19 years ago
track email responses via subject and/or sender of incoming emails and time frame specified at send time.
Categories
(MailNews Core :: Backend, enhancement)
MailNews Core
Backend
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: y2khero2003, Assigned: mscott)
Details
User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 Build Identifier: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 Netscape Mail should be able to track email responses for selected emails as follows: 1. During the step of creating new emails (or responding to emails), the user can select an option to activate response tracking and enter or select a certain time frame (a certain number of minutes, hours, days, weeks, or months). 2. When sending such emails, the sender, the subject, and the desired latest response date and time, calculated from the current time and the time frame entered or selected, is stored on disk in an appropriate ASCII format, in a list that may be called an email response tracking list ("tracking list"). 3. All incoming emails are now scanned against the email response tracking list. If an incoming email matches the following criteria: a) sender of incoming mail is the same as an entry in the tracking list, AND b) subject of that entry in the tracking list is substring of the subject of the incoming mail (a string compare using "Re: " and subject will not work because there are also other methods of marking an email subject as a response, like "WG: "), AND c) the arrival date and time is less than the date/time specified in that entry, then that entry will be deleted. Additionally, if desired (user configurable), the user will be notified that the response tracking entry has been deleted. For a notification method, see next chapter. 4. Additionally, regularly or when connecting to email servers (user configurable), for all entries in the tracking list for which the destination date and time are smaller than the current date and time, the user is notified via a user-configurable method like xmessage, mailx, or any other convenient method. The user may also specify if such a notification may occur only once or more than once. Another possible method would be to resend the email automatically, after the whole response tracking system has been proven to be reliable. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Updated•20 years ago
|
Product: MailNews → Core
Comment 1•19 years ago
|
||
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/
Comment 2•19 years ago
|
||
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
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•