188451 - possibility of sending receipts not requested by the sender

Status: UNCONFIRMED

(MailNews Core :: Backend, enhancement)

Description

[85318892]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.0) Gecko/20020530
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.0) Gecko/20020530

I often receive a lot of emails waiting for answers, and I want to assure the
senders that I have received/read their email sending a short notice in the
cases I will have time for a response later only.
So I would like to see new buttons:
- "received"
- "read"
The first sends a (multilingual, customizable) sort answer to the sender of the
respective email, stating "your email written at YYYY-MM-DD hh:mm:ss has been
received by XXXX".
The second send a short answer stating "your email written at YYYY-MM-DD
hh:mm:ss was read by XXXX".
I would use this feature many times a day.


Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1

[Andreas Troschka]

RFC2298 and the RFC822 describe also this two processes, so the implementation
into Mozilla would be formally correct.
Concurrent mail-agents are already supporting this features so, if somebody will
work on this, he/she/they should look at first for compatibility.
The RFCs are actually a bit too vague on this items and leave much freedom on
how to implement this processes.

...Just to flag-up a bit.

Comment 2

[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 3

[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 4

[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 5

[Serge Gautherie (:sgautherie)]

At first glance, it would look like a valid enhancement...

Comment 6

[Rainer Bielefeld]

Sounds plausible, but I doubt that "Seamonkey only" is appropriate.

Comment 7

[Rainer Bielefeld]

I asked for support at mozilla.dev.extensions with reference to this Bug.