Confirm
1,059
edits
Changes
initial page
This page is a design scratch intended to fix the situation with return receipts. There is a disambiguation problem here as stated in {{bug|328341}} where return receipts are considered to be many things. A technical return receipt is an SMTP extension that gives notification of deliver; this is not what most people think it is. An MDN is a return receipt that indicates the receiver has seen the message; of course the receiver is able to control sending of the receipt.
For [[Thunderbird]]'s purposely we should be thinking of "Return Receipts" as MDNs and not have the separation which will confuse people. If there is still a desire for the actual return receipt it's functionality should be moved into an extension.
== Receiving a Return Receipt Request ==
=== Viewing Message with Return Receipt Request ===
<pre>
{{ message header }}
+-----------------------------------------------------------------------------+
| +====+ $SENDER requests a Return Receipt for this Message [ Send ] [x] |
| |****| |
| +====+ Always send return receipts to $SENDER |
+=============================================================================+
{{ message body }}
</pre>
mockups
* [http://clarkbw.net/designs/return-receipts/receive-return-receipt-with-x.png receipt request with x button]
* [http://clarkbw.net/designs/return-receipts/recieve-return-receipt.png receipt request with ignore button]
=== After a Return Receipt has been Sent ===
<pre>
{{ message header }}
+-----------------------------------------------------------------------------+
| A Return Receipt for this Message was sent at $TIME $DATE [x] |
+=============================================================================+
{{ message body }}
</pre>
mockups
* [http://clarkbw.net/designs/return-receipts/requested-receipt-sent-02.png return receipt was sent (with timestamp)]
* [http://clarkbw.net/designs/return-receipts/requested-receipt-sent.png return receipt was sent]
=== Failed to Send a return Receipt ===
* What does a failed receipt send look like?
* Do we offer a [Re-Send] in the original?
== Sending a Return Receipt Request ==
=== Writing a message with a return receipt requested ===
<pre>
{{ message header }}
+-----------------------------------------------------------------------------+
| +====+ Request a Return Receipt for this Message [ Cancel ] |
| |****| |
| +====+ Always request return receipts from $SENDER |
+=============================================================================+
{{ message body }}
</pre>
mockups
* [http://clarkbw.net/designs/return-receipts/request-return-receipt.png request a return receipt]
* [http://clarkbw.net/designs/return-receipts/never-request-return-receipt.png never request a return receipt]
=== After canceling the request for a return receipt ===
<pre>
{{ message header }}
+-----------------------------------------------------------------------------+
| This message will *not* request a Return Receipt [ Undo ] [x] |
+=============================================================================+
{{ message body }}
</pre>
=== Receiving return receipts ===
* What does a return receipt look like to our user?
* How do we notify them of their arrival?
== Relevant Links ==
* [http://en.wikipedia.org/wiki/Return_receipt Return receipt (wikipedia]
* [http://nic-nac-project.de/~kaosmos/index-en.html#nrrh New Return Receipt Handler Extension] by Nic Nac Project
** [http://nic-nac-project.de/~kaosmos/returnreceipt.png NRRHE screenshot]
== Relevant Bugs ==
{{bug|380399}} — Return receipt status is only stored in .msf file and not in mbox file
''Possible problem that still needs to be worked around, indicated in the NRRHE extension''
{{bug|249684}} — Return Receipt prompt should ask Yes/No, not OK/Canel
''Good suggestions for improvements to button text. Used the 'Send' and 'Ignore' text suggestion from this bug.''
{{bug|346205}} — Return Receipts prefs shouldn't be under Composition
''The pref is currently under Advanced -> General -> [Return Receipts...]''
{{bug|221615}} — View Before Return Receipt (Reciept)
''Brings up good point that you should be able to wait to send a receipt and also see when a return receipt was sent''
{{bug|378224}} — Toolbar button: toggle return receipt
''Our info bar on send should provide an excellent fix to this situation''
{{bug|339233}} — return receipt settings refer to "Sent" folder when they really mean the folder specified as the fcc folder
''Possible bug with the placement of receipts according to where your sent messages are stored.''
'''Recommend''': Returned receipts shouldn't be messages at all really, but viewed almost as something stapled to the sent message. When you view the sent message you also see the receipts listed with the people, see {{bug|339307}} listed below. That said we also need to have a story for notifying people as receipts come in.
{{bug|386158}} — Sending receipt fails but no warning returns to user
''Possible failure in our storyline if there is a failure sending the receipt message the user is never informed nor given a chance to resend.''
{{bug|345205}} — Return receipt control doesn't work as advertised
''Seems to be a perception issue and we're doing the wrong thing. The pref says 'never 'send' If not in To: or CC: field, yet the report indicates that if you are in the received header it will ask anyway.''
=== Further Improvement Bugs ===
{{bug|312425}} — User should be able to choose folder where received return receipts would end
''Currently the pref only allows for Inbox or Sent folders to be chosen, this bug wishes to extend those choices to any folder.''
{{bug|339307}} — Return receipts (MDN) status overview
''Improvement for the overview of a message sent requiring a return receipt. There should be a nice opportunity to indicate each person in the receiver list who sent back a receipt.''
For [[Thunderbird]]'s purposely we should be thinking of "Return Receipts" as MDNs and not have the separation which will confuse people. If there is still a desire for the actual return receipt it's functionality should be moved into an extension.
== Receiving a Return Receipt Request ==
=== Viewing Message with Return Receipt Request ===
<pre>
{{ message header }}
+-----------------------------------------------------------------------------+
| +====+ $SENDER requests a Return Receipt for this Message [ Send ] [x] |
| |****| |
| +====+ Always send return receipts to $SENDER |
+=============================================================================+
{{ message body }}
</pre>
mockups
* [http://clarkbw.net/designs/return-receipts/receive-return-receipt-with-x.png receipt request with x button]
* [http://clarkbw.net/designs/return-receipts/recieve-return-receipt.png receipt request with ignore button]
=== After a Return Receipt has been Sent ===
<pre>
{{ message header }}
+-----------------------------------------------------------------------------+
| A Return Receipt for this Message was sent at $TIME $DATE [x] |
+=============================================================================+
{{ message body }}
</pre>
mockups
* [http://clarkbw.net/designs/return-receipts/requested-receipt-sent-02.png return receipt was sent (with timestamp)]
* [http://clarkbw.net/designs/return-receipts/requested-receipt-sent.png return receipt was sent]
=== Failed to Send a return Receipt ===
* What does a failed receipt send look like?
* Do we offer a [Re-Send] in the original?
== Sending a Return Receipt Request ==
=== Writing a message with a return receipt requested ===
<pre>
{{ message header }}
+-----------------------------------------------------------------------------+
| +====+ Request a Return Receipt for this Message [ Cancel ] |
| |****| |
| +====+ Always request return receipts from $SENDER |
+=============================================================================+
{{ message body }}
</pre>
mockups
* [http://clarkbw.net/designs/return-receipts/request-return-receipt.png request a return receipt]
* [http://clarkbw.net/designs/return-receipts/never-request-return-receipt.png never request a return receipt]
=== After canceling the request for a return receipt ===
<pre>
{{ message header }}
+-----------------------------------------------------------------------------+
| This message will *not* request a Return Receipt [ Undo ] [x] |
+=============================================================================+
{{ message body }}
</pre>
=== Receiving return receipts ===
* What does a return receipt look like to our user?
* How do we notify them of their arrival?
== Relevant Links ==
* [http://en.wikipedia.org/wiki/Return_receipt Return receipt (wikipedia]
* [http://nic-nac-project.de/~kaosmos/index-en.html#nrrh New Return Receipt Handler Extension] by Nic Nac Project
** [http://nic-nac-project.de/~kaosmos/returnreceipt.png NRRHE screenshot]
== Relevant Bugs ==
{{bug|380399}} — Return receipt status is only stored in .msf file and not in mbox file
''Possible problem that still needs to be worked around, indicated in the NRRHE extension''
{{bug|249684}} — Return Receipt prompt should ask Yes/No, not OK/Canel
''Good suggestions for improvements to button text. Used the 'Send' and 'Ignore' text suggestion from this bug.''
{{bug|346205}} — Return Receipts prefs shouldn't be under Composition
''The pref is currently under Advanced -> General -> [Return Receipts...]''
{{bug|221615}} — View Before Return Receipt (Reciept)
''Brings up good point that you should be able to wait to send a receipt and also see when a return receipt was sent''
{{bug|378224}} — Toolbar button: toggle return receipt
''Our info bar on send should provide an excellent fix to this situation''
{{bug|339233}} — return receipt settings refer to "Sent" folder when they really mean the folder specified as the fcc folder
''Possible bug with the placement of receipts according to where your sent messages are stored.''
'''Recommend''': Returned receipts shouldn't be messages at all really, but viewed almost as something stapled to the sent message. When you view the sent message you also see the receipts listed with the people, see {{bug|339307}} listed below. That said we also need to have a story for notifying people as receipts come in.
{{bug|386158}} — Sending receipt fails but no warning returns to user
''Possible failure in our storyline if there is a failure sending the receipt message the user is never informed nor given a chance to resend.''
{{bug|345205}} — Return receipt control doesn't work as advertised
''Seems to be a perception issue and we're doing the wrong thing. The pref says 'never 'send' If not in To: or CC: field, yet the report indicates that if you are in the received header it will ask anyway.''
=== Further Improvement Bugs ===
{{bug|312425}} — User should be able to choose folder where received return receipts would end
''Currently the pref only allows for Inbox or Sent folders to be chosen, this bug wishes to extend those choices to any folder.''
{{bug|339307}} — Return receipts (MDN) status overview
''Improvement for the overview of a message sent requiring a return receipt. There should be a nice opportunity to indicate each person in the receiver list who sent back a receipt.''
