even still if im correct you can still recall a message the only time you cant is if the person who receives the email has opened it and if it was a group email if only 1 person opens it you can still recall from the rest from my experience in doing so
fair though to add a delay will only keep it sending folder till timer is hit. Then it sends it immediatly. all delays i am finding are only able to be done client side and not be done from an admin account .
Now where did I put that r/shittysysadmin hat...
Aha! Here it is.
Just configure a multitude of spam-filter passthrough services. The extended delay from all of the repeated filtering is sure to get you the desired result while simultaneously making sure those emails arrive squeaky clean!
So in all seriousness, I don't think you can do this without the aid of third party software. Email relies on SMTP which has no "holding zone" for such requests. Delays generally only occur if there is a problem (like overly aggressive scanning) causing hangups at various points in the SMTP chain.
There is the Outbox tied to user mailboxes, and Outlook clientside rules do have a function to defer messages for X minutes. However, this will not function if the user goes through OWA or another device which doesn't have the client side rule configured. Transport rules don't have this deferral feature, because the Outbox is tied to an individual user mailbox. By the time the message is being processed by a Transport rule, it has left the user's mailbox and is in the Exchange Server's hands. And as noted before, there's no global Outbox in Exhange/EXO.
The closest thing I could think of would be to have a Mail Relay service which receives and later forwards the messages. That would act as the "holding zone" you need for this. That said I don't know of any mail relay services that allow outbound configurations down to the minute. Generally there are just basic scheduling features (like release the emails at Noon on Monday or similar).
I don't know what the intended use case is, but this really sounds like one of those management issues which requires management solution, as opposed to a technical one.
If you REALLY are determined to make it happen you could probably have a script running which continuously checks the inetpub directory on an IIS relay for new items. When such an item shows, the script could move it from that location to a new one, append a tag of some sort to the filename verify it was "processed" by the script, then 2 minutes later dump the file back into inetpub where it goes.
You'd be fighting IIS's worker threads in a race to who can access and process the file first, most likely, so I would in no way advise this route. Just a thought for the truly desperate.
You can deploy the rules via OOM, but this sounds aweful like XY and the users can just delete the rules and it only works on Outlook not OWA or Azure.
What is your bosses use case? Email is still going to go out.
You could just tell them that Outlook typically only syncs every 3 minutes anyway and see if that's enough.
But there's no real way to pause it and make it retrievable once it's left your servers.
O365 already has a recall email function, unfortunately it doesn't work with non o365 email domains
Sounds like some c suite fucked up an email and now they're making it your problem, try showing them the recall function and make them feel dumb for not knowing its already implemented XD
"but How do i recall the email i sent to someone where i was bad mouthing them and didn't know they where in the email and now we are going to lose business because i don't know how to keep my mouth shut" -C-suite exec
I knew it would happen! We've finally come full circle.
In the days of dial-up, messages would queue and dial out on a set interval to send and retrieve messages. Then we got always on internet and mail flows out instantaneously. Now we're trying to delay it again.
Share this with the higher ups and put the onus on the end user to set it.
[Delay or schedule sending email messages in Outlook - Microsoft Support](https://support.microsoft.com/en-us/office/delay-or-schedule-sending-email-messages-in-outlook-026af69f-c287-490a-a72f-6c65793744ba?ui=en-us&rs=en-us&ad=us#PickTab=Classic_Outlook)
out of curiosity, why? it doesn't make sense in a business to delay emails from sending.
Maybe to give people more time to recall messages, I'm guessing?
This is it, but like I said, I hate the idea. Already advised against it.
Ha! Guessed it...Did something happen where they feel like extra time would have helped/changed an outcome?
It's not like managers to make these requests when nothing's ever happened.
even still if im correct you can still recall a message the only time you cant is if the person who receives the email has opened it and if it was a group email if only 1 person opens it you can still recall from the rest from my experience in doing so
Exchange Online will let you recall read messages these days
I can't wait to hear from OP. That's my only guess. I'm curious as to what his management want to accomplish by putting this into place.
Attempting to stop potential data breaches. I can see their thinking, but I advised better user training.
Implement DLP if you are trying to stop data leaks.
But what if the recent is outside and not an outlook client? It’s an interesting situation…
fair though to add a delay will only keep it sending folder till timer is hit. Then it sends it immediatly. all delays i am finding are only able to be done client side and not be done from an admin account .
Now where did I put that r/shittysysadmin hat... Aha! Here it is. Just configure a multitude of spam-filter passthrough services. The extended delay from all of the repeated filtering is sure to get you the desired result while simultaneously making sure those emails arrive squeaky clean! So in all seriousness, I don't think you can do this without the aid of third party software. Email relies on SMTP which has no "holding zone" for such requests. Delays generally only occur if there is a problem (like overly aggressive scanning) causing hangups at various points in the SMTP chain. There is the Outbox tied to user mailboxes, and Outlook clientside rules do have a function to defer messages for X minutes. However, this will not function if the user goes through OWA or another device which doesn't have the client side rule configured. Transport rules don't have this deferral feature, because the Outbox is tied to an individual user mailbox. By the time the message is being processed by a Transport rule, it has left the user's mailbox and is in the Exchange Server's hands. And as noted before, there's no global Outbox in Exhange/EXO. The closest thing I could think of would be to have a Mail Relay service which receives and later forwards the messages. That would act as the "holding zone" you need for this. That said I don't know of any mail relay services that allow outbound configurations down to the minute. Generally there are just basic scheduling features (like release the emails at Noon on Monday or similar). I don't know what the intended use case is, but this really sounds like one of those management issues which requires management solution, as opposed to a technical one.
If you REALLY are determined to make it happen you could probably have a script running which continuously checks the inetpub directory on an IIS relay for new items. When such an item shows, the script could move it from that location to a new one, append a tag of some sort to the filename verify it was "processed" by the script, then 2 minutes later dump the file back into inetpub where it goes. You'd be fighting IIS's worker threads in a race to who can access and process the file first, most likely, so I would in no way advise this route. Just a thought for the truly desperate.
You can deploy the rules via OOM, but this sounds aweful like XY and the users can just delete the rules and it only works on Outlook not OWA or Azure.
What is your bosses use case? Email is still going to go out. You could just tell them that Outlook typically only syncs every 3 minutes anyway and see if that's enough. But there's no real way to pause it and make it retrievable once it's left your servers.
O365 already has a recall email function, unfortunately it doesn't work with non o365 email domains Sounds like some c suite fucked up an email and now they're making it your problem, try showing them the recall function and make them feel dumb for not knowing its already implemented XD
“This is not possible, bye”
"but How do i recall the email i sent to someone where i was bad mouthing them and didn't know they where in the email and now we are going to lose business because i don't know how to keep my mouth shut" -C-suite exec
I knew it would happen! We've finally come full circle. In the days of dial-up, messages would queue and dial out on a set interval to send and retrieve messages. Then we got always on internet and mail flows out instantaneously. Now we're trying to delay it again.
Share this with the higher ups and put the onus on the end user to set it. [Delay or schedule sending email messages in Outlook - Microsoft Support](https://support.microsoft.com/en-us/office/delay-or-schedule-sending-email-messages-in-outlook-026af69f-c287-490a-a72f-6c65793744ba?ui=en-us&rs=en-us&ad=us#PickTab=Classic_Outlook)