I think it's just "ReturnReceipt".

I'm not sure what the structure is, or how the originator might be affected by what your forwarding agent is doing. It's often the originator that gets a return receipt, and I think that's the agent signer in most cases on the Notes side.

I'm as baffled as you that the originator would be blind-copied an email they sent. Odd.

There are two fields:  ReturnReceipt and RR2.  When I send an email with Return Receipt, the ReturnReceipt field is set to 1 in the message in my Sent folder.  After a Return Receipt has been generated by the recipient, the ReturnReceipt field disappears, and the RR2 field remains. The RR2 field establishes that a ReturnReceipt at one point existed in the message. 

I do have a ticket open with IBM on this but need to try all avenues to get an answer.  With regards to the Return receipt setting, there is no way, per IBM, to remove that setting programatically because the document is in a truncated state.  The document has to be retrieved first.  So we're at the point on how to capture the return receipt before it escapes. 

Jay Marme per your response it's almost as though once the Return Receipt is triggered the first time no new return receipts will be triggered again, is that what you were writing? 

Mike Woosly per your response on a return receipt there is no way that the owner would be bcc and IBM has said this also, but it still seemingly happened.  

I'd probably be looking at the "Recipients" field to see exactly what got there.

Also, the forwarding code may need a review to see exactly what it's expecting to route to.

Clearly the best method for dealing with a truncated document is to replicate the full version, then you have greater control. But if you made a new doc & copied what you wanted into it, I'm unsure how Notes could possibly force you to re-enable return receipt.

It comes down to, how the agents forward the docs.

Yes, that was what I was getting at.  Once a Return Receipt is generated for a given user, it can't be triggered again for that user. You can, of course, have multiple recipients on a message, and get a Return Receipt for each one. 

First, thanks everyone for responding to this.  It's bit of a mess trying to figure out what's happened and how and unfortunately I'm not getting all the information for the person that this happened to that I'd like, such as how exactly was the forwarding done, but I'm pretty sure the Forwarding done was the standard Notes Forwarding, nothing different.

Regarding my heading, if everything in the ACL is, except for the Admin, is Reader or lower can a return receipt still be generated when a message is opened that has return receipt turned on?

The issue is whether the user can route, and that's pretty straightforward.

I think that's the key issue. I wasn't aware simply truncated documents had this issue, but I've seen the issue with archive documents. In fact I remember seeing archive docs firing return receipts multiple times after archival, months after they'd been received.

I didnt control administration though so could check no further.