Teams has this "send message later" feature...

Marc Clifton

...where you can specify the date and time to send a message. Snazzy! I can send messages when I'm not working. People will think I'm working! :laugh: [edit]Doesn't work with the web version of Teams. I just get the standard browser right-click popup menu. Bummer.[/edit]

Latest Article:
Create a Digital Ocean Droplet for .NET Core Web API with a real SSL Certificate on a Domain

dandy72

All this technology, and we end up using it to randomly interject with a "yes, dear"

Forogar

I'll send you a message about that.... later.

- I would love to change the world, but they won’t give me the source code.

Daniel Pfeffer

Procrastinators of the world, unite! (When you get around to it...)

Freedom is the freedom to say that two plus two make four. If that is granted, all else follows. -- 6079 Smith W.

trønderen

Actually, that is a standard function in X.400 email, and one of the reasons why the X.400 standard prevailed in some commercial contexts quite for quite long. Note that in X.400, there is a well defined separation between the end user (either as sender or as recipient) and the mail transfer network. If you specified a delivery time for a message, it was sent to the recipient's 'local post office' immediately, or as soon as possible, but held back there until the specified time, at which it was put into the mailbox. If the mail transfer was slow or unreliable (as it often was, 35-40 years ago), this would ascertain that the message was delivered on time, which could be of great legal importance in e.g. bidding processes or anything with a deadline (there was also a function for cancelling a message before the specified delivery time; this was also considered an essential function from a legal point of view), information that for legal reasons should be held back until a certain time, etc. I believe that in the days of telegrams, delivered to your doorstep, you could also specify a delivery time. E.g. your 'Congratulations!' to a marrying couple would be delivered during the wedding dinner, to be read out loud to all the guests. Another X.400 function of essential legal importance was non-repudiation: When the mail transport service put the message in the recipient's mailbox, it could return to the sender a proof that the message had been delivered, and the delivery time, so that the recipient couldn't deny knowledge of, say, your bid before the deadline. Also, you could request that the recipient's user agent reported when the recipient actually fetched the message from his mailbox (although for most legal purposes, the time when the message was made available to him, in his mailbox, was probably more significant). This non-repudiation was also an essential reason why telex/teletext lived so long: It served as proof that an offer or bid had been given at the given time. Also common to telex/teletext and X.400: The infrastructure made it very difficult to forge a sender ID. SMTP did get a receipt confirmation function, but many years later, and as it is handled by the recipient himself, it cannot serve as proof of anything. Sender ID is as easy to forge as ever. Sometimes I am surprised that people dare to send anything of commercial/legal importance through SMTP at all ... :-)

Lost User

..incoming message scheduled for: 1st april, 2525 (if man is still alive).. "pending"

Bastard Programmer from Hell :suss: "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.

yacCarsten

I'll add it to my list

// TODO: Insert something here

Top ten reasons why I'm lazy 1.

trønderen

I'm so lazy that I defer even procrastination.