178724 - mdn:return receipt on, forwd as attach will include rr request but forw as inline won't

Status: RESOLVED EXPIRED

(SeaMonkey :: MailNews: Backend, defect)

Description

[grylchan]

using commercial trunk 20021106 and commercial
branch 20021106.

If you forward any mesg [mesg w/rr or mesg w/out rr] as
attachment, it will include RR flag (assuming you have the pref
'when sending mesgs, always request a receipt' set) but
if you forw inline it won't.

This is only a BUG if we decide 'forw or edit as new' should NOT
have return receipt flag on the mesg even though you have
your pref set 'when sending mesgs, always request a receipt'.

Currently for 'Forw as INLINE 'no return receipt flag on it even
though you have RR on. See bug 139617

NOT RELATED to bug 162842 but discovered this bug when testing that bug.

steps
1)set pref set 'when sending mesgs, always request a receipt'.
2)forw any mesg as attachment
3 [details] [diff] [review]) go to options|Return Receipt 

result: menu item is checked and if you send it off, the recepient
        will be prompted for return receipt
expected: not have flag set (even though have the ret rcpt pref on)
          since forw as inline doesn't include it

this bug is related to bug 139617. So which ever bug has
the correct behavior the other one should be corrected.

Comment 1

[Frederic Bezies]

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

Comment 2

[David :Bienvenu]

I don't know why the fact that you're forwarding a message should have any
affect on the generation or not of a return receipt, other than the bug that JF
already fixed where the forwarded message might have a return receipt. 

Comment 3

[David :Bienvenu]

Gary, if I can resummarize, is the bug here that forward inline doesn't request
return receipts?

Comment 4

[grylchan]

you wrote:
>Gary, if I can resummarize, is the bug here that forward inline doesn't request
>return receipts?

Which applies to bug 139617

I guess when I wrote this bug, I meant that Forw as Attach includes
Return Receipt flag.

So since we have 2 very different behaviors for Foward as Inline and
Forw as Attachment, I didn't know which was the bug (do we include
return receipt flag when forwarding or don't?)

Comment 5

[David :Bienvenu]

there was a bug, already fixed, that reading a message that had an attached msg
with a rr request in it, caused us to send a return receipt (we were not
attaching the rr request to the new msg; the code that was reading the forwarded
message was incorrectly looking into the forwarded message for the return
receipt request). That bug is fixed. So, let's forget about that one. What's the
remaining bug? In this bug, you seem to say that if I forward a message inline,
and explicitly request a return receipt for the new msg, that return receipt
request is not generated/honoured.

Comment 6

[grylchan]

Ok David I'm getting more confused now.

>there was a bug, already fixed, that reading a message that had an attached msg
>with a rr request in it, caused us to send a return receipt (we were not
>attaching the rr request to the new msg; the code that was reading the forwarded
>message was incorrectly looking into the forwarded message for the return
>receipt request). That bug is fixed.

I understand what you are saying (i assume above applies to bug 162842).
That when we forw a mesg (w/rr) we set the rr flag on since it was 'reading'
the original mesg.

But I still see something else. Go to your prefs and set 'when sending mesgs,
always request a receipt'. Take any msg that doesn't have a Ret.Recpt
request in it. Forw as attachment and you will see ret recpt flag
when you go to options|return receipt. But If I do the same for
Forw as inline, the RR flag is not set.


But yes you are correct that if I set Ret Recpt pref on, and forward
any mesg inline, there will not be Ret Recpt flag on that mesg.
Should there be?

sorry for the confusion

Comment 7

[David :Bienvenu]

yes, that's exactly the bug. Forwarding inline doesn't apply the default return
receipt setting, if that setting is to request a return receipt.  If you
manually set the return receipt option, it does work. So the problem is with
forward inline and the compose window.

Comment 8

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

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

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

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420