A &MESSAGE; of type "groupchat" SHOULD NOT be carbon-copied.
A &MESSAGE; containing a &xep0249; SHOULD be carbon-copied.
A &MESSAGE; containing a Mediated Invitation SHOULD be carbon-copied.
-
A private &MESSAGE; from a local user to a MUC participant (sent to a full JID) SHOULD be carbon-copiedThe server SHOULD limit carbon-copying to the clients sharing a Multi-Session Nick in that MUC, and MAY inject the <x/> element into such carbon copies. Clients SHOULD ignore carbon-copies of MUC-PMs related to a MUC they are not joined to..
+
A private &MESSAGE; from a local user to a MUC participant (sent to a full JID) SHOULD be carbon-copiedThe server SHOULD limit carbon-copying to the clients sharing a Multi-Session Nick in that MUC, and MAY inject the <x/> element into such carbon copies. Clients can not respond to carbon-copies of MUC-PMs related to a MUC they are not joined to. Therefore, they SHOULD either ignore such carbon copies, or provide a way for the user to join the MUC before answering..
A private &MESSAGE; from a MUC participant (received from a full JID) to a local user SHOULD NOT be carbon-copied (these messages are already replicated by the MUC service to all joined client instances).
As the above is an implementation detail of servers, clients MUST NOT rely on the server implementing a particular set of rules for which messages are eligible for Carbons delivery.