Section 5. When to Request Receipts; 5.2 FULL JID states that
“If the sender determines that the recipient’s client does not support the Message Delivery Receipts protocol then it SHOULD NOT request a receipt when sending a content message to that full JID”
Currently Smack 4.4.0 implementation of:
“Enables/Disables automatic requests of delivery receipts for outgoing messages of …”
is globally enabled or disabled independent of recipients capabilities.
It would be good if smack can include support optional sending the Delivery Receipt Request base on contact BareJid to allow contact multiple logins;
Although requested, personally not sure how useful is this support; as the Receipt Request is required to be sent if contact login with multiple resources, and not all resources support the Delivery Receipt Request feature.
How the sender handle the ack from contact with multiple resources login?