139617 - MDN:No Read receipt Request when Forwarding(inline) or Edit Message As New

Status: NEW

(MailNews Core :: Backend, enhancement)

Description

[Joel Nelson (don't send email)]

This could be an option in Return Receipt Preferences (or just a bug to fix)...
   My preferences are set to request a receipt for all outgoing messages.   When
I use the Edit Message As New tool, a receipt is not requested (I have to
manually request one).   This happens even if the original message requested a
receipt.  
   I use Edit Message As New to reply to e-mails with background images since
while Reply doesn't preserve the background, Edit Message As New does.  
   In my opinion, if a user's preferences are set to request a receipt for each
outgoing message, it should also apply to messages generated using Edit Message
As New.

Comment 1

[grylchan]

Changing component from composition to mail back end
reassigng bug, reassigning qa contact
Changing os from os x to  all
changing severity from enhancement to normal

Changing summary line
Old line was: Request read receipt when using Edit Message As New

If you have Return Receipts on and you compose or reply to a mesg
you will see in the composition window: options|Return receipt checked.

But if you forward or edit a mesg as new, you won't see return
receipt checked and hence the mesg will not request a return receipt.

Confirmed on commercial trunk: 2002042510 Win98 &
Commercial branch 2002042306 winNT 4.0

Should I nominate for nsbeta1?

Comment 2

[grylchan]

changing platform to all

Comment 3

[grylchan]

adding nsbeta1 keyword

Comment 4

[Jeff Tsai]

This would be a nice to have feature. Changing severity to enhancement. In
theory, if a message originally request for a MDN report when Forwarding or Edit
message as new if request for return receipt the Disposition-Notification-To:
header value should include the original message sender. There might be privacy
arguments on whether the original sender be added or not. To be more fancier,
one could have an ui specifically to solicit user's input when requesting for
MDN report.

Comment 5

[Joel Nelson (don't send email)]

I use "Edit Message As New" often in Mozilla for replying to messages since I
found that while replying to e-mails with stationery using the Reply button
loses the stationery, using Edit Message As New generates a new compose window
with the stationery.   So, I can take the Edit Message As New window, add RE: to
the subject line, request a receipt (which should already have been requested!),
add "sender" wrote:, and type a reply.    It's not the intended use of the Edit
Message As New feature, but it provides a workaround until Bug 119594 is fixed.
   However, I think it gives me the wrong perspective on the proper use and
purpose of this command.
   (Off-topic for this bug:  Why can't similar code used to generate the Edit
Message As New window be used for a reply window?  If that were to be done then
bug 119594 seems that it could be easily fixed).
   Back on topic...    Edit Message As New does not work entirely as a
'redirect' anyway as when I use Edit Message As New, the new message shows as
coming from me, not the original sender.  From that, why would the receipt go to
the original sender?   The original sender would have received a receipt already
for their message.   As far as the UI for user input (comment #4), what would be
the options presented?
   In reply to comment #1, Mozilla doesn't request a receipt for Edit Message As
New compose messages (the purpose of this bug entry).  I do receive receipts
from forwards (I use "Forward Message As Attachment"). 

Comment 6

[Jeff Tsai]

Personally, I don't think using Edit as New Message as reply message is right.
As you said, Edit Message As New provide a way to use the stationery of the
original message including attachement. It's the main purpose of that. I
implemented the feature in the early days. However, Edit As New may violate the
original author's copyright. Someone could easily store other people's work as
posted as his/her work. 

>> ... why would the receipt go to the original sender? 

Because the original sender may not want his original message forward to someone
else without the prior consent from him. He may want to know who will be the
recipient if his/her message get forwarded by the original recepient. I would
definely want to know if I said something about my boss and the message gets
forwarded around.

>> As far as the UI for user input (comment #4), what would be the options
presented?
For example, if request for return receipt we could prompt the user for
including the the original sender's email address in the DNT header. Or provide
a way in the menu item to check for including original sender's address in the
DNT header. 

Comment 7

[grylchan]

*** Bug 162842 has been marked as a duplicate of this bug. ***

Comment 8

[grylchan]

see bug 178724 (forw as attachment will have rr flag on).
Don't know what the correct behavior is. RR flag on/off
for forwrd mesg as inline/attachment?