Beware that timing is an issue on Android. Due to power consumption apps normally cannot use an exact timer. Doing so would drain the battery too much.
Thus, inaccurate timers or the system’s alarm manager are used. Both leading to scheduled messages not being sent at the exact desired time.
So, if delayed sending is important to you with correct timestamp, you should not rely on a client running on an Android device.
If your account is an exchange account, you can set the delay on the server through the OWA.
doing “scheduled send” from the client side isn’t very reliable, regardless the client. with the client-side approach you are counting on the client (desk/laptop/mobile) being on and having connectivity at the desired time. if that’s “in the middle of the night”, when you’ve likely turned your desk/laptop device off, or when you have your mobile device in airplane mode, it’s going to fail.
the way this works with gmail and outlook the message is stored and scheduled on and sent from the server side.
if you have a client that can interact with the server to do the setup that’s fine, but otherwise don’t count on it.
scheduling isn’t part of the IMAP protocol, and so is server specific. so, you’re unlikely to see server-side support in other than the service provider’s client or webmail interface.