Please provide a snippet of the part of the specification which we violate if possible: 3.2.2. Server Processing of Outbound Subscription Cancellation Upon receiving the outbound subscription cancellation, the contact's server MUST proceed as follows. 1. If the user's bare JID is not yet in the contact's roster or is in the contact's roster with a state of "None", "None + Pending Out", or "To", the contact's server SHOULD NOT route or deliver the presence stanza of type "unsubscribed" to the user and MUST NOT send presence notifications of type "unavailable" to the user as described below. Please provide a link to the specification: https://datatracker.ietf.org/doc/html/rfc6121#section-3.2.2 Prosody (observed with version 0.11.9) notifies the user whose subscription request is being rejected about the rejection, at least when both involved users are on the same server, and the user is in the contact's roster with "to" state.