On Thu, 2012-04-19 at 18:01 +0100, Matthew Wild wrote: > However even <archived/> doesn't cover the case of the client knowing > the id of its *outgoing* messages. The server could echo them back > with <archived/>... but then things start to get a bit muddy.
Thoughts. Say that Carbons shall echo back your outgoing messages, with the <archived/> stamp. Or, some cross between that and Delivery Receipts, which just contain the <archived/> with the UID. Message Archive Receipts? -- Kim Alvefur <[email protected]>
