RFC 6121 (8.5.3.2.1) non-compliance: Chat message sent to unavailable resource ID not sent to other available resource IDs
Description
During testing of RFC6121, noticed that Chat messages sent to a non-existent or non-available user are not being received by other available resources (with non-negative priorities).
If there is more than one resource with a non-negative presence
priority then the server MUST either (a) deliver the message to
the "most available" resource or resources (according to the
server's implementation-specific algorithm, e.g., treating the
resource or resources with the highest presence priority as "most
available") or (b) deliver the message to all of the non-negative
resources that have opted in to receive chat messages.
Replication Steps:
Send a message to another user, specifying a resource ID for them that doesn't exist, or isn't available.
Environment
Openfire 4.0.0 (beta/nightly (5th Jan), using Psi as client.
During testing of RFC6121, noticed that Chat messages sent to a non-existent or non-available user are not being received by other available resources (with non-negative priorities).
According to RFC6121 (https://tools.ietf.org/html/rfc6121#section-8.5.3.2.1):
If there is more than one resource with a non-negative presence priority then the server MUST either (a) deliver the message to the "most available" resource or resources (according to the server's implementation-specific algorithm, e.g., treating the resource or resources with the highest presence priority as "most available") or (b) deliver the message to all of the non-negative resources that have opted in to receive chat messages.Replication Steps:
Send a message to another user, specifying a resource ID for them that doesn't exist, or isn't available.