3 ms·
I think you might be mixing up two features here. One is deleting a message from your own inbox (this part about your email example makes sense). The other is
by tharkun__ 5y ago
I think you might be mixing up two features here. One is deleting a message from your own inbox (this part about your email example makes sense).
The other is deleting a message that was sent to someone else from _their_ inbox. Which email does not allow you to do.
Except some clever people tried to implement this (notably Outlook and/or Microsoft Exchange has such a feature IIRC) where it sends another email to "recall" the earlier message. It's funny when you receive those recall messages in a non-Microsoft email client and on a different server than the Exchange sever they're using. I.e. you just ignore their request to recall and now you _really_ go read the message they're trying to recall, because it makes it _more_ interesting. Also googling this quickly it seems even if you stay completely within the Microsoft ecosystem it only works if the recipients didn't open the original email yet:
With message recall, a message that you sent is retrieved from the mailboxes of the recipients who haven’t yet opened it.
https://support.microsoft.com/en-us/office/recall-or-replace-an-email-message-that-you-sent-35027f88-d655-4554-b4f8-6c0729a723a0 https://support.microsoft.com/en-us/office/recall-or-replace...
- proc0 5y agoRight, well in concept that feature is silly. It would be like paying USPS to remove some letter from a physical mailbox. At some point you need to commit to the message. Regardless what I'm really saying is that it's all probably smoke and mirrors on the client server (plus client UI). The server is probably configured to keep all messages anyway, and it gets "tombstoned" and not sent by the middle tier server. I don't know of course, but I was talking about how users are not really in control as they think they are.